Change SharePoint Site Sub Domain
business needs will inevitably result in an organisation changing it's name during its lifetime (mergers, acquisitions, re branding etc)
Migrating an entire organisation (likely to include Exchange, Skype, SharePoint and OneDrive data!!) to a new Tenancy is absolutely not a viable option.
The domain for my company was not purchased at the time of the Office 365 subscription and now we can't change it for Sharepoint?!?. There was ZERO warning about this and this is incredibly frustrating and an AWFUL way to introduce the new migration of the company on to Microsoft. Microsoft, you guys ROYALLY messed this one up. :-/
Jean-Paul de Jong commented
This is an elementary function, it simply needs to be available in a connected world. We do it for our customers when they change their legal name, hey we even do it when they just ask nicely ;)
This is a much needed feature, in fact a required feature!
Much needed feature!
GSuite allows this feature...
Travis Ryals commented
We need the ability to change the Office 365 tenant name; specifically SharePoint.
SharePoint is a great collaboration platform but the control over branding (URL) on a tenant is imperative.
Shushanth Gopal commented
We need ability to change the domain name for SharePoint.
Thyran John Wright commented
@John Smith thanks for your feedback. Microsoft have confirmed they are no longer working on the previous case because they feel they have completed the requirement by allowing us to rename a site. Even though this is not what was asked for.
Hence the reason for starting a new idea.
The below post with over 5000 votes is being ignored by Microsoft
Freddy Kuong commented
Our organisation just bought a domain and it's different to what we use the first time when we register at Microsoft, so, we need to change the name and it's not possible.
I do agree that this request is very important and needs to be addressed by Microsoft.
Even aliasing would be a plus at this point (keep the old subdomain to preserve backups, but have the new one redirect). Not an ideal solution for many, MANY reasons, but better than nothing.
John Smith commented
Microsoft didn't misinterpret the previous UserVoice post for this issue. It was very clearly stated in the User Voice which has nearly 5000 votes that it was the subdomin that we were requesting to be changed. They know exactly what we are talking about. They had a pilot program for the SPO Rename which took place last year with no promises that your sharepoint or links would not break after performing the rename. So you had to sign a waiver that you understood and if you were chosen for the program the rename process was performed. But of course no feedback from the users who went through with the process. i provided a link to that pilot for those that were interested. Rightly so nobody in their ripe mind would sign up for such a task unless they had an entire 365 backup and could easily restore back to a working state again. Here was the original post with 5000 votes. i dont see how this post was not clear in the verbiage that we are requesting the ability to change the subdomain. Read the original post below. Now you have created a new post with only 52 votes and it's going to take forever to get any visibility from Microsoft. At least previously they were writing back once per year. Your post is about 5% clearer then the original post below.
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?
domagoj svagelj commented
This feature is a MUST have. Our SharePoint tenant is somehow named after an admin user and can not be changed, so at this point SharePoint site is almost not usable.
Adam Tsiopani commented
We've just completed a lengthy setup of a new domain on our account for rebranding: import many users, resolve issues, map devops users, create folder structures, etc. Days have been spent on this. And we cannot change the subdomain to our new brand, even if we completely remove the old domain brand from our account. This is very frustrating! Re-migrating to a new account is not viable at this stage. Please add ability to either change subdomain or add additional aliases for users with multiple domains!!!
R Webb commented
The original request to change sub-domain has nearly 5,000 votes.
Microsoft know this is a serious requirement. There is no need for people to keep explaining why this is such an important and fundamental feature.
The question should be: "Why is Microsoft ignoring this?"
Thyran John Wright commented
I recently recreated a new tenant and moved domain, email, email protection, OneDrive, SharePoint sites and libraries.
1 user took over 24 hours to successfully migrate with having to download all the data locally and then re-upload it into the new tenancy.
Not a financially viable option for any client no matter the size. I will in future be telling clients who want to change name that at this stage its uneconomical until Microsoft provide a way for us to do this within the same tenancy and that although Microsoft have committed to the last two years into developing this project we have had no updates in the last several months about the progress and that they should not keep their hopes up for several more years or at least until we receive another update from Microsoft as to the progress of this feature request on this user voice as well as the one with the required votes.
Susan Bozorgi commented
I am in great need of this. I have a law firm, and had to change my domain pursuant to bar rules. Why should I have to migrate everything to a new Office 365 site - and I use my Sharepoint to share files and the link shows the old firm domain which we can't use anymore. Microsoft please deal with this!
Davis Cotter commented
This is a simple and concise request, MSFT surely cant misinterpret a second time....
Please support by voting for this domain change feature.