Exchange Online Migration

%3CLINGO-SUB%20id%3D%22lingo-sub-319907%22%20slang%3D%22en-US%22%3EExchange%20Online%20Migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-319907%22%20slang%3D%22en-US%22%3E%3CP%3EApologies%20if%20this%20has%20been%20answered%20before.%26nbsp%3B%20We%20are%20going%20for%20a%20hybrid%20migration%20to%20EOL.%20On-premise%2C%20we%20have%20Exchange%202016%20and%20Exchange%202016%20Edge%20transport%20servers%2C%26nbsp%3BDLP%20appliance%20(Forcepoint%208.4)%2C%20and%20Trend%20Micro%20IMVSA.%20The%20Edge%20Transport%20is%20only%20used%20for%20address-rewrite.%20We%20are%20deciding%20whether%20to%20enable%20Centralised%20Transport%20because%20we%20wish%20to%20retain%20the%20DLP%20applicance.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20can%20you%20advise%20if%20Centralised%20Transport%20is%20the%20best%20choice%3F%20Should%20we%20re-create%20all%20DLP%20policies%20that%20are%20currently%20in%20Forcepoint%20over%20to%20Office%20365%20DLP%20so%20outgoing%20emails%20are%20screened.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20using%20Cisco%20Email%20Security%20as%20the%20mail%20gateway.%20MX%20record%20points%20to%20the%20on-prem%20Exchange.%3C%2FP%3E%3CP%3EWe%20also%20want%20to%20retain%20Trend%20Micro%20IMVSA%20and%20Cisco%20ES%20as%20our%20AV%20solution.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20advise.%20Thank%20you%20very%20much.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-319907%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn-Premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-320179%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20Migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-320179%22%20slang%3D%22en-US%22%3E%3CP%3EThat's%20not%20a%20question%20you%20will%20find%20the%20answer%20for%20on%20a%20random%20board%2C%20you%20need%20to%20sit%20down%20with%20your%20team%20and%20evaluate%20whether%20the%20DLP%20capabilities%20of%20O365%20meet%20your%20needs%20and%20whether%20there%20is%20a%201%3A1%20correspondence%20with%20the%20features%20you%20are%20already%20using.%20Configuring%20centralized%20transport%20certainly%20sounds%20like%20an%20easy%20to%20give%20answer%2C%20but%20then%20again%20if%20you%20can%20have%20a%20similar%20setup%20within%20O365%2C%20why%20keep%20paying%20for%20the%20on-premises%20boxes.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Regular Visitor

Apologies if this has been answered before.  We are going for a hybrid migration to EOL. On-premise, we have Exchange 2016 and Exchange 2016 Edge transport servers, DLP appliance (Forcepoint 8.4), and Trend Micro IMVSA. The Edge Transport is only used for address-rewrite. We are deciding whether to enable Centralised Transport because we wish to retain the DLP applicance. 

 

Please can you advise if Centralised Transport is the best choice? Should we re-create all DLP policies that are currently in Forcepoint over to Office 365 DLP so outgoing emails are screened. 

 

We are using Cisco Email Security as the mail gateway. MX record points to the on-prem Exchange.

We also want to retain Trend Micro IMVSA and Cisco ES as our AV solution.

 

Please advise. Thank you very much.

1 Reply
Highlighted

That's not a question you will find the answer for on a random board, you need to sit down with your team and evaluate whether the DLP capabilities of O365 meet your needs and whether there is a 1:1 correspondence with the features you are already using. Configuring centralized transport certainly sounds like an easy to give answer, but then again if you can have a similar setup within O365, why keep paying for the on-premises boxes.