Allow sharepoint to use a vanity domain for the URL rather than tenant.sharepoint.com
Currently our SharePoint uses tenant.sharepoint.com but I would ideally like this to be changed to intranet.mydomain.com or extranet.mydomain.com. It seems I can't use my vanity domain name for a SharePoint site or have multiple top level sites such as intranet and extranet for different purposes.
Jon Scarpa commented
Agree with everyone here. Please fix this Microsoft!
Josh Butcher commented
We are used to creating an Alternative Access Mappings (AAM) within an on-premise environment should renaming the intranet be required. In our case, the part of the business I am with was purchased and I could then update the intranet domain name to reflect this.
Please provide this functionality, as there are solid use cases to support it.
the M&A and branding drums are loud - but MS doesn't get it..
I agree 100%.
For corporate users to take SharePoint seriously as the company intranet/extranet, it absolutely needs to be inextricably associated with the privately owned domain names such as Shenton refers to "vanity" domain names. Case-in-point: Compliance and security best practices are often written with the primary domain name hardcoded in policies for employees and IT security assessments.
PETE DIDONATO commented
This would be a great addition to the product!!!
So with having to move my public website, my vanity URL on my Intranet is not gone. Basically, I am a small business that has to pay for a static brochure-ware website as O365 pulled the public website and our vanity URL on our tenant is now gone. There does not appear to be a way to have a vanity sub domain for my O365 tenant.
Same for outlook and all other O365 products
Please do something about this feature, we really need to have this one.
David Wallach commented
Yes, we also went though agency name change recently, unfortunately right after migrating to O365. So to endure another migration (all content from SharePoint, OneDrive and Email!) just to achieve a more appropriate URL seems to be an awfully high price to pay for this truly common occurrence. This really needs to be addressed. Thank you!