12-27-2016 03:59 AM
12-27-2016 03:59 AM
I recently noticed that many Office 365 consumers are facing difficulties in loading Teams when they are using their corporate networks. When they launch Teams desktop app or Teams service on a browser, they are able to successfully authenticate and the above ‘Loading Microsoft Teams’ image appears. After some time, they are presented with the error message: Doh! Something went wrong.
Microsoft Teams is based on the consumer version of Skype, not Skype for Business. It makes use of various *.skype.com URLs for loading components, etc. Since most of the corporate networks have blocked *.skype.com domain, Microsoft Teams is not loading even after successful authentication. In this case, IT administrators need to do additional configuration work, such as updating firewall policies, to ensure employees can fully use Microsoft Teams.
I really hope Microsoft switches to some other domains so that anyone can use it inside corporate network without any work from their IT teams.
12-27-2016 05:48 AM
12-27-2016 06:17 AM
12-28-2016 11:57 PM
12-31-2016 02:55 AM
07-22-2019 01:19 AM
We are always fighting setting firewall rules to enable Office365 functionalities from inside our LAN configuration.
We are also discovering configuration limitation in Teams due to users not completly migrated to the cloud (we have Lync/S4B on premise server, Exchange onpremise server)... not easy to coordinate all the innovation in Office365 with our internal infrastructure and policies :(
With users completly migrated on O365 (S4B+Exchange) the Teams functionalities are ok, a nightmare in a mixed user configuration.
Right now we migrated the affected users and it is working.
07-22-2019 03:06 AM
07-15-2020 07:40 AM
I run into this issue multiple times in different situations and all the hotfixes out there help sometimes but more and more less.
What haved worked for me is going to %LOCALAPPDATA%\Packages where you should find a folder "Microsoft.AAD.BrokerPlugin_" with some random letters an numbers at the end.
Inside is a folder called "LocalState" remove this folder and create a file called LocalState but remove the extension. So for example create a textfile.txt and call it LocalState.
If the folder got created again, then you did something wrong.
After this start Teams and you will have to enter your email adress and maybe it will show you this login screen twice, but after the second one you are able to login again and use Teams.
Worked for me on all users i got this error before.
So it seems to have something to do with the AD Broker Plugin.