A question about renaming our Azure AD tenant

KJ-2073 20 Reputation points

Hi there, We need to rename our Azure AD tenant to completely get rid of any references to the old business name. This includes Sharepoint and Onedrive links, any references to old business name in the onmicrosoft.com urls and email addresses, and any other references. We need to remove the references from everywhere. I am seeing this article which addresses part of what we need to do: https://learn.microsoft.com/en-us/sharepoint/change-your-sharepoint-domain-name. Looks like it would change the default onmicrosoft domain with the SPO command, which would change the subdomain name for sharepoint and onedrive to the new business name. However, we need to also remove the onmicrosoft email addresses for users and other objects in Azure AD and need to fully get rid of the <old business name>.onmicrosoft.com domain, but I'm not seeing how to do that in this article. Are the onmicrosoft changes I specify possible w/out creating an entirely new tenant?

A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.
1,048 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,212 questions
{count} votes

Accepted answer
  1. Sandeep G-MSFT 15,341 Reputation points Microsoft Employee


    There is no option to delete the onmicrosoft.com initial domain. You can delete the custom domains which were added to tenant. However, when you sign up for a tenant, there is a an initial domain which gets created and it is with onmicrosoft.com suffix. This domain cannot be deleted from Azure AD. If you have added multiple onmicrosoft.com domains, then those can be deleted and can set other onmicrosoft.com domain as initial domain.

    • You can't remove your onmicrosoft.com domain. Microsoft 365 needs to keep it around because it's used behind the scenes for your subscription. But you don't have to use the domain yourself after you've added a custom domain. If you choose to create a new onmicrosoft.com domain, it cannot be removed. You are limited to five onmicrosoft.com domains in your Microsoft 365 environment, so make sure to check for spelling and to assess your need if you choose to create a new one.
    • You can replace your onmicrosoft.com domain after sign-up. While you can’t rename or remove an existing onmicrosoft.com domain, you can create a new one and make it your default onmicrosoft.com domain (your “fallback domain”). For example, if the initial domain you chose was fourthcoffee.onmicrosoft.com, if needed you can create a new onmicrosoft.com domain called fourthcoffeecorp.onmicrosoft.com and set it to be your fallback domain.

    You can also refer to below article to know more about onmicrosoft.com domains,


    If you want all users to stop using onmicrosoft.com then then only option is to delete the entire tenant. Post deletion Microsoft waits 30 to 90 days before permanently deleting your data in case you need to access it or you change your mind. We don't charge you for keeping the data.

    You can refer to below article to know more about deletion of tenant,


    Let me know if you have any further questions on this.

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
  1. Vasil Michev 98,681 Reputation points MVP

    The feature only affects SPO/ODFB resources, and functionalities that depend on them. It's not a full suite-wide "rename", thus services such as Exchange will continue to rely on the old domain. If you really need to "start clean", your best option would be to provision/migrate to a new tenant, with all the corresponding implications.

    1 person found this answer helpful.

  2. KJ-2073 20 Reputation points

    Thanks for the confirming @Vasil Michev and @Sandeep G-MSFT !

    0 comments No comments