Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
Hi MichaelClementin1712,
Please let us know if you have any updates about the issue.
Thanks,
Johnny Zhang
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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 features that help users manage their subscriptions, account settings, and billing information.
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.
Hi MichaelClementin1712,
Please let us know if you have any updates about the issue.
Thanks,
Johnny Zhang
Hi MichaelClementin1712,
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.
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
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?
Hi MichaelClementin1712,
Do you have any update on the issue?
Regards,
Johnny Zhang
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