Contents
How to host client side web part from Microsoft 365 CDN?
The package-solution.json file defines the package metadata as shown in the following code: The default value for the includeClientSideAssets is true, which means that static assets are packaged automatically in the *.sppkg files, and you don’t need to separately host your assets from an external system.
For information on enabling and configuring the Microsoft 365 CDN in your SharePoint Online tenant, see Enable the Microsoft 365 CDN. Switch to the console and make sure you’re still in the project directory that you used to set up your web part project.
How does a CDN policy work in Office 365?
CDN policies exclude assets in public or private origins by attributes such as file type and site classification, and are applied to all origins of the CdnType (private or public) you specify in the policy.
But hosting resources externally isn’t without downsides. Assuming you’re not hosting your organization’s customizations publicly, it adds yet another location for you to monitor and maintain. So, to deploy SharePoint Framework web-parts in Private CDNs of the Office 365 CDN there’s a new edition of SharePoint Online.
How to host web assets in Microsoft 365?
Microsoft 365 Content Delivery Network (CDN) provides you an easy solution to host your assets directly from your own Microsoft 365 tenant. It can be used for hosting any static assets that are used in SharePoint Online. There are multiple different hosting options for your web part assets.
How to set up Office 365 content delivery network?
To set up the Office 365 CDN for your organization, you follow these basic steps: Determine which static assets you want to host on the CDN. Determine where you want to store your assets. This location can be a SharePoint site, library or folder and is called an origin.