hybrid email flow

%3CLINGO-SUB%20id%3D%22lingo-sub-1603098%22%20slang%3D%22en-US%22%3Ehybrid%20email%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1603098%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20Exchange%202016%20on-premise%20multi%20region.%20Email%20flow%20goes%20from%20internal%20to%20Edge%20to%20third%20party%20cloud%20to%20internet.%20Hybrid%20is%20installed%20using%20classic%20mode%20and%20centralised%20email%20flow%20was%20selected.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20outbound%20connector%20in%20O365%20pointed%20to%20cloud%20provider%20with%20address%20*.%20I%20have%20second%20connector%20pointed%20to%20Edge%20servers%20with%20route%20all%20accepted%20domains%20selected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EO365%20to%20on-premise%20keeps%20going%20via%20the%20'O365%20to%20cloud'%20connector%20despite%20the%20second%20connector%20being%20more%20applicable.%20I%20i%20disable%20the%20'O365%20to%20cloud'%20connector%20the%20second%20connector%20kicks%20in.%20The%20'O365%20to%20cloud'%20was%20created%20by%20the%20hybrid%20wizard%20and%20i%20notice%20in%20order%20to%20allow%20the%20'*'%20address%20space%20to%20function%20the%20connector%20has%20the%20'RouteAllMessagesViaOnPremise'%20value%20set%20to%20true.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20on-premise%20domains%20in%20O365%20are%20configured%20as%20InternalRelay%20following%20advice%20from%20MS%20support.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20spoken%20to%20MS%20and%20they%20tell%20me%20the%20connectors%20should%20work%20perfectly%20however%20this%20is%20not%20the%20case.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20i'm%20trying%20to%20make%20happen%20is%20all%20email%20flow%20for%20my%20internal%20domains%20flows%20by%20my%20Edge%20servers%20and%20all%20other%20emails%20flow%20via%20my%20O365%20to%20Cloud%20provider%20and%20then%20onto%20the%20internet.%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%3CLINGO-LABS%20id%3D%22lingo-labs-1603098%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ehybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1604558%22%20slang%3D%22en-US%22%3ERe%3A%20hybrid%20email%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1604558%22%20slang%3D%22en-US%22%3Ehello%20leslie%2C%3CBR%20%2F%3E%3CBR%20%2F%3Eyou%20can%20try%20CBR%20to%20force%20emails%20to%20use%20a%20connector%2C%20for%20example%20for%20O365%20to%20your%20cloud%20email%20security%20provider%2C%20you%20can%20create%20a%20transport%20rule%20to%20route%20all%20emails%20to%20the%20connector%20if%20sender%20is%20inside%20the%20org%20and%20recipient%20is%20outside%20the%20org%20%2C%20this%20should%20force%20all%20external%20emails%20to%20go%20through%20the%20connector%20you%20want%20it%20to.%3CBR%20%2F%3E%3CBR%20%2F%3Ethanks%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hello all,

 

I have Exchange 2016 on-premise multi region. Email flow goes from internal to Edge to third party cloud to internet. Hybrid is installed using classic mode and centralised email flow was selected. 

 

I have outbound connector in O365 pointed to cloud provider with address *. I have second connector pointed to Edge servers with route all accepted domains selected.

 

O365 to on-premise keeps going via the 'O365 to cloud' connector despite the second connector being more applicable. I i disable the 'O365 to cloud' connector the second connector kicks in. The 'O365 to cloud' was created by the hybrid wizard and i notice in order to allow the '*' address space to function the connector has the 'RouteAllMessagesViaOnPremise' value set to true.

 

The on-premise domains in O365 are configured as InternalRelay following advice from MS support.

 

We've spoken to MS and they tell me the connectors should work perfectly however this is not the case.

 

What i'm trying to make happen is all email flow for my internal domains flows by my Edge servers and all other emails flow via my O365 to Cloud provider and then onto the internet.

 

 

 

1 Reply
Highlighted
hello leslie,

you can try CBR to force emails to use a connector, for example for O365 to your cloud email security provider, you can create a transport rule to route all emails to the connector if sender is inside the org and recipient is outside the org , this should force all external emails to go through the connector you want it to.

thanks