Using classic Outlook for Windows in business environments
Hi David Nguyen
According to my research, here is a checklist for your review:
Clear Cached Credentials & Reset WAM:
- Credential Manager: Open Windows Credential Manager and delete any entries starting with
MicrosoftOffice16,Outlook, orADAL. - Windows Settings (WAM): Go to Settings > Accounts > Access work or school. Find the M365 account, click Disconnect, and then Connect to re-add it. (Note: Do not disconnect the account if it is the primary Entra ID/Azure AD device join).
Force Modern Auth via Registry: Ensure Outlook isn't falling back to Basic Auth by verifying/adding these DWORD values:
-
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity- EnableADAL = 1
-
HKEY_CURRENT_USER\Software\Microsoft\Exchange- AlwaysUseMSOAuthForAutoDiscover = 1
Verify Tenant & Client Readiness
- Check Exchange Online PowerShell to ensure Modern Auth is enabled globally:
(Must be True).Get-OrganizationConfig | FL OAuth2ClientProfileEnabled - Ensure users are on supported Outlook versions.
Check Network & Conditional Access
- Network: VPNs, proxies, or SSL inspection can sever OAuth tokens. Temporarily bypass the VPN to test.
- Entra ID: Check Azure AD Sign-in Logs for the affected users. Look for "Interrupted" statuses, which often point to Conditional Access policies evaluating repeatedly.
Create a New Outlook Profile
If the issue is isolated to a few users, their Autodiscover cache may be corrupted. Recreating the profile via Control Panel > Mail > Show Profiles will force a clean OAuth connection.
Once configured correctly, users should only see one prompt per token lifetime. Outlook should remain connected silently in the background without loops.
I hope this helps and if you have any update, please let me know via comment section! Thank you.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.