Prevent Outlook from connecting to Office 365
An Outlook client with a profile pointing at an on-premises Exchange mailbox can suddenly start showing a Microsoft sign-in prompt that never accepts the credentials. The status bar reads Trying to connect, and the mailbox never connects even after a new profile is created. In this guide you will learn why Outlook forces a connection to Microsoft 365 and how to prevent Outlook from connecting to Office 365 with a single registry key.
The sign-in prompt keeps coming back
The Microsoft sign-in window appears every time Outlook starts. Entering the email address and clicking Next shows the message This username may be incorrect, and the mailbox stays disconnected.
The mailboxes are not in Microsoft 365 at all, so the prompt is a side effect of Outlook trying the cloud first.
Why Outlook connects to Office 365
Newer Outlook versions force a direct connection to Microsoft 365 during autodiscover before they consult the Exchange Server on-premises URL. This applies to Outlook 2016, Outlook 2019, and Outlook for Microsoft 365. When a new domain is added to the Microsoft 365 tenant, Microsoft treats the domain as cloud-hosted and Outlook tries the Microsoft 365 autodiscover endpoint, even though the mailbox lives on the on-premises Exchange Server.
The registry setting ExcludeExplicitO365EndPoint tells Outlook to skip the explicit Microsoft 365 endpoint and use the on-premises autodiscover service instead.
Add the ExcludeExplicitO365EndPoint registry key
Create the registry value on each affected client. The registry path depends on the Outlook version, which is 16.0 for all three current versions.
Verify the connection to Exchange on-premises
Restart Outlook and confirm the sign-in prompt is gone and the mailbox connects to the on-premises server.
You do not have to recreate the existing profiles after adding the registry key.
Remove the key after migrating to Microsoft 365
Once mailboxes are migrated to Microsoft 365, Outlook should be allowed to use the Microsoft 365 endpoint again. Delete the ExcludeExplicitO365EndPoint value from the clients when the migration is complete so autodiscover works normally for cloud mailboxes.
Frequently asked questions
Why does Outlook keep asking for Microsoft 365 credentials?
Outlook forces a direct connection to Microsoft 365 during autodiscover and skips the on-premises Exchange Server autodiscover URL.
Which Outlook versions are affected?
Outlook 2016, Outlook 2019, and Outlook for Microsoft 365.
What does ExcludeExplicitO365EndPoint do?
It tells Outlook to skip the explicit Microsoft 365 autodiscover endpoint and use the on-premises autodiscover service instead.
Do I need to recreate Outlook profiles?
No. The registry key works with the existing profiles, so no profiles need to be recreated.
When should I remove the registry key?
Remove it after the mailboxes are migrated to Microsoft 365 so Outlook can use the Microsoft 365 autodiscover endpoint again.
