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.
Thanks for your feedback! Just a note to let you know that we’re building your suggestion now. We plan to increase availability to this feature as we continue improving the tech, and ensuring a smooth experience across Office 365 following the URL changes in SharePoint Online.
The only thing more frustrating than not having this functionality is the utter lack of communication from Microsoft regarding status and delivery expectations.
While addressing the issue has been procrastinated internally within Microsoft for the last four years - at a minimum there needs to be some official documentation for how customers should proceed with creating a new SPO tenant and moving associated Microsoft 365 resources with minimal impact to clients and other services.
One of several thousand pissed off customers.
Jeff Z commented
We would greatly benefit from this feature being added as well.
Mathias Gläser commented
PLEASE ADD THAT OPTION SOON
PLEASE ADD THAT OPTION SOON
PLEASE ADD THAT OPTION SOON
It is insane that this capability doesn't exist. Please please please fix this! Until it is done, I have had to stop using SharePoint to distribute information and share files with my entire company.
Harmen Wessels commented
Any ETA on when this feature will be available?
In the SharePoint roadmap I now see a feature called 'SharePoint site Url rename' (Featured ID: 56205). From there a reference to the sharepoint blog is made. In the SharePoint Updates blog I see a reference to this UserVoice at the section 'Site rename':
In the example on that page it's not actually the tenant-id renamed, but a sub-folder in the domain:
"So for example, if you have a site https://contoso.sharepoint.com/sites/Develpment, using the SharePoint admin center you can rename the site Url to correct the incorrect spelling of “Development”."
Is the example wrong here, or is the wrong UserVoice referenced?
make its so! we really need this!
unfortunately we beating a dead horse voting on this post... Microsoft have already confirmed this request has been delivered in the form of being able to rename the site name and not the sub domain as per my ticket raised with them (see post below)
See new user voice and vote on it to get the ball rolling again
Elie Saliba commented
Would you pls communicate when this features will be available. Yes It is a must change for a big design mistake.
Would you pls do some advertising about this design and the trap that people will have to avoid: office365 -> Sharepoint.
People feel incapable to manage their technology the way that would like which is against the flexibility that cloud should offer.
Eugene van der Merwe commented
<3 thank you for your consideration. We'll hold off our merger until this feature is in place, we don't want to embarrass our 1000 employees with the old defunct name.
steven sarginson commented
This is honestly crazy that you still cannot do this. Imagine the number of people not using Sharepoint because they accidentally set it up as bobjones.sharepoint.com. Unbelievable and unacceptable
They understood the request. I was able to participate in the Pilot and did exactly as described domain1.sharepoint to domain2.sharepoint. That was last June.
re-reading the comments from Microsoft on this case it appears that they have misunderstood the requirement from the user who submitted this request.
Microsoft have come back and said they are developing the ability to
The second feature is developed and working now I can confirm and I suspect Microsoft think the issue is now resolved.
However its not what we asked for!
I am going to create a new user voice that is clear to Microsoft and ask that you share and vote on the new request since its clear Microsoft are no longer monitoring this request and the Program Manager appears to be no loner working at Microsoft to provide further feedback.
Microsoft, please give us a status update on this, which is the number 1 requested feature in Office 365 and SharePoint. Thank you.
Please provide any sort of update on this. Something just to let us know what is happening! It's very disconcerting that there has been so much support of this idea and that there's been zero communication for 4 Months!
This has cost 5 people their job in a friendly company within the last 2 years already, due to burn out... and more will follow... because the Management does not accept it, the ITI People have to fulfil the Needs with literally 420h/month and more.. they are losing staff to the pressure and new guys are like coal-pieces to be burned. All started when the Company growed and renaming, fusions, Joint-ventures etc. became a Thing - currently the Name in this Company is chaning for each Project, and the tenant Migration would be needed every like 6 to 9 months, particularly the new Project Partner don't want to see the Name of a concurrent Company that was a Partner a year ago in their ACTUAL Projects, that is Business critical. Said friendly Company is avoiding SharePoint and OneDrive totally and using third Party or self made Shares and this is what produces so much over-time... SharePoint in particular is just not useable, it is non existent for this Company.
based on a simple investigation it appears Matthew Carlson is no longer with Microsoft and he has invested interests in his startup TouchMail..
Guess this project has fallen by the wayside.
Contacted Microsoft they have no idea about this project neither is it on their Road Map or radar. I asked that they please update this user voice and they requested that we provide feedback in Windows Feedback if we want this to progress any further. Told them we were asked to create the request in UserVoice the feedback is there we have enough votes and we have confirmation from Microsoft that this is in development for over 2 years already... It would be counter productive to start placing feedback elsewhere and manage feedback for a request in several different channels.
So i got to migrate exchange, OneDrive & SharePoint from one tenant to another to change the SharePoint domain name... Glad the customer is willing to pay for this after explaining the issue is with Microsoft.
Nick Orlich commented
We are also in dire need for this feature, please finish this!