Forum Discussion

VesaJuvonen's avatar
VesaJuvonen
Icon for Microsoft rankMicrosoft
Apr 22, 2017

General availability of Office 365 CDN

  We are happy to announce general availability for the Office 365 CDN with new great improvements for the CDN asset handling. Please see following blog post from dev.office.com for addition...
Jim Duncan's avatar
Jim Duncan
Iron Contributor
May 23, 2017

Hello Vesa,

 

I notice that the defaul origins for Public vs. Private are quite different.

Our customer is hesitant to use Public CDN for things that live in Master Page Gallery and Style Library but would love to leverage the same functionality under Private CDN.

 

Current plan is to enable Private CDN (only) and then add to that the origins that would be defaulted for Public.

 

Questions:

 

  1. Is this a viable option?
  2. Will it work with the Publishing integration automatically?

 

Thanks!

 

#MCM #R6 #WUB

Daniel Westerdale's avatar
Daniel Westerdale
Iron Contributor
May 25, 2017

VesaJuvonen

 

 

Is there any guidance or recommendations around the type of new Site Collection and or library we should be creating for our CDN Origins. Do Public and Private CDN origins need to be on separate site collections, say to accomodate the URL rewriting?

 

e.g.  Team Site - SharePoint Online configuration  and Asset Library

 

 

# private 
Add-SPOTenantCdnOrigin -CdnType Private /sites/cdn/ec-cdn


#public 
Add-SPOTenantCdnOrigin -CdnType   Public /sites/cdn/cdn. 

 

 

Added to the above, I am working with a client  that has multple team sites with each site having a /clientnameImages library  which they use to surface event pics on to their respective home sites.  

 

Add-SPOTenantCdnOrigin -CdnType Private */ClientNameImages
Add-SPOTenantCdnOrigin : A positional parameter cannot be found that accepts argument 
*ClientNameImages.
At line:1 char:1
+ Add-SPOTenantCdnOrigin -CdnType Private */ClientNameImages

Do I need relocate each teamname/clientnameImages under /SiteAssets?

  • VesaJuvonen's avatar
    VesaJuvonen
    Icon for Microsoft rankMicrosoft
    May 26, 2017

    You can define any library or folder as a CDN origin. You can use wildcard mapping or relative URL for the origins. In your specific sample, you have a small bug around hte Add-SPOTenantCdnOrigin cmdlet execution. In your case, it should be looking as follows.

     

    Add-SPOTenantCdnOrigin -CdnType Private -OriginUrl "*/ClientNameImages"
    • Daniel Westerdale's avatar
      Daniel Westerdale
      Iron Contributor
      May 26, 2017

      Vesa

       

       

      Thanks. Interesting, as I had tried single quotes and got the error .  Double quotes accepted .  Thanks

       

       

      BTW This issue I am trying to fix we have seen on a few team sites using the new Origin

Resources