Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
Yes, I know that is expected. But how do I get around this???
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi All,
I am planning to migrate over 2 email domains 1 at a time.
Domain1.com i already have a bunch over users on office365 using a sharepoint add-in. I am planning to migrate email from the current hosted exchange in about 2 months.
Domain2.com i am migrating email this week hopefully (currently just POP email)
When a user from domain2 sends email to a users on domain1 it is routed locally to the users mailbox on office365 which is expected behaviour i guess.
So wondering if someone can give me an idiots synopsis of how i am supposed to get around this..?
I assume i am supposed to create a connector?
I made domain1 an internal relay domain, then i was prompted that i needed to create an external connector.
I went through the wizard to create it (not really sure what i am supposes to put for the address of the external server, i put my MX record but i assume that might not be right and that i then need to do some config on the hosted exchange accepting the emails) then when i went to validate the connector i typed in one of the email addresses and had an error saying it couldn't be an email that is hosted in office365.
Any clues please?
thanks
Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Yes, I know that is expected. But how do I get around this???
Hi AdrianAlessi,
When you send an email from domain2 to domain1 user (they are created in Office 365), it will be delivered internally, and will not check the MX record. It is by designed setting. As far as I know, it is not feasible to use connector to achieve the goal.
Thanks,
Johnny Zhang
and yes i was creating a connector
Hi Johnny,
Yes both domains are verified in office365 under the one tenancy. (IE i have 40 mailboxes and 30 have the email address of domain1 and 10 have email address of domain 2. The MX records are still pointing to old mail servers and i haven't cut anything over yet.
I have deployed outlook mailbox settings to users of domain2 in a second outlook profile ready for switch over.
If a user from domain2 sends an email to a user in domain1 from either office365 configured outlook profile or office365 web client the email will be delivered in the domain1 users office365 mailbox.
For the next 2 months, when a user from domain2 sends an email to a user in domain1 i want it routed via the MX record to the current exchange host's mailbox (currently on sherweb)
thanks
Hi AdrianAlessi,
To understand the situation, could you provide the detailed example regarding the expected mail flow to avoid misunderstanding? Do you mean domain1 and domain2 are verified in Office 365? Regarding” I went through the wizard to create it”, do you mean you create connector in Office 365 EAC?
Thanks,
Johnny Zhang