Using a CDN for Static Resources on SharePoint 2016

[This post is based on the SharePoint 2016 Preview — Functionality is not guaranteed to be supported, configured identically, or exist in RTM]

SharePoint 2016 includes a feature to use a CDN for static resources, such as JavaScript. And what better CDN to leverage than SharePoint Online? Configuration is fairly simple. Enable CDN, configure it to point to static.sharepointonline.com, and set up a Side by Side token which matches your farm build number.

The PowerShell:

Using Fiddler, browsing to a home page, you should now see requests to http://static.sharepointonline.com/bld/_layouts/15/16.0.4316.1217/init.js, as an example.

You can also configure your own personal CDN using the same method. As long as the CdnPrefix does not contain “static”, you do not need to set a SideBySideToken value.

3 Comments

  1. Nice article. I’d assume the Azure CDN service would work equally well for this purpose?

    • I would assume so as well, but that isn’t something I’ve tested. Note there is a check for the word “static” in the URI and may be a dependency to use a CDN. That is for another blog post.

  2. Pingback: SharePoint & Office 365: Recopilatorio de enlaces interesantes (II)! - Blog de Juan Carlos González en Geeks.MS

Leave a Reply