First published on TechNet on Mar 04, 2017 We’ve had questions about the CNAME configuration required for Windows devices to automatically discover the MDM server for mobile device management (M...
Updated Oct 30, 2018
Version 3.0
Blog Post
Even though the change to "-s" was implemented in https://intunedin.net/2017/01/29/pointing-to-manage-microsoft-com-will-no-longer-work-for-enrollment (I missed it back then), some documentation agrees, like https://docs.microsoft.com/en-us/office365/admin/dns/create-dns-records-using-windows-based-dns?view=o365-worldwide#add-cname-records, but others do not, like https://docs.microsoft.com/en-us/office365/admin/dns/create-dns-records-at-cloudflare?redirectSourcePath=%252fen-US%252farticle%252fCreate-DNS-records-at-Cloudflare-for-Office-365-84acd4fc-6eec-4d00-8bed-568f036ae2af&view=o365-worldwide#add-the-six-cname-records-that-are-required-for-office-365.
Even the DNS checker in the admin portal warns of possible service issues and shows this. How can this possibly be at this point?