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.
An error occurred while saving the commentSerge Ammosov commented
This is really - "the need".
To have an ability to change FQDNs for SharePoint Online site collections and related services Like Video Portal or Teams.
I understand Microsoft concerns about "security" since customer will need a write access at the SharePoint "farm" level but you can make this changes by request, manually or automatically using account with farm level permissions.
In more than 2k users environment this is really a headache for helpdesk answering users questions why the site URL is not "their company" url and why they should store data on non corporate servers, I mean sharepoinonline.com suffix.
In Office365 planning and migration documents MS suggest the Exchange Online as a first part of migration and Deployment, Skype as second and SharePoint Online as a third. But how can it possible when you have working Exchange Online and Skype create ANOTHER organization only for SharePoint Online to be able to have another FQDN? And in this case you will have to pay twice for E3 or E5. This is not applicable.Serge Ammosov supported this idea ·