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.
Thomas Freuen commented
Please Make It so!
This is also critical for our organization, and a must if I'm to move my on-premise Sharepoint Solution to online.
thanks for your consideration.
Please MS make this line up with Domain names which are added to the O365 tenancy,this is critical
this is critical for us. We have a single group of people with multiple business names. Having the business name in the URL is a no go for us.... plus, the shared URL are way too long to include in an email.. (go look a Gdrive and shared URLs... they know the right way to do it)
Sam Easterday commented
We need this feature. This is critical.
SharePoint Experiences Team (Admin, Microsoft SharePoint), I can see the option "Rename Website" in SharePoint Admin Center, but this button is disabled. How can i enable it?
If this option is enabled, does it mean i could change website URL?
Edge browser resists loading resources on Sharepoint Online pages from our other other webservers because of this new Metro privateNetworkClientServer permission that Edge doesn't seem to have, which causes the resources to be blocked.
I've confirmed that a vanilla Edge browser "out-of-the-box" would allow the resources to load if the base domain name of our Sharepoint matched the rest of our web servers. So until someone sorts this out, Edge wont load our images, videos or webservices in Sharepoint and we'll just recommend they use another browser.
This is what's keeping me from using SharePoint.
Bernard Voss commented
Crazy that Microsoft is still apparently only thinking about rolling out this feature this should be top priority. We're currently merging several companies and the owners want to achieve correct branding of url's and not a 4 year old name that nobody uses anymore. But we're stuck with that or we need to setup a brand new subscription and then move all our data one by one to the new version. It's crazy.
this is unacceptable. The ability to use their own domain "sharepoint.company.com" has already caused several customers to opt not to use SharePoint online. inability to change the host portion of the URL is ridiculous. It's hard to believe anyone in a global company like Microsoft ever thought this would be acceptable even temporarily.
Tony Brock commented
Wow, so you really can't change this? That is inflexible, considering that someone hijacked the proper domain we would use in this instance.
Issues in choosing a tenant name needs to *clearly* be made more important to those making the decision. Additionally, there is no way simple availability should be the only deciding factor in tenant name approval.
Dan McIntyre commented
The fact this functionality doesn't exist already is a major problem for our company who are just embarking on a migration to SharePoint Online from on-prem. trying to ask a partner to remember https://portal.company.com is hard enough, never mind https://company.sharepoint.com/sites/portal.
Redirects are all well and good but not the most professional approach. HNSC would suffice.
Ian Moran commented
It's a nightmare.
The problem is only going to get more difficult to resolve. I've started with a new client that has already begun using a tenant name that they now wish to change (because of an inappropriate SharePoint URL)
We now have to consider migration of ODFB, SharePoint, Office 365 Groups, Yammer, Planner, Dynamics 365 to a new tenant (email, the workload that is easy to migrate, is not being used in the tenant)
Preliminary research suggests that no Yammer data can be migrated, Dynamics 365 is a matter of asking Microsoft to re-point billing etc, ODFB & SharePoint will require data migration, not sure about Planner etc.
Seems easier to simply abandon all data and perform a tenant migration - or accept the URL.
I can accept that the mechanics of this are non-trivial - but re-org of a tenant is always going to be a possibility.
Chris Webb commented
Ditto, seems easy but probably isn't or we would have it, but the problem is all the other ties in's to SharePoint where they got stuck making this hard to do. Groups, Yammer, Teams, Video, OneDrive all links back into SharePoint...... cName support would solve this as well.
Shawn Fagan commented
Azure Sites already can handle custom URLs with Custom Certs, and SharePoint already has Alternate Access Mappings (AAMs), this should be a simple problem to fix. I have many clients that would even pay to have this added ability.
UN BE LIEV ABLE! On what planet is it possible for a company the size of Microsoft to not deliver on this kind of key functionality and maintain happy customers????? I wonder if they would be ok with their (Microsoft's) internal staff Sharepoint site url to be http://183yhgajju716.sharepoint.com like ours is currently! This issue has been around too long. Fix it people, fix it! This is INSANE!
Brian Tydings commented
Absolutely imperative to be able to, at the very least, change Site Collection URLs. Custom domain settings would also be nice. We have over 70 domains attached to our tenant, yet can only use the primary domain. Flexibility in regards to total URL configurations are required functionality.
JoLynn Rihn commented
When I changed my domain name and configured it for use with Office 365, I was shocked to learn that I was not able to change the domain name when creating a new SharePoint Site Collection- this is Microsoft, right? I really hope this will be fixed soon. I really think we need the consistency for naming.
This is very difficult when trying to migrate from on-prem where you had full flexibility of DNS and management of websites and domain names tied to SharePoint. I might lose a customer because of this issue.
Trully needed feature!