Forum Discussion
Bug - Teams Android-Unable to switch orgs
I'm guest in multiple orgs. As of today I'm no longer able to switch from my home org into any of the orgs I'm a guest in. I tap the guest org, the app flashes, and I remain in the original home org.
Have done the usual troubleshooting: cache clear, reset database, clear app data, uninstall/reinstall.
This is an Intune managed device, with a work profile, fwiw.
Anyone else seeing this before I submit a bug report?
Bob
- This may have been fixed with a recent Teams update. I just updated apps on several devices and Teams version 1416/1.0.0.2021062302 was installed and I'm once again able to switch among orgs with our registered/managed devices. Can anyone else corroborate?
33 Replies
- I am a guest user in 2 different organizations. One organization which doesn't have device registration policy is working fine for me. But the other organization that has device registration policy is asking me that your organization required your device to be registered. When i tap yes, its taking me to https://portal.manage.microsoft.com/ and then its showing you are not authorized.
- A year later, not working for me. Latest version, device is not registered. Not able to switch organizations.
Same, I am helping set up a volunteer Teams for one of our Clients and am testing it with them to get the functionality down. this is quickly becoming a headache. If I log in only with the same account then access is normal and I can toggle between my org and theirs. But no matter which routine or hoola hoop that was suggested through this thread I try, I cannot seem to access their Org on my Android app. Ralf_Longwitz
- On 5/25, I received an update to Microsoft Authenticator (version 6.2105.3263) that seems to have fixed the issue. Switching orgs is now working. Can anyone else confirm the same?
- Same here. Seems like now is working as expected 🙂
- This may have been fixed with a recent Teams update. I just updated apps on several devices and Teams version 1416/1.0.0.2021062302 was installed and I'm once again able to switch among orgs with our registered/managed devices. Can anyone else corroborate?
- Cool, so now ThereseSolimeno selected this answer as best response, without giving any kind of answer or support.
No, this is not fixed and there are plenty of users with the same problem, so please, don't try to close it before it is solved and confirmed. That's not how things should work- ThereseSolimeno
Microsoft
Hi davidarema A "best response" is not necessarily an answer or a solution - it is the best response available for the time being, which in this case refers to the several comments that the issue repaired itself with the new update.
As it happens, I did report this post to our mobile PM, which he found interesting and will share with the developers. You might also want to check the Uservoice feedback forum to see if anyone reported this and if not, you can open your own ticket and allow others to vote on it as well. That site is the best vehicle for communicating bugs (or requesting features) directly to the engineers (this forum is mostly for user interaction, tips and tricks). Thank you for being a member of the community.
MTSBob is it still working for you? I checked this morning and it worked, but now again bug is happening 😞
- Oh geez. Yes, at the moment, on my 2 devices (Samsung Galaxy S20 and Surface Duo) both are working, but I haven't checked in with others yet.
bjmEW Just to report: I have the same version, but the problem persists. Hoping that the solution is somewhere in the backend systems and just hasn't propagated to all tenants yet.
I have a 14 person engineering team impacted by this issue right now (12 Android users, 2 iOS people that work fine), all client communications are negatively impacted.
- Same problem for us... All our organizations android phones stopped working, and we can't switch over organizations, maybe someone gets any solution from MS?
- Ok, we've now had several people confirm this behavior. I had submitted this issue a while back, but have gotten no reply. I have no idea if it's a known issue, whether it was received, if it's being worked on, if it's low priority, if it's "not really a bug" etc.
- Same here, unregistering device from Authenticator works as expected, but on the other hand, Outlook stops working prompting to log in, so is a choose between Teams and Outlook.
I have even tried with previous Teams versions, and same issue occurs.
This discussion is 14 days old and we had not any answer from Pernille-Eskebo 😕- I use the Blackberry Email client rather than Outlook. It prompted me once for creds and MFA after I unregistered but has been fine for a couple of days since then. Workable solution for me until MS sorts this nonsense out. I am not holding my breath.
- Same issue here.
- Same issue here.
- I am experiencing the same issue. Did anyone find a solution yet?
- No, it still is not working for me either. I reported it a week ago. I find this stuff hard to believe. I would expect this to impact thousands (if not more) users. Maybe we're the only three people in the world with managed devices who use Teams as guests. /s
- I noticed the same issue today and found an older thread from 2019 referencing a correlation with having the device registered with your home organization *in the Authenticator app*.
I just "Unregistered" the device from Authenticator, and I'm able to switch to a Guest org (Microsoft in this case) now.
This did not affect my Intune compliance for enterprise app/data access but presumably it means I can't use the Authenticator app for Passwordless anymore if I want to be able to switch orgs in Teams. Seems like a bug...- Update -- I was wrong about the Intune compliance not being affected.by unregistering from Authenticator. My enterprise apps did soon after require me to re-register the device in Company Portal, and switchingOrgs in Teams broke again.
