But by mistake, I turned on MFA for the admin account, and then when I logged in again, it prompted me to use Microsoft Authenticator. The bad thing is this account was not registered with Microsoft Authenticator, so I couldn't see any codes Outlook profile repair and recovery steps in the authenticator. And there were no other login options, and I was stuck in a login loop. This is now the 2nd machine that presents the same issue. I have a valid MS 365 subscription that includes 5 device licenses. On the main machine where I have been using the suite, now my account is deactivated and if I try to authenticate, it looks like it works but then get the "Fix", "Authenticate", "Activate" or "Resolve" buttons, all of which do nothing.

Outlook credential prompt loop

In the instances that this occurs the effected user is not new to MFA but has been running it for at least months. The problem appears to randomly affect users (I’ve had it affect myself once too), and the only solution appears to one of (or a combination of) the options in the OP. Out of 140 staff the problem seems to occur once every 2-3 weeks on average. In this case are you saying that there is a password prompt for the users credentials? Clear the Windows Credential manager or recreate the users Outlook profile. In fact if you just turned on MFA and you were not using MFA before you usually end up having to rebuild flush DNS and re-sync Outlook the profile and clearing the credential manager.

Loop of 'Sign in to your account'.

Which to me sounds like the issue is service side, not client side. A vast community of Microsoft Office365 users that are working together to support the product and others. I’ve seen this happen when the time and or date is wrong on the machine. It’s not caused by an out of sync MFA prompt as I have personally looked at a number of cases with the user as stepped through it. In each case the fix has either been one of the above items or a combination of them. There doesn’t appear to be any pattern to the issue occurring or the problem being limited to any specific computer or user.

Resetting the Windows Credential Manager:

I have contacted my organization and everything looks alright from their end.. I went as far as getting a new device but it did not cut it. When I try to sign again it will be stuck in sign in loop with the message " Taking you to your organization sign in page" after I have logged in on my company site... When I log in to my account at first from a new device or after a while, it stays signed in and I can work peacefully for about an hour, then it automatically signs me out. Or, any suggestion on how to fix this issue, even Fix Outlook and Office 365 Errors 2025 better. I do NOT have this issue with the other laptop, an iPad, a MacBook Pro and tablet.

• We’ve got a support case opened with Microsoft on this one but it’s been open for about 3 months.
• I am unable to stay signed in to my work account on Teams, Outlook, Office365 for more than 5 minutes.
• We have been experiencing the exact same issue for months now.
• Create your account and connect with a world of communities.
• The user had Office 2015 and Office 2016 credentials and Teams credentials that we deleted.
• We too have been seeing this more and more, all W10 on O365, although we use Okta as our MFA.
• Initially, this account didn't have MFA turned on, and I was able to log in.

Changing Outlook Security Settings:

Hi, my office 365 account used to work with my desktop apps, I have confirmed with my admin system twice already that I have the appropriate license and everything is enabled but i keep getting stuck in this loop. We are looking at using conditional access policies where a user with a Domain joined PC is not prompted for MFA. Right now we have it set to prompt when a user is not on any of our corporate networks or they are using a mobile device. The user had Office 2015 and Office 2016 credentials and Teams credentials that we deleted. We checked with Word that the account was connected–it was and the we opened Outlook and it immediately connected. We too have been seeing this more and more, all W10 on O365, although we use Okta as our MFA.