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.
Any update since Nov 2019 as to when this might be available either in beta or GA?
any news ?? i need this now.... my company change name ed now we need to change all tenant..
Any updates? I have read so many older requests and no one ever responds in the M$ help forums.
I have been nothing but dismayed moving to O365. I thought it would make life easier and it has made it 10x harder. Noting ever works and things like this happen where you are just stuck unless you want to move heaven and Earth. I have 100 things I want to get done and dealing with Exchange and Office problems are not one.
Hello Microsoft, we really need this feature for our business, as like most businesses we go through a rebranding from time to time and having the old incorrect name on our site or products reflects poorly on our IT team. Please fix this or allow for alternate access mappings, as this could be done with the on-prem SharePoint. Thank you,
Joel Kino commented
Any updates on this? Really need this!!!
This is insanity. How is it that you guys can't handle this?
(and I wonder what kind of thinking created this problem in first place - did someone think that Microsoft would never change its own name and accordingly probably nobody else would do so either?)
Lisa French commented
This is what I got from a Microsoft support person when I opened a ticket again with them yesterday:
My name is with Microsoft Office Support emailing in regards to the ticket that was submitted!
I took a look at the older ticket and looked at the uservoice as well! I even asked an advanced team member so I can get a better understanding as I do not have any access to the knowledge of upcoming features. I do not have any concrete information, but it seems that last year there was a beta for tenants to test this feature out. From this testing, the direction on how to accomplish the renaming was changed and is still in development, as they are reworking the ability so the tenant is still functional after processing a SPO rename.
There's not much information that we have regarding this, but I wanted to provide you with atleast something to give you some context as to this feature's development! I do apologize for any inconvenience as well for not having this feature available to you.
Alessandro Riolo commented
Someone at Microsoft needs to be fired for this.
The more the better.
It is simply unacceptable.
You cannot keep this wound open for 4 years.
Brandon Carlson commented
Our tenant name is some garbage temporary name a 3rd party reseller picked for us not realizing it was permanent. We didn't realize this until after a very painful migration.
It's crazy that we can't change this. Or that there isn't some seamless way to migrate to a new tenant account, that copies all the accounts\logs\reports and settings we've changed and created over the years.
We're basically just not using any of these features, because of the link address it creates.
Any update on the status of this enhancement or when we might see it pop up on the M365 roadmap? Thanks.
Robin Wilson commented
Great to hear this is finally being worked on.
J. Benfield commented
Admins on this forum have indicated that this feature is being worked on, and have indicated so for quite nearly a year. However, a call to O365 support indicated that they don't have any information about it or see it on their roadmap. My clients have content across a multitude of Microsoft's cloud services, including SharePoint. To tell them that I need to migrate all this data to an entirely separate tenant just because the company is rebranding is ludicrous. This functionality should have been present since the very beginning, and customers have been asking for it for over 4 years.
I'd be happy with a time frame, at this point. Q3 2020? Sometime in 2021? I understand if that estimate ends up not being accurate, but I'd love to know what the plan is, at least.
Jurgen De Wetter commented
This is a real problem as a silver partner installing a lot of O365 tenants this is a critcal functionality that should be available.
You can't explain to your client that you should migrate their entire environment only for a change in tenant name.
Cato Haukeland commented
I second all the comments here. This is a critical functionality that needs to be implemented soon.
Phil Ketteringham commented
So much for release statements from MS! The only feature released in Q4 2019 is to allow changing of a site name. That is NOT the issue described here. We need to change the TENANT name and I can find nothing in the roadmap. Would you please try providing a new release date for THIS feature - that is a true & viable release date!
Our organization change the name and we want to change the site collection URLs but it's not possible. We want to migrating an entire organisation (likely to include Exchange, Skype, Sharepoint and Onedrive data!!).
Scott Isaacs commented
@matthew.carlson or other admins -- I get that this is a non-trivial change, but it's been requested and voted for at least 4 years. As users, admins and partners, we need to know more than you are providing.
Can you please give another update to confirm:
- Whether tenant's domain name can be renamed, or only non-domain parts of the URL path as indicated in the roadmap.
- Any progress, approximate dates for alpha, beta, RC, etc.
- Anything at all
Honestly, it would be better to not have per-tenant domain names at all than to have a name that is incorrect or out of date.
Migrating to a new O365 subscription isn't an option. That's like telling someone to buy and move to a new house when all they want to do is change the locks on the door.
Mark Wyzykowski commented
We need an ETA date for this feature. It's been far too long without any real update from Microsoft about this lack of key functionality. Matthew Carlson please update us with an ETA. Is it possible that this will be released in 2020? We have customers that need to have this feature due to rebranding and M&A reasons. They are moving to Atlassian Confluence and ditching SharePoint Online. Moving away from Teams and back to Slack. It's a nightmare for us IT Administrators to convince them to stay with O365. At the very least an update would delay their decisions to move away from your service.
Jodi Thomas commented
We are facing the same thing- rebranded, fear migration due to potential data loss. PLEASE tell us an ETA for rollout.