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.
Grzegorz Szypa commented
I think think that it is necessary. So, custom domain have to be available. It is necessary in security point of view.
If 365 is ever going to be a truly Enterprise solution this feature is essential. In todays business world most companies that are enterprise levels have more than just one brand under their umbrella and standing up a new tenant just to keep autonomy isn't a sustainable solution. Branding is key to successful adoption.
Chris Webb commented
Someone else in my org had the name I wanted to use when I set this up. Microsoft wouldn't tell me who had it etc. if I had known I could have gone 2 rows over and had the name transferred but instead opted for a longer alternative. Now org renamed and the name I couldn't get is the one name we go by now. Very frustrating, I'm about to migrate sharepoint and I'm waiting for my CEO to throw a fit about our URL. Please for the love of god implement this. Can't be that hard to just support both applications urls. Pretty sure on prem sharepoint can do it. If we could have multiples that would be ideal then old links work and new links going forward using primary URL would start being used in notifications. Sharing links etc. *praying*. I think you would have even more people voting for this if they knew where to go.
Our sub-domain was selected for us by our former MSP and isn't correct for our brand. It is really important that we are able to amend the tenant subdomain as we cannot deploy OneDrive until this is changed.
This is causing trouble for our hybrid cloud setup as well.
I do agree that it should be possible to update the sub-domain. But, I practice and preach the sharing of links at various customers on a daily basis. If Microsoft makes it possible to update the sub-domain, please build-in an optional redirect, so old links keep functioning.
Yoav Rheims commented
No update yet?
Michael Burke commented
We get many requests for this change. If you can't implement in the near future, possibly include some dialogue in the tenant creation process to show how things are set when picking a subdomain. This would enable customers to pick a subdomain that is more aligned with their branding.
Our organization have gone through a few changes and re-organization. Since the site represents divisions / unit, the name would have a high chance of rename.
Nothing more to say, we desperately need this feature...
it is highly unacceptable that there is not a solution yet to this! We have a client who's name changed due to a merger and have to tell them they can't change their sharepoint domain. Microsoft, you are going to start losing paying customers if you don't fix this ASAP!
Seeing an update from MS, ideally where this falls on a roadmap and release cycle would be amazing! When we signed up for O365 5 years ago there was absolutely nothing that indicated the name could never be changed. We've been wanting to roll out Sharepoint to our users for a year now and have continued to put it on hold because of a sharepoint domain name we can't use (internal political reasons). Tech told me just setup a new account, export email to psts and re-import to new account... yeah right, that's 5 years of email, average user mailbox is 30-40 GB with many having 10-20GB in their online archives... not going to happen!! Worse still the tech tells me there's no way to perform this migration on the server side. What other solutions do people use if they can't use Sharepoint? I'm open to suggestions as I have zero faith this is going to get resolved anytime soon.
"We recognize that this is important for customers..."
No you don't, or you would have addressed it and/or updated this 10 month old status.
Doug Mortensen commented
Please Microsoft. I am a partner and advocate O365, but this really needs to change.
Serge Ammosov commented
This is really - "the need".
To have an ability to change FQDNs for SharePoint Online site collections and related services Like Video Portal or Teams.
I understand Microsoft concerns about "security" since customer will need a write access at the SharePoint "farm" level but you can make this changes by request, manually or automatically using account with farm level permissions.
In more than 2k users environment this is really a headache for helpdesk answering users questions why the site URL is not "their company" url and why they should store data on non corporate servers, I mean sharepoinonline.com suffix.
In Office365 planning and migration documents MS suggest the Exchange Online as a first part of migration and Deployment, Skype as second and SharePoint Online as a third. But how can it possible when you have working Exchange Online and Skype create ANOTHER organization only for SharePoint Online to be able to have another FQDN? And in this case you will have to pay twice for E3 or E5. This is not applicable.
Support informed me the only option is to start a new tenant. This means all licenses need to be canceled, and new ones issued. Ok, fine, I'll do it. Start the process only to find out that due to my license types Microsoft can not refund the cost towards new licenses and I would have to purchase all new. Not going to happen. It has been a daily battle of Microsoft roadblocks and short comings.
Kelly McCormack commented
Where is this solution MS??!! Our company has changed names and now we are stuck with a URL that has an incorrect business name and is not legally ours! I am dumbfounded that this is such a limitation and also the lack of feedback. Currently paying big $$ for a substandard product and service.
Paul Ahern commented
Do we have any update on this from MS. It is prohibitive that we move to the office 365 however within that platform we cannot do the basics like change the domain name on a sharepoint site.
Rune Smistad commented
Very unfortunate not be being able to change domain for collaboration – companies change all the time. Moved from Google – was happy – not so happy anymore
So is MS still thinking about this? We changed organisation name in July last year and I cannot change my SharePoint Site Name? Last update from Microsoft is May 2016? Could we please get this on the roadmap and sorted!
This is completely absurd. Rebranding is hard enough as it is without this kind of nonsense.