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.6,070 votesworking on it · AdminSharePoint UserVoice Admin (SharePoint UserVoice Admin, Microsoft SharePoint) responded
We are continuing to validate this long-awaited feature in a Private Preview Program with a subset of customers. Although feedback has been very positive we have identified a few things that we still need to address before we start making this more generally available. We appreciate that this is taking time, however providing a consistent user experience across M365 that continues to function as expected is a complex problem. We will provide another update within the next few months.
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.348 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?