Hybrid - centralized mail transport

%3CLINGO-SUB%20id%3D%22lingo-sub-289037%22%20slang%3D%22en-US%22%3EHybrid%20-%20centralized%20mail%20transport%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-289037%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3EI'm%20in%20the%20final%26nbsp%3Bphase%20of%20planning%20our%20Exchange%202013%20to%20Exchange%20online%20Hybrid%20deployment.%3C%2FP%3E%3CP%3EWe%20require%20that%20all%20primary%20smtp%20mail%20routes%20through%20our%20email%20gateway%20service%20(Mimecast)%20for%20compliance%20purposes.%3C%2FP%3E%3CP%3EWhat%20I%20would%20like%20to%20understand%20is%20when%20enabling%20this%20option%20using%20the%20HCW%20%2C%20will%20it%20also%20apply%20to%20our%20non%20primary%20SMTP%20domain%20mailbox%20users%20like%20our%26nbsp%3B%40***.onmicrosoft.com%20domains%20%3F%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-289037%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-289416%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20-%20centralized%20mail%20transport%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-289416%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Adam%20%2C%20that's%20a%20clear%20answer.%20Appreciate%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-289322%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20-%20centralized%20mail%20transport%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-289322%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Julian%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20HCW%20you%20have%20to%20select%20the%20domain(s)%20that%20you%20are%20using%20for%20hybrid.%20Those%20domains%20are%20then%20used%20in%20the%20connectors%20that%20are%20created.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20do%20not%20specify%20the%20domain%2C%20it%20will%20not%20be%20included%20on%20the%20connectors%2C%20and%20thus%20will%20not%20be%20impacted%20by%20the%20mail%20routing%20changes.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20same%20is%20true%20for%20any%20connector%20that%20is%20going%20to%20be%20pointed%20to%20mimecast%2C%20you%20have%20to%20specify%20what%20domains%20it%20applies%20too.%20In%20normal%20configurations%20the%20.onmicrosoft.com%20would%20not%20be%20included.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAdam%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi all,

I'm in the final phase of planning our Exchange 2013 to Exchange online Hybrid deployment.

We require that all primary smtp mail routes through our email gateway service (Mimecast) for compliance purposes.

What I would like to understand is when enabling this option using the HCW , will it also apply to our non primary SMTP domain mailbox users like our @***.onmicrosoft.com domains ?

Regards

 

 

2 Replies
Highlighted

Hey Julian,

 

In the HCW you have to select the domain(s) that you are using for hybrid. Those domains are then used in the connectors that are created.

 

If you do not specify the domain, it will not be included on the connectors, and thus will not be impacted by the mail routing changes.

 

The same is true for any connector that is going to be pointed to mimecast, you have to specify what domains it applies too. In normal configurations the .onmicrosoft.com would not be included.

 

Adam

Highlighted

Thanks Adam , that's a clear answer. Appreciate it.