
If Outlook still connects to the old server after mail has moved to Microsoft 365, keeps prompting for a password or cannot create a new profile, the problem is almost always Autodiscover. Outlook may find an SCP record left in Active Directory by an old Exchange server, a hosting server answering on your domain’s root address, or a wrong autodiscover DNS record before it ever reaches Microsoft 365. The fix is to point the autodiscover CNAME to autodiscover.outlook.com, clear the SCP values and stop the web server from answering Autodiscover requests.
Symptoms: “Not Responding”, repeated password prompts, IMAP profile
- Outlook opens and the Inbox appears, but as soon as you do anything the title bar shows “Not Responding” for several minutes.
- The credentials window keeps reappearing even though the correct password is entered.
- A new Outlook profile cannot be created, or the account is added as an IMAP profile instead of Exchange.
- Free/busy information cannot be viewed, and connecting to a shared mailbox or public folder fails.
- The problem occurs on domain-joined company PCs but not on a home computer or in Outlook on the web (OWA). This distinction points to SCP.
Root cause: in what order does Outlook look for Autodiscover?
According to Microsoft’s “Outlook 2016 implementation of Autodiscover” article, Outlook 2016 and later try to obtain Autodiscover information in this order: local XML preference, last known good URL, Office 365 as priority, the SCP in Active Directory, the root domain (https://domain/autodiscover/autodiscover.xml), the autodiscover subdomain (https://autodiscover.domain/autodiscover/autodiscover.xml), HTTP redirect, the _autodiscover._tcp SRV record and, as a last resort, Office 365 again. Once a step returns a valid payload, the later steps are not tried.
There are three typical sources of trouble. The first is the SCP: if the computer is domain-joined, Outlook performs an LDAP query to read the service connection point published by the old Exchange server and tries that URL. Microsoft KB 3012603 attributes Outlook hanging with “Not Responding” after mailboxes move to Exchange Online to exactly this: on-premises Client Access servers referenced in the client registry or in SCP objects.
The second is the root domain. During the root domain attempt, Outlook deliberately silences certificate errors. If the server hosting your website returns a successful Autodiscover response at that address, Outlook never moves on to the autodiscover subdomain; it tries to authenticate with the POP or IMAP protocols advertised in the response and fails. Microsoft KB 3049615 describes this scenario with the IMAP profile, profile creation failure and missing free/busy symptoms.
The third is DNS: the autodiscover record may still point to the old server or the hosting company, or only the external DNS was updated and the internal one was forgotten. The record Microsoft requires is a CNAME with the alias autodiscover pointing to autodiscover.outlook.com.
Step-by-step fix
- Isolate the symptom: if the problem only occurs on domain-joined PCs, look at SCP first; if it happens everywhere, look at DNS and the root domain. While Outlook is running, hold Ctrl, right-click the Outlook icon in the notification area, run “Test E-mail AutoConfiguration” with the “Use Guessmart” options cleared, and read on the Log tab which URL was tried.
- Check DNS: the autodiscover record for your domain must point to autodiscover.outlook.com. If you have a separate internal DNS zone (split-brain), Microsoft warns that both internal and external DNS must be updated.
- Test the root domain response: in Microsoft Remote Connectivity Analyzer (https://testconnectivity.microsoft.com/tests/o365), run the “Outlook Autodiscover” test on the Microsoft 365 tab, open all results with “Expand All” and search for “<Type>IMAP</Type>”. If you find it, your web server is answering the Autodiscover request; ask your hosting provider to switch that response off.
- Read the SCP values: if there is still an on-premises Exchange server, view the AutoDiscoverServiceInternalUri values with the read-only command below in the Exchange Management Shell.
- If all mailboxes are in Microsoft 365 and you no longer need Autodiscover from on-premises Exchange, clear the SCP values with the command from Microsoft’s decommissioning article. This makes clients use DNS-based Autodiscover instead.
- If the Exchange server no longer exists and the SCP cannot be cleared, set the ExcludeScpLookup DWORD to 1 on the client as a documented workaround. If the root domain problem cannot be fixed on the hosting side right away, the ExcludeHttpsRootDomain value can also be used temporarily.
- Restart Outlook and confirm with “Test E-mail AutoConfiguration” that the correct URL is returned. Outlook refreshes Autodiscover one hour after a successful attempt and five minutes after a failed one; if the old URL still comes back, create a new Outlook profile.
nslookup -type=CNAME autodiscover.yourcompany.com
Resolve-DnsName -Name autodiscover.yourcompany.com -Type CNAME
# Exchange 2016 and later, read-only:
Get-ClientAccessService | Format-List Name,AutoDiscoverServiceInternalUriThe SCP clearing command below turns off on-premises Autodiscover. Do not run it if there are still mailboxes, public folders or SMTP relay services on premises; Microsoft states that in this scenario pointing Autodiscover to Exchange Online breaks features such as hybrid public folder access. If you use directory synchronization, read Microsoft’s decommissioning article on recipient management before removing the Exchange server completely.
# Exchange 2016 and later
Get-ClientAccessService | Set-ClientAccessService -AutoDiscoverServiceInternalUri $Null
# Exchange 2010 or 2013
Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri $NullBack up the registry before changing it. For ExcludeHttpsRootDomain, Microsoft states explicitly that it is not a long-term solution and that the key must be removed once the hosting side is fixed. Values deployed through Group Policy live under HKEY_CURRENT_USER\Software\Policies and take precedence.
Key: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover
Value: ExcludeScpLookup (DWORD) = 1
Value: ExcludeHttpsRootDomain (DWORD) = 1 (temporary only)Note: the Microsoft Support and Recovery Assistant (SaRA) command-line utility was removed with Windows updates released on and after 10 March 2026; Microsoft recommends the Get Help tool instead. Do not download old SaRA builds from unofficial sites.
Lasting prevention
- Put “change the autodiscover CNAME and clear the SCP” into the migration plan just as prominently as “change the MX record”.
- Update internal and external DNS at the same time; do not forget the autodiscover record in split-brain DNS.
- Before the migration, tell the company hosting your website that the server must not answer /autodiscover/autodiscover.xml requests.
- Document any Exclude values deployed by registry or Group Policy and roll them back once the root cause is fixed.
- After the migration, rerun the Outlook Autodiscover test in Remote Connectivity Analyzer for several user domains.
When should you call an expert?
If your environment still has an old Exchange server, directory synchronization or public folders, or if the problem only appears on some computers, deleting the SCP or editing the registry can create new problems. For post-migration issues like these that we encounter in the field at businesses in Denizli, Workas reviews the Autodiscover chain end to end as part of its Microsoft 365 service and fixes DNS, Active Directory and the client side together. We provide support Monday to Saturday, 08:00–18:00, and respond with priority in emergencies.
Frequently Asked Questions
Why does the problem only happen on company computers?
The SCP lookup is only performed on domain-joined computers. A home computer cannot reach Active Directory, so it never sees the old Exchange record and goes straight to the DNS methods.
Is the autodiscover CNAME record mandatory?
Microsoft describes it as optional but highly recommended. If it is missing or wrong, Outlook falls through to lower-priority methods and is more likely to get stuck on a bad response.
Can I deploy ExcludeScpLookup permanently to all PCs?
Microsoft offers this value as a documented fix, but the clean, permanent route is to clear the on-premises SCP values. Registry values should be documented and removed once they are no longer needed.
How can I verify the root domain response myself?
In the Outlook Autodiscover test in Remote Connectivity Analyzer, expand the results and search for “<Type>IMAP</Type>”. Unless you deliberately set the mailbox up for IMAP, this shows that the web server is answering.
Sources
- Microsoft Support: Outlook 2016 implementation of Autodiscover
- Microsoft Learn: Issues when using Autodiscover service (KB 3049615)
- Microsoft Learn: Outlook not responding when connecting to Online mailbox (KB 3012603)
- Microsoft Learn: How and when to decommission your on-premises Exchange servers in a hybrid deployment
- Microsoft Learn: External Domain Name System records for Microsoft 365


