Teams Room Cannot sign in

%3CLINGO-SUB%20id%3D%22lingo-sub-833663%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833663%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F402047%22%20target%3D%22_blank%22%3E%40WhizFi%3C%2FA%3E%26nbsp%3Boften%20this%20kind%20of%20thing%20comes%20down%20to%20some%20conditional%20access%20policies%20or%20other%20config%20thats%20refusing%20the%20Teams%20Room%20System.%20If%20you%20go%20into%20AzureAD%20and%20look%20up%20the%20useraccount%2C%20can%20you%20see%20any%20blocked%20login%20events%20and%20their%20cause%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-833667%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833667%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F402047%22%20target%3D%22_blank%22%3E%40WhizFi%3C%2FA%3E%2C%3CBR%20%2F%3E%3CBR%20%2F%3EHave%20you%20assigned%20a%20Teams%20Meeting%20Room%20Licence%3F%20The%20following%20article%20may%20help.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fblog.kloud.com.au%2F2019%2F02%2F21%2Fenabling-microsoft-teams-meeting-rooms%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblog.kloud.com.au%2F2019%2F02%2F21%2Fenabling-microsoft-teams-meeting-rooms%2F%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3ELet%20me%20know%20how%20it%20goes!%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-833674%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833674%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169605%22%20target%3D%22_blank%22%3E%40Christopher%20Hoard%3C%2FA%3E%26nbsp%3Bit%20need%20a%20team%20license%2C%20doesn't%20need%20the%20meeting%20room%20license%20specifically.%20It%20can%20just%20be%20a%20cheaper%20way%20to%20purchase%20the%20right%20licenses.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-833677%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833677%22%20slang%3D%22en-US%22%3E%3CP%3EHmm.%20That%20is%20true.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-833847%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833847%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F402047%22%20target%3D%22_blank%22%3E%40WhizFi%3C%2FA%3EIf%20you%20just%20created%20the%20account%2C%20wait%20for%20a%20little%20while%20as%20sometimes%20it%20takes%20time%20to%20populate%20to%20Teams%20and%20I%20have%20noticed%20that%20time%20increasing%20lately.%26nbsp%3B%20Also%20as%20someone%20before%20pointed%20out%2C%20if%20you%20are%20using%20anything%20like%20Pyng%20Federate%20or%20another%20service%20to%20login%2C%20try%20bypassing%20that%20service%20for%20authentication%20if%20you%20can.%26nbsp%3B%20Nothing%20that%20you%20have%20posted%20stands%20out%20as%20the%20definitive%20reason%20you%20are%20having%20an%20issue%20though.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-834094%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-834094%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F178440%22%20target%3D%22_blank%22%3E%40Steven%20Collier%3C%2FA%3E%26nbsp%3BYou%20may%20be%20right.%20We%20are%20working%20on%20the%20Azure%20AD%20side%20at%20this%20moment.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20there's%20no%20%22reply%20to%20all%22%20function%20in%20the%20forum%2C%20regarding%20the%20licensing%20etc.%20We%20already%20used%20this%20account%20to%20test%20on%20the%20evaluation%20unit%20and%20it%20worked%20without%20any%20problems.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20has%20an%20E5%20license%20attached%20to%20it.%20(I%20know%2C%20E3%20was%20enough%20too).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYesterday%20I%20managed%20to%20download%20the%20logs%2C%20but%20frankly%20I'm%20not%20sure%20what%20I%20am%20supposed%20to%20look%20for.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-833572%22%20slang%3D%22en-US%22%3ETeams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833572%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20trying%20to%20install%20our%20first%20Teams%20Rooms%20system.%20Though%20the%20system%20(Lenovo%20ThinkSmart%20Hub%20500)%20is%20logging%20onto%20the%20SRS%2C%20it%20is%20not%20signing%20in%20to%20the%20Ms%20Teams.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20checked%20the%20system%20logs%20but%20I%20could%20not%20detect%20any%20valid%20information%3A%3C%2FP%3E%3CP%3E%3CSPAN%3E%7B%22Description%22%3A%22Network%20status%20%3A%20Healthy.%20Exchange%20status%20%3A%20Connected.%20Signin%20status%3A%20Healthy.%20Teams%20Signin%20status%3A%20Unhealthy.%22%2C%22ResourceState%22%3A%22Unhealthy%22%2C%22OperationName%22%3A%22Heartbeat%22%2C%22OperationResult%22%3A%22Fail%22%2C%22OS%22%3A%22Windows%2010%22%2C%22OSVersion%22%3A%2210.0.17134.950%22%2C%22Alias%22%3A%22abc%40hiddenmailaddress.onmicrosoft.com%22%2C%22DisplayName%22%3A%22TeamsRoom%22%2C%22AppVersion%22%3A%224.0.105.0%22%2C%22IPv4Address%22%3A%22hidden%22%2C%22IPv6Address%22%3A%22%22%2C%22IPv4Address2%22%3A%22hidden%22%7D%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EThe%20account%20is%20active%20and%20has%20been%20tested%20on%20a%20demo%20unit%20before%3C%2FLI%3E%3CLI%3ENo%20local%20admin%20account%20because%20it's%20being%20managed%20by%20Azure%20AD.%26nbsp%3B%3C%2FLI%3E%3CLI%3ESkype%20for%20Business%20and%20Exchange%20backends%20sign%20in%20but%20for%20some%20reason%20Teams%20doesn't.%3C%2FLI%3E%3CLI%3EE5%20license%20attached%20to%20it.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20would%20really%20appreciate%20your%20ideas.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-833572%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ehub%20500%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Elenovo%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eteams%20rooms%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1213412%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1213412%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20we%20have%20noticed%20the%20same%20issue%20on%20several%20of%20of%20our%20devices.%3CBR%20%2F%3ESuddenly%2C%20we%20were%20not%20able%20to%20sign%20in%20to%20Teams%2C%20which%20worked%20perfectly%20all%20the%20time%20before.%3CBR%20%2F%3EWe%20noticed%20that%20the%20time%20was%20not%20correct%20set%20up%20on%20the%20device.%20We%20fixed%20clock%20and%20activated%20'internet%20time%20synchronization'%20and%20after%20reboot%20the%20device%20was%20able%20to%20log%20in%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EChecking%20time%20zones%20and%20time%20could%20resolve%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1221721%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1221721%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F132432%22%20target%3D%22_blank%22%3E%40Franka%20Sander%3C%2FA%3E%26nbsp%3Bthanks%20a%20lot%2C%20we%20were%20having%20the%20same%20issue%20with%20our%20system.%20Log-in%20the%20admin%20session%20and%20making%20sure%20the%20time%20was%20synced%20solved%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1667497%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1667497%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20here%20we%20got%20the%20exactly%20same%20problem%20with%20our%20Logitech%20Tap%20Rooms%20System.%20Time%20and%20timezone%20is%20correct%2C%20conference%20room%20licence%20assigned%20correctly%2C%20conditional%20access%20rules%20are%20disabled%20for%20this%20user%2C%20Teams%20rooms%20app%20is%20updated%20to%204.5.37.0.%20Eveything%20has%20been%20set%20up%20in%20the%20cloud%2C%20still%20the%20teams%20login%20is%20shown%20as%20%22unhealthy%22%20while%20all%20other%20logins%20(Network%2C%20Exchange%2C%20etc.)%20are%20in%20a%20%22healthy%22%20state.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20support%20is%20not%20able%20to%20give%20any%20advice%20or%20solution%20for%20more%20than%201%20month%20now.%20It's%20really%20annoying%20since%20I%20was%20creating%20the%20user%20several%20times%20with%20the%20SkypeRoomProvisioningScript%20and%20even%20first%20reset%2C%20then%20completely%20reinstalled%20the%20NUC%20device%20that's%20running%20the%20teams%20rooms%20app.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1723170%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1723170%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F793872%22%20target%3D%22_blank%22%3E%40MVo_CH%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi.%26nbsp%3B%3CSPAN%3EI%20have%20the%20same%20problem%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EMy%20config%3A%20Logitech%20Tap%20Rooms%20%2B%20Intel%20NUC%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1789145%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1789145%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F812940%22%20target%3D%22_blank%22%3E%40Farik7707%3C%2FA%3E%26nbsp%3BI%20have%20almost%20the%20same%20issue%20except%20Skype%20for%20Business%20says%20disconnected%20and%20Teams%20is%20logged%20in%20but%20still%20have%20the%20same%20message%20at%20the%20top%20%22Signing%20in...%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1789188%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1789188%22%20slang%3D%22en-US%22%3EI%20solved%20this%20problem%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1795330%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1795330%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F812940%22%20target%3D%22_blank%22%3E%40Farik7707%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20fixed%20your%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20handful%20of%20devices%20that%20run%20into%20this%20issue%20occasionally%20on%20whatever%20version%20of%20the%20Teams%20app%20and%20Windows%2010%20OS%20build.%20Our%20devices%20(Lenovo%20ThinkSmart%20Hub%20500)%20are%20on%20a%20wired%20connection.%3C%2FP%3E%3CP%3EOur%20workaround%3A%3C%2FP%3E%3CP%3E1.%20Sign%20into%20the%20local%20admin%20account%3C%2FP%3E%3CP%3E2.%20Disconnect%20from%20wired%20connection%3C%2FP%3E%3CP%3E3.%20Connect%20to%20a%20hotspot%20(external%20connection)%20and%20reboot%3C%2FP%3E%3CP%3E4.%20Once%20the%20device%20signs%20into%20Teams%2C%20reconnect%20to%20wired%20connection%20and%20turn%20off%20hotspot%3C%2FP%3E%3CP%3EOur%20workaround%20typically%20works%20for%203%20-%205%20days.%20It's%20as%20if%20it%20quits%20trying%20to%20sign%20in%20after%20that%20amount%20of%20time%20or%20getting%20blocked%20by%20our%20network.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1802254%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1802254%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F382665%22%20target%3D%22_blank%22%3E%40Jazzy23%3C%2FA%3E%26nbsp%3BHi%3C%2FP%3E%3CP%3E%3CSPAN%3EReinstalling%20.appx%20(Teams)%20to%20the%20old%20version.%20And%20then%2C%20Teams%20itself%20will%20update%20to%20the%20latest%20version%20and%20still%20work%20normally.%20Look%20my%20screenshot%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%221620581.png%22%20style%3D%22width%3A%20628px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F228200iA6AE2BC7FF15D8A7%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%221620581.png%22%20alt%3D%221620581.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1803260%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Cannot%20sign%20in%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1803260%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F812940%22%20target%3D%22_blank%22%3E%40Farik7707%3C%2FA%3E%26nbsp%3Bstill%20didn't%20work%2C%20screen%20looks%20different%20but%20still%20sitting%20at%20a%20%22Signing%20in...%22%26nbsp%3B%20prompt%20as%20before%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi,

 

