Microsoft Teams Room Can't sign in

Today I encountered the same issue with (2) new Crestron UC Teams Room systems. They would get stuck at the "Signing In" stage, although I could see successful login on the account by looking in Azure AD at the "Sign-Ins" for the room account. As it turns out, the issue was with the version of MS Teams Rooms that was installed by Crestron when the unit was shipped (4.7.19). I located Microsoft's page on how to locally update a unit to the latest version via PowerShell, and once the units were running 4.10.10 all was well.

Manually update a Microsoft Teams Rooms device - Microsoft Teams | Microsoft Docs

Before you run this script, it's important to note that the "Skype" user must be logged-in for this script to complete successfully. Here's how to do that:

1. Connect a keyboard to the device
2. Boot the device and allow Teams Rooms to load. It will say "Signing In"
3. Press the Windows Key 5 times to bring up the login screen
4. Log in as the Administrator account
5. Follow the instructions in the article to place the update script (PS1 file) in the Downloads folder for the Admin account
6. Launch PowerShell via "Run as Administrator"
7. Navigate to the Downloads folder for the Admin user
8. Set the PS execution policy to unrestricted (Search Set-Execution-Policy if unfamiliar)
9. Run the update script and wait for it to complete (3-5 minutes)
10. Reboot the unit
11. If your stars are aligned, the issue will be resolved

Hello Oliver,

Yes, it's true the signing in now works with the cloud-only account. I did not make any changes regarding ADAL (as mentioned) we use just Azure AD Connect with password hash synchronization for SSO of our domain-joined clients. Possible that it might not work on non-domain joined devices with a local user account (like the "Skype" default login).

I can not check anymore with the locally created account that has been synced to AAD because I already deleted it. But I just sent you the new logs with the new account by PM.

Best Regards,

Marc

Hello Marc,

Thanks for your clarification with patience.

So from the last updates you shared above, my understanding is you can sign in the Microsoft Teams Room with the new created online account ( onmicrosoft.com) without problem,  and as you have enabled ADAL for the required sections, may I double confirm if you still cannot use the old account ?( I think it would be custom domain generated) since I noticed SSO modern authentication failed from the log you shared before.  If you can sign in the Microsoft Teams Room with the new created account, but the old account still experience issue, in this case could you please sign in the worked account after that please re-collect the log which we talked before, after that please share the worked one with me in the PM, and I'd like to do more research and have a comparison, thanks.

Your patience will be highly appreciated.

Best Regards,

Oliver

Hello Marc,

Thanks for your updates with patience, and sorry for my late response because of OOF.

According to the log file you shared in the PM, I checked it and found some errors in the teams log.  It shows " Get UPN for user signin.  Found user and returned it for UPN"  and  " ADAL SSO failed login failed " Die moderne Authentifizierung ist hier fehlgeschlagen, aber Sie können sich trotzdem anmelden. Ihr Statuscode lautet caa2000c. diag:"   I translate the error to English it is " Modern authentication failed here, but you can still log on. Their status code is caa2000c."    

Since the Microsoft Teams Room you directly created from Microsoft 365 online in a Hybrid environment, may I double confirm if you enabled the ADAL ( modern authentication) for Microsoft Teams Room?  For more details, please refer to Authentication in Microsoft Teams Rooms"   By the way, since you don't have Skype for Business on-premises environment, and has Exchange Hybrid instead, based on my research on deploying the Microsoft Teams Room with Exchange on-premises and Skype for Business online ( or Microsoft Teams), it is recommended to create the room resource account from on-premises and then sync it to Microsoft 365, but not directly create it from online.  For more details, please refer to https://docs.microsoft.com/en-us/microsoftteams/rooms/with-exchange-on-premises.  

Please feel free to share with me if you got any further updates, thanks.

Best Regards,

Oliver

Hello Oliver,

Thank you for your advices. Right now, we have a specific room account in Exchange Online to access Microsoft Teams Rooms. I created another test account with no success before, at the end I tried with 3 different accounts and the issue is unfortunately the same, so I am doing all further tests now with that signle account.

The Teams Room device is registered in my Teams Admin Center as unhealthy since Teams can not sign in (see Screenshot in my post on September 15). Firmware and drivers are up to date of the Logitech Tap Device and the Intel Nuc Device. Windows and teams rooms as well:

Teams Admin Agent 2020.7.12.1

Windows Operating System 10.0.18363.1082

Microsoft Teams Room App 4.5.37.0

I just installed and started the Teams Rooms App in the Admin mode with no difference (Can not sign in to Microsoft Teams). I sent you the logs from the device.

Best Regards,

Marc