Outlook keeps asking for password, the user types it in correctly, and two minutes later the same prompt is back. The status bar says Need Password or Trying to connect…, Outlook on the web works fine, and resetting the password changes nothing. The obvious fixes (new profile, Office repair, password reset) usually treat only the symptom. In most cases the real problem is the Windows sign-in broker that hands tokens to Office. Below is the order I work through now, using the steps and commands Microsoft documents, plus the checks I use to prove it is fixed.
Why Outlook Keeps Asking for Password in Microsoft 365
Current Microsoft 365 Apps do not keep your password themselves. On Windows 10 and 11 they ask the Web Account Manager (WAM) for a token, and WAM uses a per-user plug-in, the Microsoft.AAD.BrokerPlugin package for work or school accounts. If that package is missing, damaged or blocked, Office cannot get or renew a token, so it falls back to prompting you. Microsoft’s article on automatic authentication failures describes exactly this: Outlook goes into the “Need Password” state without any interaction because package information for the WAM plug-in or Live ID is missing.

When Outlook keeps asking for password, these are the causes I check, roughly from most to least common in my experience:
- Broken or missing WAM plug-in in the user profile (Microsoft.AAD.BrokerPlugin).
- Security software that blocks or removes the WAM plug-ins, or old Windows Filtering Platform (WFP) drivers that break the connection. Microsoft documents this in Can’t sign in to Microsoft 365 desktop applications.
- Stale cached credentials in Credential Manager after a password change.
- Hybrid Exchange with RPC: Outlook connects to an on-premises mailbox over RPC and to a Microsoft 365 mailbox at the same time, and never uses Modern Authentication for the cloud one.
- Policy, not a bug: an expired password, or a Conditional Access sign-in frequency setting that asks the user to sign in again on purpose.
Step 1: Rule Out the Service, the Account and Policy
Before touching the PC, I spend two minutes on the cloud side. Open Outlook on the web as the user. If Outlook keeps asking for password and OWA also fails, the problem is the account, not Outlook. Check Health > Service health in the Microsoft 365 admin center as well. During the Microsoft 365 November 2026 incident on November 12 and 13 (tracked as EX1550543), Exchange Online and Outlook were disrupted across many tenants, and reports on the outage were clear that nothing on the client needed fixing. Re-registering packages during an outage only adds noise.
Then look at the user’s Entra ID sign-in logs. Failures with a clear reason, such as an expired password, MFA not completed or a blocked Conditional Access policy, point you to the account. If the password itself is the problem, my SSPR troubleshooting guide covers the self-service reset side. If the logs show successful sign-ins and Outlook keeps prompting for credentials anyway, carry on with the client steps.
Step 2: Clear Stale Office Credentials
Old entries in Windows Credential Manager are a classic reason Outlook keeps asking for password right after a password change. First list what is there, from a normal (not elevated) PowerShell window as the affected user:
cmdkey /list | Select-String 'MicrosoftOffice'Code language: JavaScript (javascript)Then open Control Panel > Credential Manager > Windows Credentials and remove the generic credentials whose names start with MicrosoftOffice16_Data (or MicrosoftOffice15_Data on older builds). Close all Office apps first. Outlook recreates what it needs at the next sign-in. I prefer the GUI here because it shows which account each entry belongs to.
Step 3: Repair Microsoft.AAD.BrokerPlugin When Outlook Keeps Asking for Password
This is the step that fixes the problem most of the time. Because the WAM plug-ins are installed per user, run these commands as the affected user. Microsoft’s security software article is explicit that diagnosis should happen in the user’s context, not as an administrator. (The older authentication failure article says to open PowerShell as Admin. If the admin account is a different user, the check will look at the wrong profile, so I follow the newer guidance.)
First, check that both packages are registered:
Get-AppxPackage Microsoft.AAD.BrokerPlugin
Get-AppxPackage Microsoft.Windows.CloudExperienceHostCode language: CSS (css)If both return a package, test whether the plug-ins actually start. Each command should open a Work or school account window (the first one) or a Microsoft account window (the second one):
explorer.exe shell:appsFolder\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy!App
explorer.exe shell:appsFolder\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy!AppCode language: CSS (css)If a command returns nothing or a window does not open, re-register the packages. This is the command from Microsoft Learn, and it only registers the work-account plug-in if it is missing:
if (-not (Get-AppxPackage Microsoft.AAD.BrokerPlugin)) {
Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown
}
Get-AppxPackage Microsoft.AAD.BrokerPluginCode language: JavaScript (javascript)When the package is listed but broken (the window does not open), Microsoft’s procedure registers both packages without the if check:
Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown
Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdownCode language: JavaScript (javascript)-ForceApplicationShutdown closes apps that use the package, so save the user’s work and close Outlook first. Then sign out of Windows and back in, open Outlook and sign in once more when asked. If Outlook keeps asking for password after that single sign-in, move on to Step 4.

