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.
Hi Microsoft and SharePoint Team. Any new Information or updates about this Vote.
I concur with many others. Microsoft have been thinking about this too long. Our initial 365 set-up was setup wrong so we have something that does not mean anything and is being rejected by our marketing department therefore meaning we cannot use a service we pay for.
Recent conversations with support reiterate that the only solution is migrating an entire organisation to a new tenancy. This is absurd in this era of cloud services.
Pretty sure you can rename site collection paths with the right tool or powershell. You just can’t change the domain section of the URL
Frederick Lin commented
For those that have decided to implement naming policies, this is important that we have the ability to rename modern SharePoint site collection URLs. What about sites that were provisioned before the naming policy is put in place? Or what if you change your naming policy and need to retroactively rename site URLs? These are new reasons to the existing use cases in the comments here.
I know this is a bit of a technical challenge since a rename in SharePoint would probably involve a backup/restore to a new site at a new URL (ie. downtime).
Ian Caldwell commented
We are re-branding. Can I change the sitename? Yes, says Microsoft support - with these three easy steps - and two are optional!
From: Office 365 Support [mailto:email@example.com]
Sent: October-12-17 6:31 PM
Subject: Office 365 Ticket #
If you must change the domain of a team site (contoso.sharepoint.com to fourthcoffee.sharepoint.com) you will need to do the following:
1. Create a new Office 365 account and use the name that you want to use for the onmicrosoft.com domain as part of sign up.
2. (Optional) Remove your custom domain from the original account (the one with the team site name that you didn't want)
(Optional) Move any email, files, or other data you may have set up with that account to the new one.
Boian Soloviov commented
Dear SharePoint Team, are you still "thinking about it" after one and a half years? Out company just underwent branding changes and my boss presses me to change the URL. What do we do now?
Singaravelu S commented
This feature is really crucial for us as we are planning to rebrand our domain name and that domain name needs to be used as the subdomain.sharepoint.com
Hope you implement it as early as possible.
Soooo, I noticed at ignite, with geo location, that URL's for sharing links etc. actually change..... Hoping they can use whatever they are using for that, to let us rename URL's to onedrive/sharepoint, because in the demo's we saw, it's like tenant-location.sharepoint.com and it redirects existing URL items to it as well.
Close to 2018 and this still is not an option. Microsoft, please implement
This is still a huge issue for us too. It was set up very badly at first and we need it changed.
Michael Munson commented
Can't you use a similar system to the the asverify CNAME domains used in Azure (https://docs.microsoft.com/en-us/azure/storage/blobs/storage-custom-domain-name#register-a-custom-domain-using-the-asverify-subdomain) in order to generate a SSL certificate for the custom domain? Why is this hard?
Ramon Diaz commented
this is really a requirement to allow the renaming of URLs. I understand the technical challenges to allow this, but i wish for sometime in the future. thanks.
Will try to migrate but worried I will lose data. This should be an option. Many company have many branded sites, too. It is unworkable to have all in separate accounts.
ain't going to happen anytime soon if ever so might as well move away.
How has this not been done yet? We have multiple domains verified in our tenant, yet we can't change the domain. This is becoming a game-changer for us and we will be considering moving away from Office 365 because of this.
Our initial Sharepoint URL consists of domain + country + first and last name. This is not acceptable and the ability to change it is a must item.
Hi all, asked this in the Microsoft Admin AMA today, and got a response, https://techcommunity.microsoft.com/t5/Office-365-Admin-AMA/SharePoint-Online-OneDrive-URL-Rename/m-p/96395#M173
Still nothing to share unfortunately but they are starting to look at it's feasibility!
Yes this is a required feature and will enable reduced IT efforts.
Please implement this ASAP
Then give us customers a refund for sharepoints that we have paid for that do not work accordingly - even after requesting this be done once we renewed our licenses under a new name - you all were NOT able to fix our naming structure to have it be the appropriate tenant - meaning we did what is hell for a customer - we setup an entire new account with our new name - and you all still did not allow us to create a new tenant site - if Microsoft cannot do this - then provide a refund for the monthly expense of a failed product or just fix it - if leadership wants to count that they have all these sharepoint accounts - including ones that do not work - fine - keep the count for whatever purposes - but be customer centric.