Skip to content

Commit 7a43a7d

Browse files
authored
Update hosting-webpart-from-office-365-cdn.md (SharePoint#9286)
1 parent 0e3d976 commit 7a43a7d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/spfx/web-parts/get-started/hosting-webpart-from-office-365-cdn.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Microsoft 365 Content Delivery Network (CDN) provides you an easy solution to ho
1414
> There are multiple different hosting options for your web part assets. This tutorial concentrates on showing the Microsoft 365 CDN option, but you could also use the [Azure CDN](./deploy-web-part-to-cdn.md) or simply host your assets from SharePoint library from your tenant. In the latter case, you would not benefit from the CDN performance improvements, but that would also work from the functionality perspective. Any ___location that end users can access using HTTP(S) would be technically suitable for hosting the assets for end users.
1515
1616
> [!IMPORTANT]
17-
> This article uses the `includeClientSideAssets` attribute, was introduced in the [SharePoint Framework (SPFx) v1.4](../../release-1.4.md). This version is not supported with **SharePoint 2016 Feature Pack 2**.
17+
> This article uses the `includeClientSideAssets` attribute introduced in the [SharePoint Framework (SPFx) v1.4](../../release-1.4.md). This version is not supported with **SharePoint 2016 Feature Pack 2**.
1818
> If you're using an on-premises setup, you need to decide the CDN hosting ___location separately. You can also simply host the JavaScript files from a centralized library in your on-premises SharePoint to which your users have access. Please see additional considerations in the [SharePoint 2016 specific guidance](../../sharepoint-2016-support.md).
1919
2020
Make sure that you've completed the following tasks before you begin:

0 commit comments

Comments
 (0)