I feel like this issue is getting progressively worse as the fix used to be diagnose Office activation conflicts 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 Outlook Stuck on Synchronizing Folders the profile and clearing the credential manager.

Loop of 'Sign in to your account'.

I had this exact issue on another machine, that after 2.5 hours on the phone with MS support (via Zoom), the solution was to uninstall MS Office 365 and reinstall it. Yeap, you describe it exactly and unfortunately we still don’t have an answer. Closed the window without entering anything and Outlook returned to ‘Connected to Exchange’. I created a new Outlook profile, and then the old one started working. I wonder if the compuer cached a new logon token or something that the old Outlook profile could use. Also, during the new profile creation, I was only prompted for a password and not for MFA.

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 Microsoft Outlook Email Repair Tool Online 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.

• 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.
• I do NOT have this issue with the other laptop, an iPad, a MacBook Pro and tablet.
• We had the issue where Outlook 2016 kept prompting for a password for an Office 365 user whose laptop was connected to their Office 365 account using Windows 10 Pro.
• In each case the fix has either been one of the above items or a combination of them.

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.