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.
Providing a consistent user experience across M365 that continues to function as expected is a very complex problem which we have been validating in a Private Preview Program.
The good news is that we are once again able to accept additional nominations into the Private Preview. If you would like to nominate yourself you can do so at https://aka.ms/SPOTenantRenameNomination. Please note that a nomination does not necessarily mean that you will be accepted. We are reviewing these on a case by case basis and will only be in contact if accepted.
For more information about renaming your SharePoint domain including the current limitations and process visit https://aka.ms/SPOTenantRename.
This is ABSOLUTELY ridiculous. Such a basic requirement yet there's been no progress on developing it. Agreed there should be a license discount until such feature is made available. Should have never switched from google.
This is kind of unacceptable, this is the "basic" and "essential" feature as a site!!!
We definitely need our own domain name for the sites!
although 11 months have passed, there is still no progress!!!
I can only agree with others. This is a must!
Mark Wright commented
Until this is implemented Office365 will present an unprofessional view to external clients when sharing Onedrive or Sharepoint resources. Until resolved we will use alternative services for sharing.
We should get a discount on the licences due to failure to deliver a business grade service.
This should be a vanity URL, not a company.sharepoint.com domain.
Edgar Sanchez commented
This is an essential feature, what is the current progress on it?
Dan Brandt commented
The dynamics of companies are constantly changing. From acquisitions and mergers to market share and re-branding. The inability to rename a tenant cause confusion for customers and employees. Please add.
Rafa Sáez commented
More than 1k votes for this feature ( https://office365.uservoice.com/forums/273492-sites-and-collaboration/suggestions/7571643-enable-renaming-of-your-internal-sharepoint-url and this )
"Ridiculous" is the word to describe the lack of this feature. Come on, developers, this is a must.
In addition to changing an existing sharepoint site domain, we should also be able to create several sharepoint sites under several different domain names just like we are able to create user accounts with any email address as long as that email address' domain has been verified to be owned by us.
Come on and do this already - it was such a major oversight not to have added it to begin with. When I go to add a new site, the primary domain field is a DROPDOWN indicating that the functionality is already there, but it isn't - Please add this already!
Charlie Rube commented
This is a very practical issue. There are a number of reasons that a different name can be mandatory. At the very least, it should be made abundantly clear at the step of creating the domain in set up how important the decision is. There are situations where the name really needs to be changed but a migration just isn't feasible due to cost and complexity. Even better than a tenant wide change, would be the ability to have the site/onedrive url reflect multiple domains within the company. So users with a company1.com email address would see that domain in onedrive and users with company2.com would see theirs. But I'll take being able to change the name across the board.
Yevgen R commented
ANY UPDATES??? HOW HARD IT COULD BE? MAKE AN INTEGRATION API WITH AKAMAI... GET CUSTOM SSL uploaded by customer for CUSTOM DOMAIN, forward it to AKAMAI, AKAMAI assign it to akadns-entry created for the website and that's all. Why making a big deal out of it ?
We NEED this feature urgently!
Jesse Shauffer commented
We were in the process of rebranding when we launched Office 365 and now we are stuck with our old name for the URL's. This is absolutely ridiculous in 2016. Please keep us posted on your "Thinking About It' status and maybe change to "Working On It"
Brandon Murray commented
It's ridiculous that years after this issue was first encountered by SharePoint Online's early adopters, we still have to request this critical ability!
We are running into this issue at a large, globally run company and need a solution implemented by the MS team to address this deficiency.
This is an absolute must.
it is really important function and hope that you could implement this at closer time
This is a huge requirement, as not only renames can happen, but this has impacted our ability to provide a reproducible test of Microsoft's site collection backups. Currently, without being able to restore a site collection to a new URL or change the URL of the existing site collection, there is now way to verifiably demonstrate that backups did not have any loss of fidelity in industries that have regulatory requirements. This is has impacted financial services clients of mine significantly.