Exchange Connection Problems

How to Configure Outlook Autodiscover in a Full Hybrid Exchange Environment

Anum Mushtaq Oct 19, 2026 869 views

Question details

Configure Outlook Autodiscover routing for environments where all mailboxes are in Microsoft 365 but an on-premises Exchange 2016 server remains active as an SMTP relay.

How to Configure Outlook Autodiscover in a Full Hybrid Exchange Environment

Product: Microsoft Exchange
Device & OS: not provided
Scenario: All mailboxes and mail flow have been migrated to Microsoft 365, with an on-premises Exchange 2016 server maintained strictly for SMTP relay purposes.
Observed behavior: Administrators need to ensure Autodiscover routes client requests directly to Microsoft 365 instead of the remaining on-premises infrastructure.

Before you start

Ensure you have Exchange administrative credentials and access to the on-premises Exchange Management Shell before modifying internal URIs or DNS configurations.

Solution 1Recommended

Update Autodiscover DNS Records and Clear Internal URI

Redirect all Autodiscover traffic to Microsoft 365 by updating DNS records and nullifying the internal Exchange Autodiscover URI.

When all mailboxes are migrated to Microsoft 365, internal domain-joined clients might still attempt to connect to the on-premises Exchange server via Service Connection Point (SCP) lookups. To prevent this connection failure, you must clear the internal URI and update your DNS records.

Verify mailbox migration status

Confirm that absolutely no user mailboxes remain on your on-premises Exchange 2016 server. All mailboxes and primary mail flows must be fully migrated to Microsoft 365.

Update internal and external DNS

Access your DNS management console and verify that both the internal and external Autodiscover CNAME records are pointing directly to autodiscover.outlook.com.

Clear the Autodiscover internal URI

Open the Exchange Management Shell on your on-premises server and execute the command: Get-ClientAccessService | Set-ClientAccessService -AutoDiscoverServiceInternalUri $Null

Update Autodiscover DNS Records and Clear Internal URI

Configuration Applied: Once the DNS changes propagate and the internal URI is cleared, Outlook clients will bypass the on-premises server and connect directly to Microsoft 365.

Solution 2

Consult Microsoft Q&A for Complex Hybrid Deployments

Use Microsoft's official support channels if standard DNS and URI configurations do not resolve the routing issues in your specific hybrid setup.

Free Microsoft Office alternative

Looking for a Lightweight Alternative to Microsoft Office?

While Exchange Server configuration requires Microsoft's administrative tools, you don't always need heavy desktop applications to manage your daily documents, spreadsheets, and presentations. WPS Office provides a free, lightweight, and highly compatible alternative to Microsoft Office suites.

1. Download WPS Office: Visit the official WPS website and download the free installation package for your operating system.
2. Install the application: Run the installer and follow the on-screen instructions to set up WPS Office on your computer.
3. Open and edit your files: Launch WPS Office to immediately start creating or editing your standard Office documents with full format compatibility.

Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Lightweight installation that consumes minimal system resources compared to traditional office suites.Familiar user interface for a seamless and intuitive transition from Microsoft Office.Built-in PDF editing, document conversion, and cloud collaboration tools.

microsoft office alternative - wps office

Frequently Asked Questions

Why do I need to clear the internal Autodiscover URI in a hybrid environment?

Clearing the internal Autodiscover URI prevents domain-joined Outlook clients from attempting to connect to the on-premises Exchange server via Active Directory SCP lookups, ensuring their Autodiscover requests route directly to Microsoft 365.

What should my Autodiscover DNS record point to after migrating to Microsoft 365?

Once all mailboxes are migrated, both your internal and external Autodiscover CNAME records should be updated to point directly to autodiscover.outlook.com.

Can I completely decommission my on-premises Exchange server after moving mailboxes?

If you are using Azure AD Connect for identity synchronization, Microsoft generally requires keeping an on-premises Exchange server for attribute management and SMTP relay purposes, even if all mailboxes are in Microsoft 365.

Outlook & Email Problems