We are trying to install our first Teams Rooms system. Though the system (Lenovo ThinkSmart Hub 500) is logging onto the SRS, it is not signing in to the Ms Teams.

 

I've checked the system logs but I could not detect any valid information:

{"Description":"Network status : Healthy. Exchange status : Connected. Signin status: Healthy. Teams Signin status: Unhealthy.","ResourceState":"Unhealthy","OperationName":"Heartbeat","OperationResult":"Fail","OS":"Windows 10","OSVersion":"10.0.17134.950","Alias":"abc@hiddenmailaddress.onmicrosoft.com","DisplayName":"TeamsRoom","AppVersion":"4.0.105.0","IPv4Address":"hidden","IPv6Address":"","IPv4Address2":"hidden"}

 

  • The account is active and has been tested on a demo unit before
  • No local admin account because it's being managed by Azure AD. 
  • Skype for Business and Exchange backends sign in but for some reason Teams doesn't.
  • E5 license attached to it.

 

I would really appreciate your ideas.

15 Replies
Highlighted

@WhizFi often this kind of thing comes down to some conditional access policies or other config thats refusing the Teams Room System. If you go into AzureAD and look up the useraccount, can you see any blocked login events and their cause?

Highlighted
Hi @WhizFi,

Have you assigned a Teams Meeting Room Licence? The following article may help.

