Score:1

Relay office 365 email via smtp during migration

us flag

I am about to move users to Office 365 email from an old hosted smtp/pop system.

The domain is configured for 365 with the exception of the mx record.

I would like to create the accounts in 365 ahead of the migration and gradually move users over without impacting their current mailboxes.

For the first two test users I have forwarded the old mailbox to the new mailbox using the onmicrosoft.com alias. They receive these forwarded mails to their 365 mailbox. They can work.

A third test user is created in 365 but continues to use his non 365 mailbox until I'm ready to move him.

If the first test user emails the third test user, the email is routed internally within 365 rather than going out to the server in the mx record.

I created and validated a connector to relay all mail via the old smtp server in order for mail from the first user to reach the third test user. This does not work, the email goes to the 365 mailbox. As the third user is not ready to move, it can now not see email from the first test user, only email that did not originate from my 365.

My question is:

Can I use the connector to relay email for addresses that exist in my 365? Or as these are technically internal will they always go directly to the 365 mailbox?

It seems there may be no option but to change the mx and fully cutover to using the 365 mailboxes.

Thanks for any thoughts.

joeqwerty avatar
cv flag
This is probably what you need. Additionally, make note that you can open a support case in your Office 365 tenant to get assistance with this. Office 365 support is always free of charge. It's a great resource so don't be hesitant to use it. - https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/use-connectors-to-configure-mail-flow/set-up-connectors-to-route-mail
yagmoth555 avatar
cn flag
@joeqwerty Good information, didnt knew that way. You cut over the MX but you still feed you onprem from O365's side in big. You should write it as an answer in case it's better for the OP.
Score:1
cn flag

If it's a small business I would tend to cut over directly by changing the MX after prefeeding everyone mailbox PST content to O365 as you have less risk to loose a email in transit.

At the MX cut the Outlook client will stop getting new emails, but the users can use their O365 online via the Microsoft webpage to see their new emails for the time you connect their Outlook to O365.

You would just need to migrate their mailbox's content that wasnt synced (if the feed took a long time to do), but they loose nothing as the local PST will stay be available.

For the prefeed, see there for the step; Use network upload to import your organization's PST files to Microsoft 365 or, if big; Use drive shipping to import your organization's PST files

Rod Scoville avatar
us flag
Thanks, I think you're probably right in not trying to bend it into doing something it shouldn't or maybe won't. You described my alternate method. It's a few hundred users with some pretty large psts. Outlook becomes a reference and they'll all work from web while I do the psts. It would be good to confirm that an "internal" email can't be tricked into hitting a connector though.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.