Forum Discussion
Switching organizations in Teams desktop client
Hi jaybee1615 ,
There are issues with O365 today, its due to lots of demand on Office 365 from all the remote workers in Europe.
Expect a few more issues until the bottle necks are found and ramped up by Microsoft.
Andy
jaybee1615, et. al:
I can confirm this issue in two different small business tenants where I'm global admin plus a personal tenant I'm owner of. I've been only logged into one of the work tenants for the last couple months, but the org switching control I used many times before is missing from my Teams desktop client. It used to be in the upper right corner just left of the account profile avatar.
Since I already had a Teams-related case open for another matter, a Microsoft support rep got to see this issue first-hand on my PC. I opened a Teams browser instance and organization switching was missing there as well. Support had already provisioned a test tenant and invited me as a guest so we could test our original guest login issue. We also wanted to see how a guest invite would impact tenant switching.
Some interesting and, in some cases, troubling things happened after I clicked on Open Microsoft Teams in the invitation:
- A Teams login page opened in the browser as expected. We chose to open in the desktop client. Windows switched to desktop Teams app, but nothing happened. There was no prompt to switch organizations.
- I went back to the browser instance and told it to open Teams in the web browser. It opened a new tab, logged me in successfully under my work profile and the organization switching control appeared where it should be in the upper right!
- I refreshed the Teams web tab that had already been open (see 2nd paragraph above) and an org switching control suddenly appeared in that instance as well.
- In an effort to troubleshoot the desktop client, we quit out of the running instance and restarted Teams. Still no org switching control. Next I logged out and back in. Still no control appeared.
The Microsoft support rep was equally surprised. After checking for known issues and coming up empty, he promised to check with his colleagues and research this further. I sent him a link to this thread.
Teams Desktop client version: 1.3.00.13565 (64-bit)
Browser: Microsoft Edge ver. 85.0.538.0 (Official build) dev (64-bit)
Windows 10 Pro ver. 10.0.19041 Build 19041
Note: The article posted by JackPaystarAccount shows the difference between external (federated) and guest users, but that wasn't a factor in this case. We were working strictly with non-federated member and guest user access.
Mike_ETC sorry no resolutions here. I am just adding that unfortunately I have the very same issue as you have so well described. I know my colleagues are having hard times with it as well.
Since 2 years, I have had access to two Teams:
1. My employer's
2. My customer's
Both of them are visible on desktop and in browser just like they are supposed to.
Now I have an invite to a 3rd team, let's say from Microsoft. I can open Teams in browser and can see the dropdown containing three options. However, on the desktop I can still see only the original two options. It does not help if I shut down Teams completely and restart again.
If Teams desktop app is running and I click "Already have the Teams app? Launch it now", nothing happens. However, if I close Teams and click the same "Launch it now" link on the browser, the desktop app nicely opens in the new Microsoft organization, and I can see all three options in the dropdown with the Microsoft team selected. New problem: when I switch back from Microsoft to either one of the original two options, the Microsoft option disappears for good. The very same happens also within the browser client.
I need to add that I have a colleague who currently has access only in our employer's Team (number 1 in my list). She is struggling with the same issue with me when she is trying to add our common customer in her Teams (option 2 in my list). That's the very same customer that I have visible in my dropdown menu without issues since 2 years. Something must have changed which has broken this functionality.