SOLVED

Office 365 domain using external email server

%3CLINGO-SUB%20id%3D%22lingo-sub-1181157%22%20slang%3D%22en-US%22%3EOffice%20365%20domain%20using%20external%20email%20server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1181157%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20tenancy%20has%20a%20number%20of%20different%20domains%20associated%20with%20it%2C%20all%20subscribed%20to%20O365%20Business%20Professional.%20For%20one%20specific%20domain%20(lets%20call%20it%20%3CEM%3E%3CSTRONG%3Ebusiness2.com%3C%2FSTRONG%3E%3C%2FEM%3E)%2C%20email%20is%20still%20hosted%20by%20a%20third%20party%2C%20so%20when%20setting%20this%20up%20we%20turned%20off%20the%20EOL%20component%20licence%20for%20the%20domain.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20when%20other%20domains%20within%20the%20same%20tenancy%20attempt%20to%20send%20to%20email%20address%20at%26nbsp%3B%3CSTRONG%3E%3CEM%3Ebusiness2.com%2C%26nbsp%3B%3C%2FEM%3E%3C%2FSTRONG%3Eoffice%20attempts%20to%20deliver%20these%20locally%20within%20the%20tenancy%20even%20though%20email%20services%20are%20provided%20externally.%20Not%20overly%20surprising%20really.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20we%20able%20to%20force%20O365%20to%20do%20an%20external%20MX%20lookup%20for%20this%20domain%3F%20Or%20do%20we%20need%20to%20set%20up%20a%20connector%3F%20We've%20looked%20into%20the%20latter%2C%20but%20are%20a%20little%20confused%20at%20how%20to%20set%20this%20up.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESimon.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1181157%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1181160%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20domain%20using%20external%20email%20server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1181160%22%20slang%3D%22en-US%22%3EHi!%3CBR%20%2F%3E%3CBR%20%2F%3EA%20connector%20is%20not%20ultimately%20required.%20What%20is%20required%20is%20that%20the%20domain%20is%20set%20to%20non-authoritative%20(Internal%20Relay)%20in%20the%20Exchange%20Admin%20Centre.%20I%20used%20to%20do%20this%20a%20lot%20of%20Coex%20migrations%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmail-flow-best-practices%2Fmanage-accepted-domains%2Fmanage-accepted-domains%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmail-flow-best-practices%2Fmanage-accepted-domains%2Fmanage-accepted-domains%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EOnce%20set%20to%20internal%20relay%20which%20you%20can%20change%20in%20accepted%20domains%20or%20by%20PowerShell%20and%20assuming%20the%20MX%20is%20directed%20at%20the%20external%20mail%20platform%20it%20ought%20to%20resolve%3CBR%20%2F%3E%3CBR%20%2F%3EHowever%2C%20if%20this%20doesn%E2%80%99t%20work%20by%20itself%20you%20add%20an%20external%20send%20connector%20from%20Office%20365%20to%20the%20mail%20server%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmail-flow-best-practices%2Fuse-connectors-to-configure-mail-flow%2Fset-up-connectors-to-route-mail%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmail-flow-best-practices%2Fuse-connectors-to-configure-mail-flow%2Fset-up-connectors-to-route-mail%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20that%20helps%20and%20answers%20your%20question!%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1191795%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20domain%20using%20external%20email%20server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1191795%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169605%22%20target%3D%22_blank%22%3E%40Christopher%20Hoard%3C%2FA%3EThanks%20very%20much%20for%20the%20information.%20Worked%20perfectly%2C%20as%20long%20as%20I%20was%20patient%20waiting%20for%20the%20update%20to%20take%20effect.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hello,

 

Our tenancy has a number of different domains associated with it, all subscribed to O365 Business Professional. For one specific domain (lets call it business2.com), email is still hosted by a third party, so when setting this up we turned off the EOL component licence for the domain.

 

Unfortunately when other domains within the same tenancy attempt to send to email address at business2.com, office attempts to deliver these locally within the tenancy even though email services are provided externally. Not overly surprising really.

 

Are we able to force O365 to do an external MX lookup for this domain? Or do we need to set up a connector? We've looked into the latter, but are a little confused at how to set this up.

 

Simon.

2 Replies
Highlighted
Solution
Hi!

A connector is not ultimately required. What is required is that the domain is set to non-authoritative (Internal Relay) in the Exchange Admin Centre. I used to do this a lot of Coex migrations

https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/manage-accepted-domains/manage-ac...

Once set to internal relay which you can change in accepted domains or by PowerShell and assuming the MX is directed at the external mail platform it ought to resolve

However, if this doesn’t work by itself you add an external send connector from Office 365 to the mail server

https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/use-connectors-to-configure-mail-...

Hope that helps and answers your question!

Best, Chris
Highlighted

@Christopher HoardThanks very much for the information. Worked perfectly, as long as I was patient waiting for the update to take effect.