Frequently asked questions about SharePoint Domain renames
This article has the answer to frequently asked questions about the SharePoint domain rename process.
In this article, 'contoso.onmicrosoft.com' is used as an example for the old domain name, while 'fabrikam.onmicrosoft.com' is used as an example for the new domain to which you want to change.
The new domain name is already taken by someone within my own organization. What can we do?
You need to contact that person in your organization and get the tenant deleted to free up the associated onmicrosoft domain.
What are the steps to delete a tenant to free up a domain name that is already in use by another tenant? How long does it take?
For instructions and more information, see Delete a tenant.
The new domain name is already in use and taken by a different organization. Is there any way we can use that domain name?
Microsoft doesn’t disclose any information about the tenant that has your desired domain. Domains are taken on a first-come, first-serve basis. You will need to choose a different domain name.
We already have 'fabikram.com' verified. Why do we need to verify 'fabikram.onmicrosoft.com' to rename our domain from 'contoso.sharepoint.com' to 'fabikram.sharepoint.com'? Can’t you simply use fabikram.com to rename it?
To have all the SharePoint URLs renamed from 'contoso.sharepoint.com' to 'fabrikam.sharepoint.com', you must have the 'fabikram.onmicrosoft.com' domain verified.
What happens to the old domain ('contoso.onmicrosoft.com') after the rename?
It is still tied to the tenant as the initial domain.
Can we change or remove the initial domain contoso.onmicrosoft.com from the tenant?
Currently, we don’t support changing or removing the initial domain. It will remain tied to the tenant.
Can we roll back or rename back to our old name in case something goes wrong?
That is currently not supported. When the domain is renamed, we will make sure issues are addressed and the SharePoint domain 'contoso.sharepoint.com' is renamed to the new name 'fabrikam.sharepoint.com'.
Can we bypass the 24-hour minimum and 30 days maximum schedule time check?
No, you must schedule the rename for more than 24 hours and less than 30 days from the current time.
Can we rename a tenant more than once?
Yes, but only after 6 months from the previous rename.
How long does the actual rename take?
It depends on the number of sites and how busy the service is at that time. A domain with 1,000 sites usually takes one to two hours to rename.
How long does the site redirection last?
As of today, Microsoft will not delete any redirected sites that were created as part of a tenant rename but this may change in the future.
What happens to our SharePoint and OneDrive data during the rename? Should we back everything up?
Backup of your data is not required. We are not making any changes to the actual data.
Our third-party backup solutions are failing after the rename. How can we resolve this?
You will need to contact the third-party backup providers to find out if they support the SharePoint Online Tenant rename action.
Scheduling a rename using PowerShell isn't returning anything but zeros. What am I doing wrong?
The most common reason for this is that there are previous versions of SharePoint Online Management Shell installed on the machine and those assemblies cause this issue.
If you have any previous versions installed of the SharePoint Online Management Shell, please uninstall them using the following command:
'Uninstall-Module Microsoft.Online.SharePoint.PowerShell -Force -AllVersions'
Then install the latest version of the SharePoint Online Management Shell.
Should we tell the users to stop using SharePoint during the actual rename? When can they start using again?
The actual SharePoint Tenant rename doesn’t lead to business downtime. However, it can cause brief interruptions if someone is trying to access an individual SharePoint site while it is being renamed as part of the domain rename. We recommend keeping user activity minimal while the rename is running.
What happens to OneDrive sync during and after the domain rename?
While the rename is happening, the OneDrive sync might fail for a user if the rename process is renaming their OneDrive at the exact same time. We recommend stopping OneDrive sync before starting the rename, and then resume after. We understand it might not always be possible for all users to stop syncing their client during the rename.
Some users are complaining that the OneDrive sync client is not working. What can we do?
If sync is not stopped prior to the rename, there might be issues with OneDrive sync after the rename. This is due to the caching within the sync client. The users should sign out, and then sign back into OneDrive after the rename to resolve any sync issues. If that doesn’t solve the problem, they should go to OneDrive > Settings > Account and select Unlink this PC, then re-link the PC. Unlinking and relinking doesn’t delete ay OneDrive data.
I have more than 5000 sites. When will my tenant be eligible for Tenant rename?
We are working on increasing the limits. We appreciate your patience.
What types of sites are considered when determining the total number of sites?
All sites are considered, including SharePoint, OneDrive, Teams, Channel, and Group connected sites.
Will Exchange be affected by SharePoint domain rename?
No, only SharePoint and OneDrive URLs are renamed.
Can we prioritize some sites to be renamed first when the job starts?
Currently, there is no way to prioritize specific sites to finish renaming first. The rename process will rename all sites and OneDrive's in a non-deterministic order.