https://blog.kloud.com.au/2019/02/21/enabling-microsoft-teams-meeting-rooms/

Let me know how it goes!

Best, Chris
Highlighted

@Christopher Hoard it need a team license, doesn't need the meeting room license specifically. It can just be a cheaper way to purchase the right licenses.

Highlighted

Hmm. That is true.

Highlighted

@WhizFiIf you just created the account, wait for a little while as sometimes it takes time to populate to Teams and I have noticed that time increasing lately.  Also as someone before pointed out, if you are using anything like Pyng Federate or another service to login, try bypassing that service for authentication if you can.  Nothing that you have posted stands out as the definitive reason you are having an issue though.

Highlighted

@Steven Collier You may be right. We are working on the Azure AD side at this moment. 

 

As there's no "reply to all" function in the forum, regarding the licensing etc. We already used this account to test on the evaluation unit and it worked without any problems. 

 

It has an E5 license attached to it. (I know, E3 was enough too).

 

Yesterday I managed to download the logs, but frankly I'm not sure what I am supposed to look for. 

Highlighted

Hi, we have noticed the same issue on several of of our devices.
Suddenly, we were not able to sign in to Teams, which worked perfectly all the time before.
We noticed that the time was not correct set up on the device. We fixed clock and activated 'internet time synchronization' and after reboot the device was able to log in again.

 

