Are you getting a “Couldn’t sign in to Microsoft Teams” message on your Teams Room System?
So this more than likely applies to those whom are rolling out Microsoft Teams Room systems for the first time, but I hope to also provide some of those whom are troubleshooting some points to look at to know where to go.
More than likely you are setting up your first system and have gone through the initial setup and are here because you are seeing something like the screen above. The above screen indicates that this unit is not signing into exchange, Teams or Skype for business within its environment. Let’s break down how I can evaluate that just from seeing this screen and then we can go further into how to troubleshoot this on the surface.
First on the image above, you can see at the top we have the banner of Couldn’t sign in to Microsoft Teams. This is a message that will appear at the top and indicates the unit is having trouble authenticating. This is very broad and can be many different things so lets look at the rest of the screen.
In the upper right you do not see the name of the room under the time. This indicates the unit has not yet logged into Exchange either. So we know we can’t get to Teams or Exchange which might both be O365 depending on your deployment, but what about on-prem Skype for Business?
Well the lack of the new meeting or dial pad icon means the unit has not yet signed into either Skype for Business or Teams as it is not yet able to authenticate to either. How do we proceed?
TROUBLESHOOTING THE CANNOT LOG IN ISSUE
Since the above image doesn’t have any authentication to Skype, Teams or Exchange the first step that I would take is to see if the unit has an IP address and can in fact reach some of the intended destinations.
In the settings, there is a spot under the about screen that will show your IP address. If you have an IP address…