Forum Discussion
Add another Domain to our Office 365 tenant
Hi SilverStar
For your main concern - adding in def.com and pointing the MX records to your 365 tenant will not have any impact to your abc.com domain - it is entirely separate. Your existing users can have a def.com alias if you wish, but it will not change their primary smtp/upn.
You need to ensure you have a plan for the email migration for def.com into your O365 tenant. What is servicing the email at the moment - hosted email, Gmail, Exchange on prem etc - and how will you migrate users to the new domain? Are there on-prem Active Directories?
Hi SilverStar
For your main concern - adding in def.com and pointing the MX records to your 365 tenant will not have any impact to your abc.com domain - it is entirely separate. Your existing users can have a def.com alias if you wish, but it will not change their primary smtp/upn.
You need to ensure you have a plan for the email migration for def.com into your O365 tenant. What is servicing the email at the moment - hosted email, Gmail, Exchange on prem etc - and how will you migrate users to the new domain? Are there on-prem Active Directories?
Hello HidMov
HidMov -thank you so much for those clarifications it's very appreciated.
Actually, they are no plan for users from domain def.com we will not migrate their actual email, we will start from scratch and import .pst file into their Outlook at the end. We simply want them to have a central repository for their emails...our Microsoft 365 tenant will do this.
So at the end our plan is to:
1-add def.com domain into our tenant
2-configure DNS stuff on our tenant for domain def.com
3-create users form domain def.com into our tenant
4-assign license to them...Am I missing something?
Best regards,
Hi SilverStar
I'd personally make the DNS changes one of the last things to do. If you make the MX changes before the mailboxes in O365 have been provisioned, then any email sent to def.com would be rejected until the mailboxes are ready to receive them which would be a pretty big disruption.
1. add def.com domain to the tenant
2. Create users in the tenant
3. Assign licences
4. change MX/autodiscover/SPF records to point to M365
5. You may need to recreate Outlook profiles for def.com users
Depending on how much legacy email and the tolerance level def.com users will have to not having their email, I would look to import the bulk of the psts between point 3 and 4, and do another sweep after point 4 in case any emails have been delivered to the old mail server.
Hope this helps,
Mark