Autodiscover setting in exchange hybird environemt for multi-domain

Chong 21 Reputation points

Hi Support,

We have serval domain in our exchange 2010 environment. The is our main domain in our exchange, all certificate and client access URL using this domain ( and
We will migrate one domain to o365 and setup a exchange 2016 for hybrid server.

In public and internal DNS, is point to ex2010, and is point to ex2016. For the ex2010 client access server uri setting, it is configured to "". And the ex2016 uri setting is configured to "". So the o365 will connect to ex2016 when run hybrid wizard.

After this configuration, our user outlook prompt the autodiscover change to "" and some user connect to ex2016

How to configure the autodiscover setting if we just planned to migrate the additional domain to o365 with no user impact (all other domain)



Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,382 questions
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,908 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. KyleXu-MSFT 26,211 Reputation points

    After this configuration, our user outlook prompt the autodiscover change to "" and some user connect to ex2016

    In a coexist environment, it is suggested and needed to use Exchange 2016 as client access point(if only publish one Exchange server to the Internet), because Exchange 2016 could proxy request to Exchange 2010, but not vice versa. Client Connectivity in an Exchange 2016 Coexistence Environment with Exchange 2010

    The URLs geted by Autodiscover service also decided by where mailbox hosted. So, make sure all "@jaswant .com" mailboxes are hosted on Exchange 2010 database.

    Then, use command below to check and backup autodiscover original configuration:

    Get-ClientAccessServer | fl Identity,*uri*  

    Then use command below to remove SCP from all Exchange servers:

    Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri $null  

    After that, make Exchange 2010/2016 use the same internal URL as their external URL(Exchange 2010 using "" and Exchange 2016 using "").

    Then restart IIS service(Run "IISReset" command in CMD) on all Exchange servers. Wait for a while, then check again.

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.