Mailflow between Exchange 365 and on premise Exchange 2007 after Staged Migration

Posted on 2016-11-25
Last Modified: 2016-11-25

I just started with Office 365 and would like to migrate 40 users from Exchange 2007 using Staged Migration. I’ve done the research and feel that understand the process reasonably well. I understand that during the migration the mail flow between on premise exchange and Exchange Online is done using TargetAddress attributes and once all users are migrated I need to convert on premises mailboxes to Mailbox Enabled Users and point MX record to Exchange Online.
However, when the migration is done, I don’t want to decommission Exchange 2007 as need to keep some service mailboxes on Exchange 2007 and ensure there is a mailflow between Exchange Online and on premise one. I other words I want to achieve that if an email is sent to on premise mailbox, Exchange online would redirected to Exchange 2007. Emails sent from Exchange 2007 should go out straight to internet. Also I need successful mailflow between mailboxes on Exchange Online and Exchange 2007.
So my question is whether I can set up connectors (or something else) between on premise Exchange 2007 and Exchange online so mail flow is achieve between all mailboxes on both Exchanges.

I understand that using Hybrid migration would do the job but it involves installing Exchange 2013 and set up is more complex. Also, we don’t need rich co-existence so Hybrid is just an overkill for us.
Any help would be much appreciated.
Question by:Milan Duchovny
  • 3
  • 3
LVL 38

Expert Comment

by:Vasil Michev (MVP)
ID: 41901439
Keep the MX pointing to on-prem and configure the domain as "Internal relay" in EO (O365 admin portal -> EAC -> Mail Flow -> Accepted domains -> double-click the domain -> select Internal relay). Once you do this, EO will redirect any messages for non-existing recipients associated with this domain to where your MX points at.

Author Comment

by:Milan Duchovny
ID: 41901455
Thanks for the comment Vasil.

I wanted to to have MX record pointing at EO as it does spam filtering etc. and it would remove dependency on on-prem Exchange. But if that's only way I could live with that I guess.
If I implemented your suggestion, I'm assuming that emails sent from on-prem mailboxes would reach EO users using TargetAddress attributes even after I deleted staged migration batch. Is that correct?
LVL 38

Expert Comment

by:Vasil Michev (MVP)
ID: 41901488
Well, if you want to keep the MX pointing to EO, you can simply use a subdomain for all the on-prem mailboxes. Otherwise you need some form of forwarding (regular forwarding, targetaddress based one, connectors, etc).
Are end users causing IT problems again?

You’ve taken the time to design and update all your end user’s email signatures, only to find out they’re messing up the HTML, changing the font and ruining the imagery. What can you do to prevent this? Find out how you can save your signatures from end users today.


Author Comment

by:Milan Duchovny
ID: 41901558
Hi Vasil
Unfortunately the subdomain isn't an option for us.
Do you think that setting up a connector between on-prem and EO would work when using staged migration? Theoretically I don't see a reason why not but it seems that it shouldn't be set up with staged migration.

If had to, I could live with MX record pointing to on-prem and configure the domain as "Internal relay" but can you answer the question in my previews comment - "If I implemented your suggestion, I'm assuming that emails sent from on-prem mailboxes would reach EO users using TargetAddress attributes even after I deleted staged migration batch. Is that correct?"
LVL 38

Accepted Solution

Vasil Michev (MVP) earned 500 total points
ID: 41901629
You need to set the domain to internal relay either way. Connector will work, and is the only solution that matches all your requirements. Just make sure that you dont have matching mailbox objects in the cloud.

I was proposing the simplest solution which doesnt require any connector, but it does require you to keep the MX pointing on-prem in order to avoid mail loops. Just to confirm, mail delivery will work just fine based on the targetaddress value even after you delete the batch.

Author Comment

by:Milan Duchovny
ID: 41901772
Thanks Vasil
I'll go for the connectors set up as that's what I wanted to do from the beginning but when I spoke with Microsoft "engineer" he said it's not possible. I found it hard to believe, thus my question here :-)
Anyway the Microsoft engineer got back to me just now with below response confirming that connectors would work but are "not recommended".

Based on our last phone conversation, we understand that you would like to migrate 40 users to Exchange online using ‘Stage migration’ and want to keep few users in Exchange server 2007. This method is not recommended by Microsoft. However, you may try below mentioned steps to achieve this.
1.      Once you complete migration of all 40 users, you need to change the On Prem mailboxes to mail enabled users and then point your MX record to Office 365 Exchange online.
2.      Set Outbound connector in office 365 to route emails to On Prem Exchange server(Smart host is recommended to route emails to On prem)
3.      Set receive connector in EMC to receive messages from office 365. Add in address space to avoid looping. Kindly refer the link to add Office 365 IP’s in exchange on prem.
4.      Create send connector In EMC to send emails to office 365 and create inbound connector in office 365 to accept messages from On prem server.
5.      Default connector in On prem sends email directly to internet so no changes required.
6.      It is very important to close the firewall and just allow office 365 IP’s in allow list.

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code. This l…
Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…

757 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now