Forum Discussion

James Boman's avatar
James Boman
Brass Contributor
Dec 11, 2019

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.

 

 

  • JPSiglos's avatar
    JPSiglos
    Copper Contributor
    Sep 06, 2020
    I work in a very large company and they are using their own domain i.e. sp.mycompany.com. Even our own one drive is customized, i.e. mydrive.mycompnay.com. I am so curious how they did it.
    • Jie Li's avatar
      Jie Li
      Copper Contributor
      Apr 20, 2021

      JPSiglos your company's Office 365 deployment was created on BPOS-D/Office 365 Dedicated, not generic Office 365. At that time during the onboard process, we asked customer to send their wildcard certificate to us so we could manually configure them on F5 load balancers. This was only for large enterprise and government customers (with few exceptions). I don't think this offer still exists today.

  • Random2495's avatar
    Random2495
    Copper Contributor
    Jan 26, 2020
    @james

    Any luck with finding out more about how this was done? Our co is in the same boat.

    • James Boman's avatar
      James Boman
      Brass Contributor
      Jan 26, 2020
      Hi All,

      TL;DR - This is a legacy config, not available for new deployments.

      It turns out in the early history of SharePoint Online (BPOS) there was a group (~75) of large customers (>20,000 seats) that couldn't accept some of the initial deficiencies in the online service - so Microsoft hosted some of the on-premises pieces for them and called it the "Legacy Dedicated" version. As time went on, Microsoft gradually changed out the on-prem parts with the same online parts we are all using today, until all that remained is the custom domain name and SSL handling pieces. While completely supported by Microsoft, this is unfortunately not a configuration that can be requested for new deployments.

      Cheers,
      J.
  • bavmotorwerkz's avatar
    bavmotorwerkz
    Copper Contributor
    Jan 22, 2020

    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!

Resources