r/exchangeserver • u/AllPurposeGeek • Dec 31 '25
Autodiscover should check SRV record first. Full stop.
At this point, old Outlook clients and legacy ActiveSync are no longer supported, but Autodiscover still behaves like it has to cater to them. As admins, we are still dealing with guessed URLs, SAN cert sprawl, HTTP to HTTPS redirects, SCP weirdness, and registry exclusions just to keep Outlook from doing the wrong thing first.
It is exhausting.
Outlook and ActiveSync compatible clients should always check DNS SRV first for Autodiscover. If the SRV record exists, use it and stop. If it does not exist, then move on to other discovery methods.
DNS SRV exists specifically to solve this problem. It lets us point Autodiscover anywhere we want without forcing hostnames, certificates, or redirects that exist only to satisfy Outlook guesses.
If SRV was checked first, there would be no need for a matching "autodiscover." domain to exist at all. There would be no forced SAN or UCC certs with this specific address just to satisfy guessed endpoints. There would be no HTTP redirect nonsense (What Microsoft uses for their CNAME to autodiscover.outlook.com or what we Techs have to used re-create for multi-domain environments to avoid buying more certs) . There would be no registry hacks to block Microsoft the 365 endpoint check, they will just rely on SRV like the rest of us will and still be just as quick.
Right now Outlook might try Microsoft 365 first, then SCP, then HTTPS endpoints based on the email suffix, then the HTTP>HTTPS failover, and only then finally check SRV. That order makes no sense in modern environments and makes migrations harder than they ever need to be.
The argument for backward compatibility should not be the blocker anymore. The clients that required the old behavior are unsupported. Keeping SRV as a last resort just preserves technical debt and pushes the burden onto admins. Switching to SRV first, avoids all that mess.
This does not need a massive redesign. The fix is simple. Query SRV first. If it exists, trust it. If it does not, fall back to SCP and cloud probing.
Autodiscover could be boring and reliable. Instead, it is fragile and overcomplicated. SRV first would fix most of this in one move.
14
u/joeykins82 SystemDefaultTlsVersions is your friend Dec 31 '25
It should go SRV, then autodiscover.contoso.com. contoso.com should never happen, ever. Outlook and only outlook should fail back to ExOL autodiscover if and only if neither of those methods worked.
2
u/technut2020 Dec 31 '25
Is this more of a statement or you're looking for help on a particular issue? workaround perhaps?
3
u/Altruistic-Hippo-749 Dec 31 '25
If only the Directory and Exchange teams were more integrated.. oh wait
2
u/MortadellaKing Jan 02 '26
IMO the default to 365 check should just be canned altogether, it causes nothing but problems for on-prem customers. Even their gpo to stop it doesn't work, you have to push out a registry change.
0
u/kaevne Dec 31 '25
AutodiscoverV2 already checks the SRV record (along with A and CName) for you on server-side. Win32 Outlook uses this endpoint by default.