I feel like this issue is getting progressively worse as the fix used to be connection status shows disconnected clearing the credential manager or if it was bad uninstalling the entire Office Suite, clearing all traces and reinstalling and now we are seeing nothing helping it. Have looked all over and people have all sorts of possible solutions, but nothing we found to resolve the issue and get a new issue daily and just keep going through until it eventually works. Problem doesn’t just happen on PC’s connected to the internal network, but can happen when a laptop is remote and connected via external wifi or mobile hotspot. Today was the first time in about 2 months that I had the issue. It happened right before lunch, locked my machine, went out for lunch, came back, and logged in, this time successfully.

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 fix MFA prompts not working 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:

When we opened the old, existing profile it didn’t ask for ANY authentication, it just started working. Office 2016 is already Modern Authentication aware so APP passwords are not required. Native IOS and Android Mail apps will require the APP password or users can use Outlook for IOS/Android which is Modern Auth aware. FYI outlook 2013 requires a registry setting to work with MA. Where I work, we have a new sandbox tenant to make tests before FixTechGuide Windows update Outlook fix official deployment. I tried registering the account to my Outlook Desktop app and for some reason I am in a credential prompt loop that always asks for it anytime I input my password.

• 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.
• Problem doesn’t just happen on PC’s connected to the internal network, but can happen when a laptop is remote and connected via external wifi or mobile hotspot.
• Have looked all over and people have all sorts of possible solutions, but nothing we found to resolve the issue and get a new issue daily and just keep going through until it eventually works.
• Not sure if it has to do with being an onmicrosoft.com account that has no domain assigned to it.
• I have a valid MS 365 subscription that includes 5 device licenses.
• 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.
• Checking the Account in Word showed the correct authentication and subscription.
• Office 2016 is already Modern Authentication aware so APP passwords are not required.

Changing Outlook Security Settings:

If this box is greyed out or disabled then you need to reset the Windows Credential Manager first. @Microsoft, given the level of attention the community has given this issue, I hope you come up with an update soon. We have been experiencing the exact same issue for months now.