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.
Corporate merger name change, shouldn't have to manually recreate SharePoint to change URL.
Currently, if an organization goes through a re-branding or re-naming, the only way to change your SP collection URL from companya.sharepoint.com to companyb.sharepoint.com is to migrate EVERYTHING to a new Office 365 tenant. For a small company this may be pretty easy. But for a company with several thousand mailboxes, perhaps Office 365-integrated CRM, this is an endeavor that costs hundreds of thousands, or even millions of dollars in man-hours to complete. And it could all be avoided if there was the ability to rename the site collection URL.
can you share you method and experience Paul. When you think about what this command has to do within the database, its essentially a transaction that runs against every record for the site collection in every table. The bigger the site, the longer the transaction will take to run.
Even a rename everything cmdlet would still run for a long time on a large site.
Share some numbers and your steps please.
Martin Wüthrich commented
SInce the URL of the SharePoint Online Site is based on the Tenant Name (selectedTenantName.onmicrosoft.com), it gets harder and harder to get good, or let me say from the customers accepted, Tenant Names.
With most of the Services, there is no big deal to use the tenant Name, but the Sharepoint Site is highly used and the URL is visible, espeically within sent links in Emails.
So the change to a own URL (based on an added Domain) would be great.
Ricardo Santos commented
Nor being able to use our O365 email-enable primary custom domain in the O365 sharepoint services is bad enough, but not allowing for a sub-domain or a different custom domain as alternate URLs for the private websites is just hurting business - both Microsoft's and their partners/customers/tenants
Please allow adding custom domains as alternate URLs for the private site collections - it's a live saving for any rebranding operation or multi-brand operating company and it allows for proper, company-owned naming on internal resources.
Alternate URLs have been available since MOSS 2007, at least - can't see why they wouldn't be possible to implement on O365, even if it does require some effort and a few changes to the back-end and service logic.
It's really hurting the value of using the Sharepoint part of O365, since tenants see it as detriment to adoption.
It is not accepted that we can not change private site collection URL.
This could be extended to a name of a field: short internal name and long display name. And to Wiki pages, so that the URL can be without space but the display name could contain special characters.
Stuart Anderson commented
The Ability to create a new Library, List,Folders or Views give it a Display Name and URL upon creation without having to name it first as the URL and then rename.
Name = Document Library
URL = doclibrary
Similar to when you create a new site you get both options and i suggest this only because its something ive found not many people know how to do using the current format.
Paul Flatt commented
The Copy-SPSite cmdlet was a step forward but using it as a method of renaming very large site collections is painful and slow.