Enable renaming the SPO tenant domain
Currently the site collection URLs are fixed as https://tenant.sharepoint.com and cannot be changed. This does not fit with flexible cloud-based solutions - business needs will inevitably result in an organisation changing it's name during its lifetime (mergers, acquisitions, rebranding etc). While it may not be possible to change it so that entirely custom domains are used (eg contoso.com, instead of sharepoint.com), it must be possible to allow the sub-domain to be changed (eg. newtenant.sharepoint.com)? Please?
Migrating an entire organisation (likely to include Exchange, Skype, Sharepoint and Onedrive data!!) to a new Tenancy is absolutely not a viable option.
We are continuing to validate this long-awaited feature in a Private Preview Program with a subset of customers. Although feedback has been very positive we have identified a few things that we still need to address before we start making this more generally available. We appreciate that this is taking time, however providing a consistent user experience across M365 that continues to function as expected is a complex problem. We will provide another update within the next few months.
Over the years we have changed our brand name but there is no way to change the name on the SharePoint domain. This is creating lots of confusion with our clients and employees, please help
klaas van lunteren commented
How long will this prob take to implement?
please make this possible
please make this posibel
One more customer waiting for this update :)!
Thierry C commented
in addition there is no way to migrate teams, forms, streams, shifts, ...
Migration from the old tenant to another is therefore absolutely not a workaround.
Gabriel Rosa commented
Any news? How we join the private preview program?
Hello Microsoft, any update on this? Thank you,
Von Umali commented
rooting for this feature to come soon!
Allan Melsen commented
I fear this won't come :(
Could be a marketing decision, as the branding they are getting from not granting this functionality is worth more than providing the ability to hide it.... *shrugs*
Bart Jaminon commented
So much has already been said, can only hope this becomes available soon.
Rasna Kandpal commented
It's a feature which was requested by many since very long.
Majority of my users are frequent SharePoint users and have huge storage in OneDrive. Migrating the data will be a hassle for all which brings the gifts of many access/permissions related errors. I have done it before, want to avoid it this time as much possible.
Eagerly waiting for this feature.
Closing in on 5 years now for this feature to be developed... is it being worked on in all honesty or are we just being dragged along?
Hello Microsoft, what is the update on this? When will we be able to rename abc.sharepoint.com to xyz.sharepoint.com, as others have indicated they were able to in your test group, with little broken links.
Yah my jaw dropped when I saw this. Maybe since Microsoft never changed names so they didn't realize companies change names. Not sure why they made a decision like this in the 1st place.
They say make a new tenet, but how do we migrate everything over. It is crazy.
JB Benjamin commented
Do we have any progress on this? We're desperately need to change the subdomain of our Sharepoint instance or at least point it at our custom domain however we still can't even get this done. Has this gone into production? Is it only accessible to a certain few? How do we get access to this feature?
Hi All, Just to update , we are fortunate that for our organization SPO tenant rename has been successfully completed from abc.sharepoint.com to xyz.sharepoint.com. Few links will break in the process but the end result is satisfying !!!
Hope this is coming soon as it's a major pain
we are waiting for this option to migrate data to sharepoint, without this we need too many different accounts and it s much easier if we just have one admin account
They really should have just gone with a random alpha numeric for the name.onmicrosoft.com and this would never have been an issue