Exchange Connection Problems

Configure Office 365 Autodiscover for Internal and External Outlook Clients

Kushani NimanthikaKushani Nimanthika Nov 18, 2026 870 views

Question details

Configure internal and external Autodiscover so Outlook clients connect to Office 365 rather than an old on-premises Exchange server.

Configure Office 365 Autodiscover for Internal and External Outlook Clients
Product
Microsoft 365 Exchange Online and Outlook
Device & OS
not provided
Scenario
A non-hybrid deployment has an internal Exchange Autodiscover service connection point (SCP) and an internal autodiscover.domain.com DNS record.
Observed behavior
Clients may discover the internal Exchange server through the SCP or internal DNS instead of connecting to Office 365.
Before you start

Confirm that all affected mailboxes are in Exchange Online and that no on-premises clients depend on the existing Autodiscover configuration. Identify the email domain, internal and public DNS zones, and any Exchange servers publishing an SCP.

Solution 1Recommended

Update the Exchange SCP and Autodiscover DNS records

Use this approach when the deployment is cloud-only and the old on-premises Autodiscover settings are no longer needed.

1
Inspect the published SCP

On an Exchange server, open Exchange Management Shell and run Get-ClientAccessService | Format-List Name,AutoDiscoverServiceInternalUri. Identify any servers publishing an on-premises Autodiscover URL.

2
Clear obsolete SCP URLs

For each server whose SCP is no longer needed, run Set-ClientAccessService -Identity "ServerName" -AutoDiscoverServiceInternalUri $null in Exchange Management Shell. Replace ServerName with the actual server name.

3
Update internal and public DNS

In your DNS management tools, configure autodiscover.domain.com as a CNAME pointing to autodiscover.outlook.com in the public zone and, if an internal zone overrides it, in the internal zone as well. Replace domain.com with the email domain and remove a conflicting record for the same name before creating the CNAME.

4
Check client overrides

On an affected Windows client, open Registry Editor and review the Autodiscover settings under HKEY_CURRENT_USER\Software\Microsoft\Office\<version>\Outlook\AutoDiscover and the corresponding Policies path. Check whether existing settings or Group Policy override normal discovery before changing them.

5
Verify discovery

From an affected client, run nslookup -type=CNAME autodiscover.domain.com to check internal DNS. In classic Outlook, Ctrl+right-click the Outlook notification-area icon, select Test Email AutoConfiguration, and review the results for the affected account.

Protect other Exchange dependencies: Do not clear an SCP or replace DNS records until you have confirmed that on-premises mailboxes and applications no longer rely on them. Outlook can also evaluate other Autodiscover endpoints, so a correct CNAME alone may not resolve every discovery issue.
Free Microsoft Office alternative

Work with Office files in WPS Office

WPS Office is a free, lightweight alternative with a familiar interface for working with Microsoft Office files. Its format support makes it easier to move document, spreadsheet, and presentation workflows to WPS. It does not repair Outlook or Exchange Autodiscover settings.

Open and edit Microsoft Word, Excel, and PowerPoint formatsUse a familiar interface for everyday Office file workflowsKeep working on Office documents while an administrator resolves Exchange connectivityInstall a lightweight office suite for free
microsoft office alternative - wps office

Frequently Asked Questions

Why does Outlook connect to the old Exchange server?

A domain-joined Outlook client may discover an on-premises Exchange SCP, or an internal DNS record may direct autodiscover.domain.com to the old server. Review both the SCP and the internal DNS zone.

What should the Microsoft 365 Autodiscover DNS record point to?

For an email domain using Exchange Online, configure autodiscover.domain.com as a CNAME to autodiscover.outlook.com. If internal DNS hosts the same zone, make sure its record also directs clients appropriately.

Can I make Outlook ignore the on-premises SCP?

On Windows, the ExcludeScpLookup DWORD under the user's Outlook AutoDiscover registry key can be set to 1. This skips SCP lookup, but an incorrect internal DNS record still needs to be addressed.

How can I see which Autodiscover result Outlook uses?

In classic Outlook, Ctrl+right-click the Outlook icon in the Windows notification area and select Test Email AutoConfiguration. Review the results for the affected account, and use nslookup to check internal DNS separately.