This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 46%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPO%3C/text%3E%3C/svg%3E)
Specifically, I am keen to understand what will happen to email because another Admin runs an Exchange server for ourcompany.com and I want to be certain that creating an Azure Tenant for mycompany.com will not impact email services already configured.
Where can I read about how email is integrated into Azure when a tenant is created? I am struggling to find the appropriate documentation.
I would assume that since I am in control of my DNS settings for the domain that nothing would change without me explicitly changing the DNS records with the registrar but I have learned the hard way not to assume such things.
Can anyone point me in the right direction to read up on how to safely add a tenant for mycompany.com without impacting our current email delivery? Maybe I am being too cautious, but I do not want to hit the "Create a tenant" button without first fully understanding what will happen to email for that domain.
please and thanks
Sorry - I can't see where to edit the question so I will correct something here. The current email is on Exchange for mycompany.com and the tenant I want is also mycompany.com - they are not different domains as the original post said.
It is all about having an Azure tenant for mycompany.com without impacting existing email services for mycompany.com.
As you correctly mentioned above, nothing will change until you update your DNS records. Azure as a (set of) service doesn't care about Exchange at all. Microsoft 365 does, and if you sign up for an M365 tenant, you will get a default tenant.onmicrosoft.com domain. You can then decide whether to add your custom domains, and in the case of Exchange Online, whether to consider the domain as "authoritative" or "internal relay": https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/manage-accepted-domains/manage-accepted-domains
While the "add a domain" wizard will insist on changing all DNS records, this step is totally optional and up to you. Until you are ready to change your DNS records, the only thing that will be affected are internal emails sent within the M365 environment.
@Paul O'Rorke
I just wanted to check in and see if you had any other questions or if you were able to resolve this issue?
If you have any other questions, please let me know.
Thank you for your time and patience throughout this issue.
----------
Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.
Perfect, this is what I wanted to hear:
"While the "add a domain" wizard will insist on changing all DNS records, this step is totally optional and up to you. Until you are ready to change your DNS records, the only thing that will be affected are internal emails sent within the M365 environment."
Thank you for this.