Checking time zones and time could resolve the issue.

Highlighted

@Franka Sander thanks a lot, we were having the same issue with our system. Log-in the admin session and making sure the time was synced solved it.

Highlighted

Hi

 

Unfortunately here we got the exactly same problem with our Logitech Tap Rooms System. Time and timezone is correct, conference room licence assigned correctly, conditional access rules are disabled for this user, Teams rooms app is updated to 4.5.37.0. Eveything has been set up in the cloud, still the teams login is shown as "unhealthy" while all other logins (Network, Exchange, etc.) are in a "healthy" state.

 

Microsoft support is not able to give any advice or solution for more than 1 month now. It's really annoying since I was creating the user several times with the SkypeRoomProvisioningScript and even first reset, then completely reinstalled the NUC device that's running the teams rooms app.

Highlighted

@MVo_CH 

Hi. I have the same problem

My config: Logitech Tap Rooms + Intel NUC

Highlighted

@Farik7707 I have almost the same issue except Skype for Business says disconnected and Teams is logged in but still have the same message at the top "Signing in..."

Highlighted
I solved this problem
Highlighted

@Farik7707 

What fixed your issue?

 

We have a handful of devices that run into this issue occasionally on whatever version of the Teams app and Windows 10 OS build. Our devices (Lenovo ThinkSmart Hub 500) are on a wired connection.

Our workaround:

1. Sign into the local admin account

2. Disconnect from wired connection

3. Connect to a hotspot (external connection) and reboot

4. Once the device signs into Teams, reconnect to wired connection and turn off hotspot

Our workaround typically works for 3 - 5 days. It's as if it quits trying to sign in after that amount of time or getting blocked by our network.

Highlighted

@Jazzy23 Hi

Reinstalling .appx (Teams) to the old version. And then, Teams itself will update to the latest version and still work normally. Look my screenshot 

 

 

1620581.png

Highlighted

@Farik7707 still didn't work, screen looks different but still sitting at a "Signing in..."  prompt as before