Autodiscover in a hybrid scenario

In the previous articles I showed you how to implement DirSync, create an Exchange hybrid environment with a migration endpoint and how to migrate Mailboxes from Exchange on-premises to Exchange Online. Not a single word on autodiscover though, and even when autodiscover is pointing to your on-premises Exchange environment, it continues to work for Mailboxes that have been migrated to Exchange Online. This is one of the advantages of an Exchange hybrid scenario.

This is what happens: when you move a Mailbox from Exchange on-premises to Exchange Online, the Mailbox on-premises is converted to a Mail-Enabled User (Remote Mailbox) and a target address is set to Exchange Online (i.e.

When an Outlook client does an Autodiscover request to the Exchange environment it detects the user is a Mail-Enabled User, and that a target address is set. Based on this target address a new Autodiscover request is initiated. So, Outlook does a request for a user called, Autodiscover returns a Mail-Enabled User with target address Next, Outlook wil try an Autodiscover request for this SMTP address.

The best way to show this is by using the Remote Connectivity Analyzer on http:/ In the RCA select the Office 365 tab and check Outlook Autodiscover in the Microsoft Office Outlook Connectivity Tests section.

Enter email address, user account and password, enter the verification code and click Perform Test. In the top section of the screen you’ll see that RCA is able to contact and retrieve an XML Autodiscover request for email address


When you expand the Additional Details, more information is shown about the information being returned by the Exchange server:


Clearly visible is the redirectAddr property and the email address

RCA will then try to continue based on this SMTP address. It will fail on several methods, but continue on the HTTP redirect option:


When you expand the Additional Details option under the HTTP redirect method, the autodiscover information is shown for the (which is the same as email address) user:


So, when moving Mailboxes from Exchange on-premises to Exchange Online in a hybrid scenario, there’s no need to change the autodiscover DNS record from on-premises to online. Even better, as long as there are resources on-premises you should leave the DNS record pointing to autodiscover on-premises.

3 thoughts on “Autodiscover in a hybrid scenario”

  1. Hi jaap, we have and in hybrid , all users are in cloud and some users are in cloud or on-perm. We still have public folders on perm. Can we switch autodiscover for to office 365?


    1. As long as you have resources on-premises that need to be accesses you have to keep autodiscover pointing to on-premises Exchange. If not, the resource won’t be discoverable anymore.


  2. now points to Office 365 (prior to running the HCW) as all mailboxes are there.
    when we run the HCW for both domains (abc and def) is it no problem to keep autodiscover pointing to office 365 or will HCW fail?

    and what would be adviseable, run HCW and use ‘Autodiscover Domain Feature’ for or use only autodiscoer and not use ‘Autodiscover Domain Feature’ (autod:) ?

    and lastly will DNS record autodiscover get higher prio or will autod: be used if both are configured?


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s