Solved

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

Posted on 2016-11-25
6
112 Views
Last Modified: 2017-01-31
Hi

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.
0
Comment
Question by:Milan Duchovny
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 41

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.
0
 

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?
0
 
LVL 41

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).
0
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

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?"
0
 
LVL 41

Accepted Solution

by:
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.
0
 

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 domain.onmicrosoft.com in address space to avoid looping. Kindly refer the link https://technet.microsoft.com/en-us/library/dn163583(v=exchg.150).aspx 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.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

My attempt to use PowerShell and other great resources found online to simplify the deployment of Office 365 ProPlus client components to any workstation that needs it, regardless of existing Office components that may be needing attention.
This article describes how to import an Outlook PST file to Office 365 using a third party product to avoid Microsoft's Azure command line tool, saving you time.
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…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

752 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