Sp-dev-docs: Is it possible to target a Private CDN location for ClientSIdeAssets?

Created on 15 Jan 2019  Â·  6Comments  Â·  Source: SharePoint/sp-dev-docs

For reasons, we are not wanting to enable a public CDN and the CDN origin for */clientsideassets , so we enabled a private CDN, and added the */clientsideassets to it, and deployed web part in the tutorial following directions. It all works fine, but in looking at Sources in the developer tools, it does not show a CDN folder, and it is sourcing the web part files from the clientsideassets library in the app catalog. Is that the expected result? Or should it show the privatecdn.sharepointonline as the source?


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Needs docs

All 6 comments

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

I was reviewing this a few days ago and recalled this posting, which may still be relevant

https://techcommunity.microsoft.com/t5/SharePoint-Developer/How-do-we-deploy-SPFx-Web-Parts-to-a-Private-CDN-on-O365/td-p/69362

"You cannot deploy SPFx solutions using private CDN at least currently. This is due the fact that the private CDN URL is changing and is not static, which is needed"

Thanks @2toLeadMike ! I should have searched deeper on this.
I would like to see if there is any change to the situation; if not , then I imagine we'll create a public CDN using the -NoDefaultOrigins, and then create the Public origin */clientsideassets , that would limit exposure of other origins in the public CDN.

No, there currently isn't a change to this.

I consider this closed now, and will offer as a workaround the following:

Create a public CDN using the -NoDefaultOrigins, and then create the Public origin */clientsideassets , that would limit exposure of other origins in the public CDN.

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues

Was this page helpful?
0 / 5 - 0 ratings

Related issues

SteIvanov picture SteIvanov  Â·  3Comments

Ralms picture Ralms  Â·  3Comments

acksoft picture acksoft  Â·  3Comments

ken-harris picture ken-harris  Â·  3Comments

StfBauer picture StfBauer  Â·  3Comments