Step 4: Check Security Software and WFP Drivers
If the fix works but Outlook keeps asking for password again the next day, something is undoing it. Microsoft links this pattern to security software and old WFP drivers that block or remove the WAM plug-ins. You can see the evidence in the Application log as AppModel-State warnings or errors that name the broker package. This quick filter finds them:
Get-WinEvent -LogName Application -MaxEvents 3000 |
Where-Object { $_.Message -like '*Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy*' } |
Select-Object TimeCreated, ProviderName, Id, LevelDisplayNameCode language: JavaScript (javascript)Messages such as “Repair for operation LocalSettings against package Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy with error” mean the plug-in was damaged or tampered with. Microsoft’s documented approach is to test without the security product, reinstall the plug-ins, monitor for 48 hours, and then work with the vendor on exclusions. These are the package and folder exclusions Microsoft lists:
- Packages:
Microsoft.AAD.BrokerPlugin_cw5n1h2txyewyandMicrosoft.Windows.CloudExperienceHost_cw5n1h2txyewy - Folders:
%windir%\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy,%localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy, the matching CloudExperienceHost folders,%localappdata%\Microsoft\TokenBroker,%localappdata%\Microsoft\OneAuthand%localappdata%\Microsoft\IdentityCache - Processes:
Microsoft.AAD.BrokerPlugin.exe,backgroundTaskHost.exefor those two packages, and thesvchost.exeinstance that hosts the TokenBroker service
Until the exclusions are in place, Microsoft suggests re-registering the plug-ins from a logon script or background PowerShell script as a temporary mitigation. My rule: if the fix keeps wearing off and Outlook keeps asking for password again, look for whatever scans or roams %localappdata%, such as profile tools on RDS and VDI hosts.
Step 5: Hybrid Exchange and the AlwaysUseMSOAuthForAutoDiscover Key
There is one scenario where Outlook keeps asking for password even after the WAM repair. Outlook connects to a primary mailbox on an on-premises Exchange server over RPC, and also to a mailbox in Microsoft 365, or the mailbox was just migrated from such a server. According to Microsoft’s Modern Authentication article (original KB 3126599), Outlook then limits itself to authentication schemes that RPC supports, so it never uses Modern Authentication for Microsoft 365 and prompts instead. The documented fix is a per-user DWORD. Close Outlook first:
reg add "HKCU\Software\Microsoft\Exchange" /v AlwaysUseMSOAuthForAutoDiscover /t REG_DWORD /d 1 /fCode language: JavaScript (javascript)The key forces Outlook to use Modern Authentication for web services such as EWS and Autodiscover. Microsoft notes that Office 2016 needs no update for it to work. For Office 2013, Outlook and MSO must have the December 2015 updates or later. You can push AlwaysUseMSOAuthForAutoDiscover with Group Policy Preferences or an Intune remediation script. If those devices also fail to enroll, my Intune enrollment error 80180014 guide may help.
What Not to Do: Disabling WAM or ADAL
Many forum answers to “Outlook keeps asking for password” still tell you to set registry values that disable WAM or ADAL so Office falls back to its old sign-in. Microsoft says plainly that disabling ADAL or WAM is not supported as a fix for sign-in or activation problems. It moves Office into a legacy configuration and can cause new issues later. If someone added those values to your image years ago, remove them, then repair the broker as shown in Step 3.
How to Verify the Outlook Keeps Asking for Password Fix
I do not close the ticket until three checks pass as the user. First, the broker package is present and healthy. Second, on Entra joined or hybrid joined devices, the user has a Primary Refresh Token. The dsregcmd troubleshooting guide explains the AzureAdPrt field. Third, nothing stale is left in Credential Manager:
Get-AppxPackage Microsoft.AAD.BrokerPlugin | Select-Object Name, Status
dsregcmd /status | Select-String 'AzureAdJoined|AzureAdPrt '
cmdkey /list | Select-String 'MicrosoftOffice'Code language: JavaScript (javascript)
Then leave Outlook open across a lock and unlock and a network change, such as VPN on and off. If the status bar still shows “Connected to: Microsoft Exchange” an hour later and the prompt has not come back, the job is done. If the user also complains that search stopped working after all the profile changes, my Outlook search not updating fix covers that.
Outlook Keeps Asking for Password: Quick Checklist
- OWA works and Service health is clear. Otherwise it is the account or an incident, not the PC.
- Remove the
MicrosoftOffice16_Dataentries from Credential Manager. - As the user, check and re-register
Microsoft.AAD.BrokerPlugin, then sign out and back in. - Fix keeps wearing off? Look at AppModel-State events and add the security software exclusions.
- Hybrid with RPC? Set
AlwaysUseMSOAuthForAutoDiscover= 1. - Never disable WAM or ADAL as a “fix”.
Why does Outlook keep asking for my password when it is correct?
When Outlook keeps asking for password in Microsoft 365, the usual cause is not the password but the Web Account Manager (WAM) plug-in that gives Office its sign-in tokens. If the Microsoft.AAD.BrokerPlugin package is missing, damaged or blocked by security software, Outlook cannot renew its token and falls back to prompting.
How do I re-register Microsoft.AAD.BrokerPlugin?
As the affected user, run Add-AppxPackage -Register “$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml” -DisableDevelopmentMode -ForceApplicationShutdown, then sign out and back in to Windows and sign in to Outlook once.
What does AlwaysUseMSOAuthForAutoDiscover do?
It is a DWORD under HKEY_CURRENT_USER\Software\Microsoft\Exchange. When set to 1, it forces Outlook to use Modern Authentication for web services such as EWS and Autodiscover. Microsoft documents it for hybrid setups where Outlook also connects to an on-premises mailbox over RPC.
Should I disable WAM or ADAL to stop the prompts?
No. Microsoft states that disabling ADAL or WAM is not supported for fixing Microsoft 365 sign-in or activation issues, because it moves Office into a legacy configuration. Repair the WAM plug-in instead.
Why does the fix stop working after a day?
Security software or old WFP drivers can block or remove the WAM plug-ins again, and profile tools can damage them. Check the Application log for AppModel-State events that name the broker package, then add the package, folder and process exclusions Microsoft lists.
References
Microsoft Learn: Fix authentication issues in Microsoft 365 apps when you try to connect to a Microsoft 365 service
Microsoft Learn: Can’t sign in to Microsoft 365 desktop applications
Microsoft Learn: Outlook prompts for password and doesn’t use Modern Authentication to connect to Microsoft 365
Microsoft Learn: Disabling ADAL or WAM to fix Microsoft 365 sign-in or activation issues not supported
Microsoft Learn: Troubleshoot devices by using the dsregcmd command






