Sep 22 2020 08:28 AM
Sep 22 2020 08:28 AM
We have a tenant which is abc.com recently we bought a new company and we want to add their domain def.com into our tenant abc.com so we can assign license E1 and E3 for the users on domain def.com.
Does this configuration will work without interfering with our actual email from our tenant (abc.com)?
Can you provide step-by-step to do so?
At the end we want users from def.com to be part of our tenant abc.com for us it will be much easier to manage with only one tenant!
Thank you for your precious collaboration!
Sep 22 2020 01:43 PM
Provided you own the domain, you can add additional domains to your M365 tenant without interrupting existing domains.
The above shows you how. One thing to note is that if def.com is already set up as a domain in another M365 tenant, then it must be removed before you can add it to yours.
Sep 23 2020 05:36 AM
Good morning HidMov...
Thank you I already consult this article from Microsoft...you know my main concern if I add the domain def.com will I be able to add DNS records (MX records) so the newly domain can send and received email without causing any issue for our main domain which is abc.com
Domain def.com are not in Microsoft 365 yet...this is why I am asking the question to incorporate this domain into our existing tenant some people say this:
You can add the SMTP and receive emails for domain 2 , but NOT send as
Best regards HidMov and have a nice day!
Sep 23 2020 08:52 AMSolution
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?
Sep 23 2020 10:37 AM
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?
Sep 23 2020 12:45 PM
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,