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.
Providing the ability to scale from renaming individual sites, to all sites within a SharePoint tenant, while ensuring a consistent user experience across M365 is a complex problem. We have been working hard on this long-awaited feature and are currently validating this with a subset of customers in a closed (no longer accepting nominations) Private Preview Program. As we consolidate their feedback, we will provide another update in the next few months.
great - please also include a function to keep existing links working (aliased) so bookmarks and existing shares do not break when the change is made.
Luis Esteban Valencia commented
only for SPO, or also SP On Prem?
R Webb commented
Although you cannot give an estimated delivery date you surely must be able to give us a broad indication of timescale. Are you talking six months, 12 months, longer...?
So glad to hear it. The lack of an estimated time frame is a bit disconcerting, but hoping it will be in time for our company migration this Summer. I add though that renaming needs to be across all services including OneDrive, Teams, etc and without a bunch of caveats.
Richard B commented
So glad to see that this will be worked on.
Just want to throw a plug in there real quick on OneDrives as they too will need this same renaming functionality since a user's OneDrive is currently set as contoso-my.sharepoint.com, and we need to ensure that they can be redirected to fabrikam-my.sharepoint.com without losing any content.
We understand that this may require our users reconfigure their sync app, but that is a welcome step to this overall improvement.
Required - not to have to delete and rebuild, but this renaming must be fully functional across the entire O365 stack of services it will impact (SP site, Groups, Teams, etc., etc.)
Todd Karakashian commented
This affects the functionality of Teams. If a Channel is renamed, the association with the SharePoint directory is not changed to the new name. It is extremely common to create a new Team and then decide the Team needs to be renamed (e.g., to represent a broader topic than had inspired the creation of the Channel).
We were evaluating Sharepoint until we came across this issue. This is a deal breaker for us. I'm not even allowed to continue Sharepoint evaluation until this gets sorted out.
I add to this chorus. This is a very BIG problem. Particularly because there are character limits to document paths. If someone makes a mistake in trying to find an available name when first signing up, no backup plan besides having to open a new account and transferring all structure and data over? A little nuts.
Chris Duncan commented
SharePoint Admin, we're running multiple companies and we absolutely must rename one of our tenant accounts. Why has this not been addressed? Most businesses go through branding or merger transitions that dictate these changes, why not accommodate your customers?
Sam Smith commented
This is an absolute must.
There is even a drop down on the Site Collection creation page but no way to add use the additional Custom Domains confirmed for that tenant.
Even if we couldn't rename but use a new Site Collection with that newly added Custom Domain :/
Dasiel Fragoso commented
This is a must for any organization. Please make this happen. Really will make a big difference for many organizations that have changed domain names.
I think the SharePoint experiences team told a lie! One and a half years to think about adding a feature the on-premise version can already do? The only reasons I can think of for not allowing this in an enterprise environment are:
1. They dont know how to do it
2. They are too lazy to do it.
3. They make too much money off the migrations and license overlaps
None of these excuses are acceptable when they are billing us and our clients the equivalent of a new server every month. I have a medium sized client with 600 seats and they have just changed names and due to the nature of their business they are stuck having to pay out tens of thousands for a migration they shouldnt have to. The Directors are talking at me about going back on on-premise. Well done Microsoft, GG.
Dan Vail commented
IT MUST BE DONE. I am stuck with a 10 year old name. People buy new domains. IT MUST BE DONE.
Jerry C Kurian commented
Request update of this feature at the earliest. Many customers with the same request. IT Admins in trouble later with the management, because the management wants a different name in the url, from the initial domain.
Steven D'Ambra commented
When is this going to be resolved? Just got off the phone with MS Support and got the same answer as everyone else.
@SharePoint Team: Still thinking? About 1.5 years now....
Anand Nigam commented
absolutely required for many of my customers
Jason Groves commented
This is an essential requirement for businesses. Has it really been posted for a year and a half with no resolution? Rename or add. Please give us something!
Conor McParland commented
At the very least we should be able to add a secondary url. If the initial tenant url can't be removed, we can just ignore it.