Exchange On-Premise and Office 365 Connectors

%3CLINGO-SUB%20id%3D%22lingo-sub-1734482%22%20slang%3D%22en-US%22%3EExchange%20On-Premise%20and%20Office%20365%20Connectors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1734482%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20situation%20where%20our%20company%20has%202%20mailboxes%20for%20each%20employee.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1%20on-premise%20exchange%202016%20and%20Office%20365.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20not%20looking%20into%20hybrid%20or%20migrating%20for%20now%2C%20but%20we%20want%20to%20see%20mails%20sent%20to%20our%20Office%20365%20mailboxes.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGood%20example%20of%20this%20is%20sharing%20onedrive%20files%2C%20we%20do%20not%20receive%20notifications%20in%20our%20on-premise%20mailboxes.%20They%20go%20straight%20to%20Office%20365.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20we%20want%20to%20accomplish%20for%20now%20is%20receive%20the%20emails%20sent%20to%20our%20office%20365%20mailboxes.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWould%20mail%20flow%20connectors%20accomplish%20this%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%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-1734482%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Connectors%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1734663%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20On-Premise%20and%20Office%20365%20Connectors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1734663%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F816397%22%20target%3D%22_blank%22%3E%40seyah96%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3EYou%20are%20in%20sort%20of%20an%20unsupported%20scenario%2C%20by%20default%20when%20any%20user%20from%20within%20office%20365%20sends%20an%20email%20to%20another%20office%20365%20recipient%2C%20the%20emails%20are%20routed%20internally%20and%20will%20be%20delivered%20to%20office%20365%20mailbox%20only%2C%20even%20if%20the%20MX%20record%20for%20the%20domain%20is%20pointed%20elsewhere.%20For%20regular%20emails%20criteria%20based%20routing%20should%20work%20%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmail-flow-best-practices%2Fuse-connectors-to-configure-mail-flow%2Fconditional-mail-routing%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmail-flow-best-practices%2Fuse-connectors-to-configure-mail-flow%2Fconditional-mail-routing%3C%2FA%3E%3C%2FP%3E%3CP%3EFirst%20create%20a%20Distribution%20group%20in%20office%20365%20with%20all%20the%20mailboxes%20present%20in%20office%20365%2C%20then%20as%20per%20above%20article%2C%20select%20condition%20that%20if%20the%20recipient%20is%20part%20of%20that%20DG%2C%20route%20the%20email%20via%20a%20connector%20where%20you%20have%20the%20smart%20host%20defined.%20This%20should%20work%20for%20regular%20emails.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EFor%20sharepoint%20sharing%20invitation%20emails%20the%20behavior%20has%20changed%20a%20bit%20over%20the%20years%2C%20first%20check%20where%20the%20invite%20is%20coming%20from%2C%20whether%20it%20shows%20as%20coming%20from%20a%20general%20email%20address%20or%20if%20it%20shows%20coming%20from%20the%20user%20who%20shared%20it.%20Usually%20if%20the%20person%20sharing%20out%20has%20an%20exchange%20online%20license%20assigned%20it%20should%20come%20from%20the%20user.%20You%20will%20have%20to%20test%20if%20the%20email%20so%20generated%20is%20being%20handled%20by%20the%20CBR%20rule%20you%20setup%20earlier.%3C%2FP%3E%3CP%3EIf%20CBR%20doesnt%20workout%20for%20you%2C%20you%20might%20want%20to%20consider%20setting%20up%20forwarding%20on%20each%20office%20365%20mailbox%20to%20an%20external%20domain%20alias%20which%20is%20not%20added%20in%20office%20365.%20If%20you%20have%20any%20domains%20on-premises%20which%20are%20not%20added%20into%20office%20365%2C%20you%20can%20add%20an%20alias%20for%20that%20domain%20to%20each%20on-premises%20mailbox%20and%20setup%20forwarding%20on%20office%20365%20mailbox.%20I%20havent%20tried%20it%2C%20but%20a%20subdomain%20should%20workout%20as%20well%2C%20so%20you%20could%20theoretically%20add%20a%20subdomain%20alias%20to%20an%20on-premises%20mailbox%3B%20point%20all%20the%20records%20for%20the%20subdomain%20to%20on-premises%3B%20configure%20forwarding%20on%20each%20mailbox%20in%20office%20365%3B%20don't%20add%20the%20subdomain%20in%20office%20365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1735016%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20On-Premise%20and%20Office%20365%20Connectors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1735016%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F67895%22%20target%3D%22_blank%22%3E%40harveer%20singh%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20will%20read%20out%20on%20it.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello, 

 

I have a situation where our company has 2 mailboxes for each employee. 

 

1 on-premise exchange 2016 and Office 365. 

 

We are not looking into hybrid or migrating for now, but we want to see mails sent to our Office 365 mailboxes. 

 

Good example of this is sharing onedrive files, we do not receive notifications in our on-premise mailboxes. They go straight to Office 365. 

 

What we want to accomplish for now is receive the emails sent to our office 365 mailboxes. 

 

Would mail flow connectors accomplish this? 

 

Thanks!

 

 

4 Replies

Hello @seyah96 ,

You are in sort of an unsupported scenario, by default when any user from within office 365 sends an email to another office 365 recipient, the emails are routed internally and will be delivered to office 365 mailbox only, even if the MX record for the domain is pointed elsewhere. For regular emails criteria based routing should work : 

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

First create a Distribution group in office 365 with all the mailboxes present in office 365, then as per above article, select condition that if the recipient is part of that DG, route the email via a connector where you have the smart host defined. This should work for regular emails.


For sharepoint sharing invitation emails the behavior has changed a bit over the years, first check where the invite is coming from, whether it shows as coming from a general email address or if it shows coming from the user who shared it. Usually if the person sharing out has an exchange online license assigned it should come from the user. You will have to test if the email so generated is being handled by the CBR rule you setup earlier.

If CBR doesnt workout for you, you might want to consider setting up forwarding on each office 365 mailbox to an external domain alias which is not added in office 365. If you have any domains on-premises which are not added into office 365, you can add an alias for that domain to each on-premises mailbox and setup forwarding on office 365 mailbox. I havent tried it, but a subdomain should workout as well, so you could theoretically add a subdomain alias to an on-premises mailbox; point all the records for the subdomain to on-premises; configure forwarding on each mailbox in office 365; don't add the subdomain in office 365.

 

Thanks

@harveer singh 

 

I will read out on it. 

 

Thanks! 

Hi @seyah96,

 

not exactly what you want, but there exists a tool that send a notification to an on-site mailbox informing them that they have received an e-mail in online mailbox.

@Victor Ivanidze 

 

Thank you, I'll check this out