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.4,159 votesworking on it · AdminSharePoint UserVoice Admin (SharePoint UserVoice Admin, Microsoft SharePoint) responded
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 throughout 2019.
Corporate lifecycle is a real and constant pressure in business, often resulting in a need to rename the Office 365 Tenant. To that end we are working on the solution to change the SharePoint domain URL (contoso.sharepoint.com renamed to fabrikam.sharepoint.com). This capability will also then enable the renaming of an individual site collection (contoso.sharepoint.com/sites/abc to contoso.sharepoint.com/sites/xyz).
While we don’t have an estimated delivery date to share at this time, we’ll update your suggestion with details as they become available.
Content types are an essential part of SharePoint. One issue that has been around since SharePoint 2007 is the absence of an overview of all applied content types. Why is this important? Try to delete a content type and you get the message it's still in use. Good luck finding out where. This is very frustrating and time consuming. That's why I vote for an overview where you can see where the content types are applied.294 votesworking on it · AdminSharePoint UserVoice Admin (SharePoint UserVoice Admin, Microsoft SharePoint) responded
A consolidated admin view of where published content types are being used is still being evaluated, but for folks voting for the related use case of “better creation and management of content types” please refer to site designs (aka.ms/spsitedesigns) as a modern mechanism to create/apply content types to site libraries. We are also looking at how this could be more easily supported from hub sites.
- Don't see your idea?