Forum Discussion
MS Teams logout issue
I am trying to figure out an issue with MS Teams, and not having much luck, so I'm wondering if anyone else has encountered this before.
We have a shared PC in a conference room that people will use to log into a shared user account, and then into their personal Teams account during their meeting. The problem is that some users' accounts seem to be cached on the PC, and all you need to do to log into their account is enter their email, no password required.
I have tried the following, with no luck so far:
- Completely cleared out credential manager
- Deleted the contents of %AppData%\Microsoft\Teams
- Deleted the contents of HKLM\Software\Microsoft\Office\Teams
- Uninstall/reinstall with Revo Uninstaller to also remove leftover registry/folder items
I finally reimaged the computer I was testing on, which of course fixed the issue, but there has to be a less invasive solution that I just haven't found yet.
Thanks in advance.
- I realize your post is old, but this was the first result that popped up when I searched this issue so I thought I would share my solution here for anyone else who comes looking.
In Windows 10, open Settings -> Accounts -> Access work or school
Click on the account you want Teams to forget, then click Disconnect.I tried deleting/disconnecting my school account but teams on my computer still won't let me logout. Any ideas? Thanks Erin_Rose5
- this is how to disconnect, but the real issue is how to stop windows from adding the Teams login account into "email and accounts" in the first place.
- I'm having this issue too.. For a public facing application, this is abysmal... Logging out of an app is basic functionality.
Dear awarwick,
thank you for already bringing up this issue. I just stumbled on the same problem, as we use a shared laptop in our university group for teaching activities. As you already pointed out, the critical point is whether you accept or decline to let your company manage your account while logging in for the first time in Microsoft Teams Desktop. After accepting this option I failed in a similar way to log out. I am a bit surprised that Microsoft does not provide an intuitive way to resolve this issue already in Teams or the login window.
I am not a specialist, but could resolve the issue for me in the following way (...after some time):
Click "Start" -> click "Settings -> click "Accounts" -> choose "Access work or school". There you can delete your account from the system.
Best regards,
Johann- it works, If the users have enough rights
this is a risk for us if the users do not do this, so we use the logoff script- I appreciate Your efforts but i won't use Your script. Your script is mere third party workaround. Nothing more. Not a fix for a problem. I am not going to add, modify or delete any entries using tdp scripts, not in case where desktop app has an explicit function to logout user - function which doesn't do what it should.
awarwick Hello, you can prevent the pre-population of the UPN with a registry key.
Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\Teams
SkipUpnPrefill(REG_DWORD)
0x00000001 (1)https://docs.microsoft.com/en-us/microsoftteams/sign-in-teams#windows-users
ChristianBergstrom This does not actually solve the problem I mentioned, it only prevents Teams from auto-populating the username.
Through a little bit more testing, I've narrowed it down a little farther. It as long as I click on "No, sign in to this app only" on the attached image, my login is not remembered and I need to enter a password every time I log in. However, as soon as I click OK in this window, whether the "Allow my organization to manage my device" checkbox is checked or not, my password is saved on this Teams login going forward, and there's no way to reverse it short of fully reimaging the computer (at least that I have found so far). And until I reimage the PC, anyone can log into my Teams account using only my email address, no password required.
Also note that this is related to our conference room PCs, which use a shared Windows login, so I'm guessing you might not have this issue without shared logins, I just haven't tested that yet since it wouldn't really help our specific scenario.
awarwick Hi, just to be clear as this hasn't been mentioned. Are these users manually signing out from Teams as well? (top right corner). Teams uses modern authentication and the process and different scenarios such as MFA, domain-joined or not etc. are being described in the previous link I attached. Perhaps this is already taken into consideration but need to ask.
Hi awarwick
It is unbelievable we are even having this conversation. This is such a basic issue and one that would be so easy to test and fix if you were Microsoft - they have the source code.
I have noticed there are several different sign out boxes in teams (some on the same page) and in testing this problem they appear to work differently. It is unacceptable from a quality point of view (not to mention a CX perspective) for two identical menu options to operate in a different way. And if that wasn't the intention, then why have the two on the one screen?
I experience this problem (cannot log out of teams) on a MAC. I have two emails accounts I use for different teams families. This problem presents itself in a few different ways.
Sometime I even get a screen that invites me to enter one email address and password and then TEAMS logs me into my OTHER email's account. Microsoft seem to have an issue with identity where people writing the code make the incorrect assumption the whole world works with ONE email account. I had the same issue with federated identity in Queensland Health a few years ago - visiting medical officers ended up with two email accounts (their private one and the hospital's one).
I don't want workarounds for this. I want the problem fixed. It's just basic functionality that should just work.
Peter Grant
- Hi mate,
No I couldn't find a workaround. Sorry I cannot help you.
But for Microsoft's benefit I found another issue for people with more than one email account using TEAMS. When you do eventually manage to get out of one account and into another (see above that's not easy) there are still links that point back to the first account. For example, if you hit a link to enter Sharepoint TEAMS will tell you your email address (the one from my other TEAMS account) is not registered for Sharepoint in this account you are trying to enter. It remembers the WRONG one from the earlier login.
There is a SERIOUS multi company design issue here. And it's not just for shared computers in a university as described above here. It applies to EVERY freelance consultant who has clients who want them to use their own TEAMS solutions. There are probably on 1,000,000 of these people worldwide.
Microsoft, I don't want a workaround. I want this fixed and the product working properly.
BTW every accounting system since the beginning of time has been designed to be multi-company. Perhaps the computer science courses at US universities should teach some business courses before they let people loose on critical business systems design. Just a thought.
Peter_Grantit's exactly what I said earlier. We can use workarounds, ok, but it is ridicule considering who brands Teams. I can use workarounds for small free apps written by nobody. And not able to log out is not the only problem i have met. The problem where application closes itself right after start without any explicit error is also haunting it. The best way to deal with both problems is just remove all Teams data placed in users folder.
- I installed TEAMS on new computer and had the same problem. TEAMS just isn't deigned for multi company (multi identity) access to multiple teams. There is no workaround for me. My computer doesn't have a register I can edit - thank god! So all the help above is useless.
- I had the same issue. to fix it, opened up an office application (MS Office-Word) and then clicked on my name on the top-right corner and noticed that I have multiple login. So removed them all, except the one that is needed. close the application and then the issue was resolved.
- The problem is still there....
