Stuck in a login loop after password change
I recently change my system password, with MS Teams is already up and running in the background. I open Teams to check new messages, and it locks the app with the pop up "Can you please sign in again? Sorry for any inconvenience. Login Now"
I click Login Now but all it does is restarting MS Teams and show me the same message. I am unable to re-authenticate. I've tried restarting the application, that didn't work.
I had to right click on the systray icon to logout and re-login. I should be able to re-login when the app prompted "Login Now"
Thanks Dave Poole, that worked.
For Mac users you will need to delete a keychain entry called: "Microsoft Teams identities cache"
Thanks Dave Poole, that worked. I wasn't getting the field for a password when I clicked sign out. Putting some extra junk in my email address took me to a page that asked for an email address, and then a password after that.
Same thing happened to me on iMac today. Endless loop, luckily signing out in the task bar solved it, until the next time. Microsoft on Mac - I can understand there are conflicts, but many of you post from PCs, and that is really disturbing.
Dave Poole's fix worked a treat for me too - thank you Dave!
Dave Poole's fix worked - thanks Dave!
Uninstall the teams and reinstall it. It works for me.
Dave Poole commented
I found an unconventional fix to this:
1. Whilst MS Teams is open, right click in System Tray and hit sign out.
2. You will then be taken to a login page with your email address autofilled. Deliberately enter an INCORRECT email address (.ukk or .comm) and hit sign in.
3. You should then be taken to a different login window, where you have the opportunity to re enter your email, which should then take you to a password window where you can complete your new credentials.
It's weird, simply clicking sign in when my email address was autofilled kept me in the loop, but entering the wrong one worked. I also went through some of the other suggested steps like clearing my generic credentials- so it's possible you may have to do that as well.
Stil happening, I'm currently stuck in this loop and the logout through taskbar workaround dosnt seem to be working, why organisations choose to use this I don't know. Although I have heard their marketing at the conferences is very effective too bad the software isn't.
Just had the same issue; right-clicking taskbar and going to Sign Out worked.
Consultants require federation, we login to Skype for Business, then we communicate and work with dozens of organizations at a time. We also login to many many O365 systems on any given day, the MS login capabilities are the worst of any platform I've used, and this has been going on for years. Today, I login to Skype for Business and it not so gently redirects me to Teams, and I'm in a login loop and can't login. I'm afraid to login and learn I can't federate with all my clients too. Just more horrible user experience. Honestly, fed up with MS and their identity systems (don't get me started on the number of redirects you go through just logging into O365, Azure, etc...). This is an area where MS is lagging, definitely not leading.
I had the same problem just now. Had to right click the taskbar icon and sign out. Took 3 tries before i got it to finaly sign me out. Then i could log back in again. Needs a fix ASAP
This has been known since 2017 and is still not fixed? Do they consider this to be "per design" for some reason?
Just encountered this on a colleague's notebook after she changes her Windows password (before it expired). The workaround of signing out and back in via the status bar icon worked.
One of our user is experiencing this.
John Jordan commented
Eric's solution didn't work for me, as the taskbar icon never showed long enough for me to right click and sign out. Even after deleting all of the credentials in the credential manager. I did find a solution that worked for me at the following link:
Terra Whitmeyer commented
Same, just happened to me.
Farbod D commented
Also had the same problem. Followed solution posted by eric and it's working now. Thanks!
Justin Valdez commented
Just had the same problem. Microsoft REALLY need to sort this out.
i had the same problem. OP's fix with manually signing out on the systray worked for me, but this isn't acceptable.