Forum Discussion
Getting the Office 365 Private CDN to work
MicrosoftHi Jason Warren,
private CDN works automatically for publishing pages if it refers assets from the CDN origins. This is fully automatic and built in the page processing. Private CDN also works for certain web parts automatically, like defined in the blog post under "Publishing Feature Auto-Rewriting to CDN URLs".
Private CDN capabilities will be currently gradually enabled in the tenants using our release rings, first for first release tenants.
You can see privatecdn.sharepointonline.com as prefix for the assets coming through this process.
BUMP.
I am having the same issue that Jason and Steve are having. I know the URL rewriting is *supposed* to be automatic but it is NOT working. I watched your video, read all the blog posts carefully and followed all of the steps.
I've enabled CDN at the tennant and created the origins:
I've made sure that I've got a major version published, and that "everyone" has read permissions in the document library:
I've put a relative path into the image link property of the image web part on my page:
The page is published. Now it shows up on the page...
But NOT with the rewritten URL (i.e. it's not coming from the CDN):
Does a Private CDN have to be in the same site collection? Or am I somehow misinterpreting how the Origin library path needs to be specified (either when setting it up or when attempting to consume files from it)? Or perhaps there is something else?
A public CDN will be a non-starter for my client, and they don't want to do SPFx if it requires a CDN they have to pay extra for (like Azure, for example), so I really need to make the Private CDN work.