Forum Discussion
External DNS records required for email in Office 365 (Exchange Online)
Hi Dan_Snape thanks for your reply.
I managed (and actually manage) a lot of hybrid configurations. No doubt on how autodiscover must be configured based on the scenario.
My question is related on the autodiscover.service.contoso.com CNAME record only.
Please read!!! I'm not referring to autodiscover.contoso.com, i'm referring to autodiscover.service.contoso.com
If i've OnPrem mailboxes in a hybrid scenario, do you mean i've to create a CNAME record for autodiscover.service.contoso.com that point to the Exchange OnPrem web services?
I never create this record, everything works fine, the record is suggested based on the MS documentation. What's the purpose of autodiscover.service.contoso.com record? Which is the difference from autodiscover.contoso.com?
Thanks!
- Dan_SnapeSep 10, 2023Bronze ContributorIt's not mentioned in the M365 admin portal when you you look at the required DNS records for a custom domain. Maybe Microsoft can provide more insights...perhaps it's for a future product/configuration
- LoremanReturns9791Sep 08, 2023Copper Contributor
Hi Dan_Snape, thanks for your reply.
I also thoungh it's just an error.
But this CNAME record is mentioned in two Microsoft documentation pages.
Here: https://learn.microsoft.com/en-us/microsoft-365/enterprise/external-domain-name-system-records?view=o365-worldwide#external-dns-records-required-for-email-in-office-365-exchange-online
and
here: https://learn.microsoft.com/en-us/training/modules/configure-client-connectivity-microsoft-365/3-explore-dns-records-required-client-configuration
In the second one it refers to the CNAME autodiscover.service.adatum.com for Exchange Federation as "needed when you deploy Exchange in a hybrid configuration with Microsoft 365"
That's a news for me, never configured "autodiscover.service.adatum.com" in any Hybrid Configuration and federation works fine.