Share via

Autodiscover changes

Anonymous
2016-01-24T19:27:35+00:00

I have an Exchange 2013 hybrid server in place and am completing the migration of mailboxess to Office 365.  I'm ready to update the autodiscover records, but need to clairify the change for the on-premise autodiscover record.  Right now it's an A record pointing to the on-premise exchange server.  I have the information for the external dns, but I don't want the on-premise record to point users to the on-premise exchange server.

Do I delete it?  Create a cname to where?

Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

5 answers

Sort by: Most helpful
  1. Anonymous
    2016-02-01T03:43:34+00:00

    Hi MichaelClementin1712,

    Please let us know if you have any updates about the issue.

    Thanks,

    Johnny Zhang

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-01-29T04:12:21+00:00

    Hi MichaelClementin1712,

    1. Did you test from internal AD network or external public network?

    When working from the internal work, the on-premise Exchange server settings might affect the Outlook connection to Office 365, like SCP. In the on-premise environment, the Exchange setup creates an Autodiscover Service Connection Point (SCP) record in AD for each Client Access server. In the internal AD environment, when Outlook client starts the Autodiscover process, it will firstly try to find the information used for Autodiscover by using SCP, instead of DNS lookup. Actually, SCP is always the first thing that Autodiscover checks for, and if it isn't found then it moves on to a DNS check.

    1. Please provide the entire test result
    2. What is the test result from external network?  

    To protect your privacy, I have sent a private message to request the test result. Please use this link to access the private message: community.office365.com/.../conversations

    Thanks,

    Young

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-01-28T07:47:05+00:00

    I've updated my internal DNS server as follows:

    Alias (CNAME)

    autodiscover

    FQDN:

    autodiscover.domain.com

    FQDN for target host:

    autodiscover.outlook.com

    I've also updated my external DNS records to

    CNAME - autodiscover.outlook.com

    However, when testing, it's still point to  domain.com/.../autodiscover.xml

    The above test is using the Outlook client - Test Configuration.

    Any advice?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-01-27T20:35:17+00:00

    Hi MichaelClementin1712,

    Do you have any update on the issue?

    Regards,

    Johnny Zhang

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-01-25T01:51:59+00:00

    Hi MichaelClementin1712,

    In hybrid, I would like to explain the autodiscover needs to be pointed to on premise hybrid server. If you would like to decommission on premise servers, and use Exchange Online service only, you can point the autodiscover to Cloud (using cname record to point to autodiscover.outlook.com).

    Regards,

    Johnny Zhang

    Was this answer helpful?

    0 comments No comments