Autodiscover - Pointing to cloud

%3CLINGO-SUB%20id%3D%22lingo-sub-1583141%22%20slang%3D%22en-US%22%3EAutodiscover%20-%20Pointing%20to%20cloud%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1583141%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20raise%20this%20question%20as%20currently%20looking%20at%20methods%20to%20re-point%20our%20autodiscover%20records%20to%20O365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20we%20currently%20have%20a%20Exchange%20Hybrid%20setup%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EOn-premise%20DNS%20pointing%20to%20our%20exchange%20servers%3C%2FP%3E%3CP%3E%3CBR%20%2F%3Eautodiscover%20-%26gt%3B%20A%20-%26gt%3B%20exchange%20server%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESRV%20record%26nbsp%3B%3CBR%20%2F%3E_autodiscover._tcp.company.pri%20SRV%20service%20location%3A%3CBR%20%2F%3Epriority%20%3D%200%3CBR%20%2F%3Eweight%20%3D%200%3CBR%20%2F%3Eport%20%3D%20443%3CBR%20%2F%3Esvr%20hostname%20%3D%20autodiscover.company.pri%3CBR%20%2F%3Eautodiscover.company.pri%20internet%20address%20%3D%2010.x.x.x%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20memory%20the%20SRV%20record%20was%20transitioned%20from%20a%20Exchange%202010%20deployment%20of%20past%20days%20and%20also%20to%20sort%20out%20the%20infamous%20Outlook%20Error%20%E2%80%9CThe%20name%20of%20the%20security%20certificate%20is%20invalid%20or%20does%20not%20match%20the%20name%20of%20the%20site.%E2%80%9D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20the%20A%20record%20is%20created%20-%20they%20will%20be%20used%20prior%20the%20SRV%20record.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20our%20current%20scenario%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20All%20mailboxes%20have%20been%20migrated%20to%20the%20cloud.%3C%2FP%3E%3CP%3E-%20On%20premise%20exchange%20servers%20used%20management%20and%20old%20application%20relays.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20stopping%20us%20from%20re-pointing%20our%20autodiscover%20records%20to%20cloud%3F%3C%2FP%3E%3CP%3EThat's%20why%20I%20ask%20this%20question%20-%20and%20pose%20the%20following%20steps%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1)%20Move%20public%20DNS%20to%20autodiscover.outlook.com%3C%2FP%3E%3CP%3E2)%20%3CSPAN%3ESet-ClientAccessServer%20-AutoDiscoverServiceInternalUri%20%24null%26nbsp%3Bor%20essentially%20point%20the%20internal%20-AutoDiscoverServiceInternalUri%20to%20%3CA%20href%3D%22https%3A%2F%2Fautodiscover.outlook.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fautodiscover.outlook.com%2F%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E3)%20Delete%20internal%20A%20(autodiscover)%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E4)%20Create%20new%20internal%20CNAME%20record%20pointing%20to%20autodiscover.outlook.com%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHere%20is%20my%20confusion%20-%20will%20the%20SRV%20record%20still%20be%20required%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1583141%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1583219%22%20slang%3D%22en-US%22%3ERe%3A%20Autodiscover%20-%20Pointing%20to%20cloud%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1583219%22%20slang%3D%22en-US%22%3E%3CP%3EHey%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F597543%22%20target%3D%22_blank%22%3E%40vas_ppabp_90%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20don't%20need%20the%20SRV%20record%20if%20you%20are%20to%20point%20the%20autodiscover%20to%20office%20365.%20In%20fact%20Microsoft%20doesn't%20provide%20a%20SRV%20record%20for%20its%20cloud%20autodiscover%20service%20%3A%3C%2FP%3E%3CP%3ERecords%20(Godaddy)%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fadmin%2Fdns%2Fcreate-dns-records-at-godaddy%3Fview%3Do365-worldwide%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fadmin%2Fdns%2Fcreate-dns-records-at-godaddy%3Fview%3Do365-worldwide%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20add%2C%20the%20exchange%20hybrid%20configuration%20doesn't%20even%20use%20the%20SRV-based%20Autodiscover%20redirection.%3C%2FP%3E%3CP%3ERef%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Fmsoffice%2Fforum%2Fall%2Fautodiscover-dns-srv-records-cannot-be-used-for%2Ffe4f27d0-efd7-4452-9e0d-6e0d30d251f8%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Fmsoffice%2Fforum%2Fall%2Fautodiscover-dns-srv-records-cannot-be-used-for%2Ffe4f27d0-efd7-4452-9e0d-6e0d30d251f8%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi All,

 

I raise this question as currently looking at methods to re-point our autodiscover records to O365.

 

So, we currently have a Exchange Hybrid setup


On-premise DNS pointing to our exchange servers


autodiscover -> A -> exchange server

 

And

 

SRV record 
_autodiscover._tcp.company.pri SRV service location:
priority = 0
weight = 0
port = 443
svr hostname = autodiscover.company.pri
autodiscover.company.pri internet address = 10.x.x.x

 

From memory the SRV record was transitioned from a Exchange 2010 deployment of past days and also to sort out the infamous Outlook Error “The name of the security certificate is invalid or does not match the name of the site.”

 

As the A record is created - they will be used prior the SRV record.

 

So our current scenario;

 

- All mailboxes have been migrated to the cloud.

- On premise exchange servers used management and old application relays.

 

What is stopping us from re-pointing our autodiscover records to cloud?

That's why I ask this question - and pose the following steps

 

1) Move public DNS to autodiscover.outlook.com

2) Set-ClientAccessServer -AutoDiscoverServiceInternalUri $null or essentially point the internal -AutoDiscoverServiceInternalUri to https://autodiscover.outlook.com/

3) Delete internal A (autodiscover) 

4) Create new internal CNAME record pointing to autodiscover.outlook.com

 

Here is my confusion - will the SRV record still be required?

1 Reply
Highlighted

Hey @vas_ppabp_90 ,

 

You don't need the SRV record if you are to point the autodiscover to office 365. In fact Microsoft doesn't provide a SRV record for its cloud autodiscover service :

Records (Godaddy)

https://docs.microsoft.com/en-us/microsoft-365/admin/dns/create-dns-records-at-godaddy?view=o365-wor...

 

To add, the exchange hybrid configuration doesn't even use the SRV-based Autodiscover redirection.

Ref: https://answers.microsoft.com/en-us/msoffice/forum/all/autodiscover-dns-srv-records-cannot-be-used-f...

 

Thanks