Custom/Vanity domain name/URL for Sharepoint Online

[Haneef Ibn Ahmad]

Hi,

I would like to change the default Sharepoint.com URLs to company's URLs, so:

1) contoso.sharepoint.com => sharepoint.contoso.com

2) contoso-my.sharepoint.com => mysharepoint.contoso.com

3) contoso.sharepoint.com/sites/abc => sites.contoso.com/abc

How can this be configured?

Thanks,

[#2]

I found this online ... hope it helps https://social.technet.microsoft.com/Forums/lync/en-US/813d8102-6f29-496e-88b1-b709a568ec84/changing...

[#3]

Thanks for that.

This is an article from nearly 7 years back. I've seen it before, however, was hoping that Microsoft would've added this feature.

Is this still the case or has Microsoft added the option to have vanity domain in private sharepoint online collections?

Thanks,

[#4]

No, unfortunately. You can create a cname on DNS

---

@Haneef Ibn Ahmad wrote:

Thanks for that.

This is an article from nearly 7 years back. I've seen it before, however, was hoping that Microsoft would've added this feature.

Is this still the case or has Microsoft added the option to have vanity domain in private sharepoint online collections?

Thanks,

---

 but that is about it. This is one of the reasons why choosing a good tenant name is important. 

[#5]

I tried to add myspo.contoso.com to point to contoso-my.sharepoint.com, but it didn't work. It gave me this error:
<h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>Ref A: XXXX Ref B: XXXX Ref C: 2018-03-09T23:46:13Z

[#6]

That is not currently possible in SharePoint Online

[#7]

I even tried to access onedrive.contoso.com after adding it as a cname to contoso.onedrive.com.

However, the only one that works is mail.contoso.com to outlook.office365.com.

[#8]

hmm, I see. Thanks for that.

It's pity actually, an enterprise level service like Office 365 should facilitate these.

Even Google Suite has these simple features.

https://support.google.com/a/answer/112038?hl=en
https://support.google.com/a/answer/2518318
https://support.google.com/a/answer/53340

[#9]

while that may be true, Office 365 has hundreds of features that are not available in GSuite and many corporations are leaving that platform because of them.

[#10]

Yup, count me in those too! 😃

You see, just a natural instinct that one doesn't want to lose any of the features in the current environment for an UPGRADE. Upgrade should be additional features, without losing any current ones. 😉

[#11]

I would expect that allowing us to change the urls like that would cause all kinds of problems for many services such as Flow, Teams, Groups, legal holds, records management, e-discovery and more.  

[#12]

You can create a Smart Link with your own DNS that points to a SharePoint Online site collection. We use this for easy reference, but it is just a redirect, not a custom domain.

For example intranet.[domain].com goes to [domain].sharepoint.com/sites/intranet. 

[#13]

I cannot believe I cannot use a cname DNS record to go to the root of my office365 site. Beyond frustrating. 

[#14]

Not in my world.  Small businesses that I manage on both platforms rarely have big "wish" items if they're on Google.  Microsoft is just full of missing, ineffective, or poorly thought-out features that don't work for small business.  

[#15]

I think that this is related to the SSL certificate, and Microsoft can not issue a certificate for each domain.

[#16]

Verizon CDN do issue its own certificate for each custom subdomain, so it seems possible, to get that working if Microsoft would like to.

[#17]

@R_KovalevThey may not be, but what they can do is allow organisations to paste in SSL details like many other cloud service providers do.

The way it normally works is that the process of enabling CNAME support also entails uploading SSL certificate matching the provided CNAME in one step.

[#18]

@Haneef Ibn Ahmad 

I know this thread is old - but after seeing over 200 Office 365 customer tenants I have encountered one with Microsoft supported vanity URL.

https://customer.sherpoint.com -> https://apps.customer.com

Looking at the DNS record for apps.customer.com shows a CNAME to:

prodnetXXXX-XXXXedgevanityXXXXX.sharepointonline.com.akadns.net

and the customer's Office 365 instance uses their custom domain name and SSL certificate (not issued by Microsoft).

How this has been achieved is still a mystery to me - and I am continuing to investigate.

Cheers, 

    James.

[#19]

@James Boman Hi James - really interesting find! Have you discovered any further on how this was accomplished by chance? My organization is interested in pursuing all efforts to finding how this can be done vs standing up a whole new tenant. Would love to hear your efforts/progress thus far!

[#20]

Im wondering about to have a IIS internal in company to fake url's for sharepoint online.
Anyone have try this approach?

then i can create a cname in my internal dns, point it to an iis who move all requests to sharepoint online.