An error occurred while saving the commentJohn 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?