SOLVED

Using EOL protection but keep autodiscover using on-premise

%3CLINGO-SUB%20id%3D%22lingo-sub-1905824%22%20slang%3D%22en-US%22%3EUsing%20EOL%20protection%20but%20keep%20autodiscover%20using%20on-premise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1905824%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3ECurrently%20I%20have%20Hybrid%20configuration%20and%20its%20working%20fine.%3C%2FP%3E%3CP%3Ecurrently%20the%20External%20DNS%20is%20point%20to%20my%20premise.%3C%2FP%3E%3CP%3EI%20need%20to%20use%20Exchange%20Online%20Protection%20only%20to%20protect%20incomming%20email%2C%20but%20I%20still%20need%20to%20keep%20Autodiscover%20pointing%20to%20my%20premise.%3C%2FP%3E%3CP%3EAs%20far%20as%20I%20know%20it%20should%20be%20a%20simple%20thing%20which%20I%20change%20the%20MX%20only%20and%20leave%20the%20CNAME%20for%20the%20autodiscover%20pointing%20to%20my%20premise.%3C%2FP%3E%3CP%3EBut%20the%20issue%20I%20am%20having%20is%20when%20I%20try%20to%20manage%20the%20DNS%20using%20the%20Portal.Office.com%20I%20am%20forced%20to%20change%20all%2C%20MX%20-%20Autodiscover%20-%20SPF%20record.%3C%2FP%3E%3CP%3Ehow%20can%20I%20configure%20the%20wizard%20to%20only%20process%20MX%20and%20SPF%20and%20not%20to%20change%20the%20autodiscover.%3C%2FP%3E%3CP%3Eis%20it%20OK%20if%20I%20did%20the%20change%20only%20for%20these%202%20records%20and%20leave%20the%20autodiscover%20as%20is%20%3F%3C%2FP%3E%3CP%3E%3CSTRONG%3ENOTE%3C%2FSTRONG%3E%20I%20am%20using%20a%20thirdparty%20External%20DNS%20infrastructure.%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1905824%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1905915%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20EOL%20protection%20but%20keep%20autodiscover%20using%20on-premise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1905915%22%20slang%3D%22en-US%22%3E%3CP%3EEOP%20doesnt%20care%20about%20your%20autodiscover%20record%2C%20the%20MX%20is%20the%20important%20one%20here.%20And%20pay%20no%20attention%20to%20the%20Domain%20setup%2FDNS%20setup%20wizard%20in%20the%20portal%2C%20even%209%20years%20after%20release%20they%20havent%20adapted%20it%20to%20cater%20to%20hybrid%20scenarios.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi,

Currently I have Hybrid configuration and its working fine.

currently the External DNS is point to my premise.

I need to use Exchange Online Protection only to protect incomming email, but I still need to keep Autodiscover pointing to my premise.

As far as I know it should be a simple thing which I change the MX only and leave the CNAME for the autodiscover pointing to my premise.

But the issue I am having is when I try to manage the DNS using the Portal.Office.com I am forced to change all, MX - Autodiscover - SPF record.

how can I configure the wizard to only process MX and SPF and not to change the autodiscover.

is it OK if I did the change only for these 2 records and leave the autodiscover as is ?

NOTE I am using a thirdparty External DNS infrastructure.

Thanks

 

2 Replies
Highlighted
Best Response confirmed by niazstinu (Occasional Contributor)
Solution

EOP doesnt care about your autodiscover record, the MX is the important one here. And pay no attention to the Domain setup/DNS setup wizard in the portal, even 9 years after release they havent adapted it to cater to hybrid scenarios.

Highlighted

@Vasil Michev 

Thanks for your answer.

So I will update the DNS direct and just leave autodiscover alone.

this should have no impact and hopfully everything will be fine ... :)