Forum Discussion
SPO domain rename duration and problems
Have anyone already done this in production? The dev and test tenant are usually not enough (missing a lot of configurations and data vs. prod) to test this and would love to hear experience from others what can go wrong.
The most worrying part is how long it will actually take in prod. Microsoft says "A domain with 1,000 sites usually takes one to two hours to rename." > this seems quit fast when the actual documentation says "Changing your SharePoint domain name might take several hours to days ".
And will the m365 logs hold the old or new url when you search from the logs?
5 Replies
Hi, we have some limitations while changing the SharePoint domain name from the old one to new one. Check the overall high-level limitations and impacts that we face when changing the domain name below. It includes the steps from scratch like adding the custom domain and renaming the SharePoint domain name using PowerShell.
https://m365scripts.com/sharepoint-online/a-guide-to-change-sharepoint-domain-name-using-powershell/
I've done it to a couple of tenants, and I wouldn't recommend if any larger tenant that you're not in control over the information and feel that the risks are well worth it.
It took 20min for a tenant with 3000 sites, but fixing everything that broke took alot alot longer.
M365 logs will not search the old logs if I remember correctly
Check the limitation list...
https://learn.microsoft.com/en-us/sharepoint/change-your-sharepoint-domain-name#limitationsNicolasKheirallah Did you have a large amount of repairs to make outside of the Low/medium/high level impacts provided by Microsoft?
- Not really to be honest, Just custom webparts and other custom developed stuff that client had broke. But other than that it was pretty smooth experience.
But that being said, bigger company, I wouldn't even consider it.
