How does DeploymentPro bypass AutoDiscover?


How does DeploymentPro bypass AutoDiscover?


When migrating from one version of Exchange to another, it is not possible to have AutoDiscover in place for two environments at once. There are a couple of scenarios for bypassing the Source AutoDiscover in order to successfully configure a new Outlook profile for Office 365. 

1. On-Premises Exchange to Office 365 Exchange Online cutover migration:

If migrating from On-Premises Exchange to Office 365, and the computers are joined to the domain, Outlook will try to automatically configure the profile using SCP​ lookup (settings from Active Directory). Then it will query internal DNS, then look to External DNS settings. The new profile will configure successfully, but it will automatically connect to the Source Exchange environment.

2. If performing a staged/batch migration from On-Premises or Hosted Exchange, it will be necessary to have some Outlook users connected to the Source environment and some users connected to Office 365.  The users who need to connect to Office 365 will need to bypass AutoDiscover.

There are several different ways that Outlook tries to connect to the AutoDiscover service. Their order and priority is as follows:

  • SCP lookup
  • HTTPS root domain query
  • HTTPS Autodiscover domain query
  • HTTP redirect method
  • SRV record query

DeploymentPro automatically makes the following registry edits to bypass AutoDiscover and hard code the Office 365 server settings into the Outlook profile to ensure that users can begin using the Office 365 profile right away.

Outlook 2010:


Outlook 2013 and above:


PreferLocalXML, 1

ExcludeHttpsAutodiscoverDomain, 1


ExcludeSCPLookup, 1

ExcludeSrvLookup, 1

ExcludeSrvRecord, 1


Read more about AutoDiscover here:


Was this article helpful?
1 out of 1 found this helpful