Skip to content

Commit f505ea8

Browse files
committed
added Resync script sources for solutions in the tenant app catalog FAQ entry
1 parent aee1e4e commit f505ea8

1 file changed

Lines changed: 24 additions & 2 deletions

File tree

docs/spfx/content-securty-policy-trusted-script-sources.md

Lines changed: 24 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Support for Content Security Policy (CSP) in SharePoint Online
33
description: Learn how SharePoint Online implements Content Security Policy to protect against various attack vectors, and how you can ensure your SharePoint Framework components are valid.
4-
ms.date: 03/03/2026
4+
ms.date: 03/12/2026
55
author: andrewconnell-msft2
66
ms.author: bjansen
77
---
@@ -266,16 +266,38 @@ Lists and libraries are performance optimized and heavily depend on local cach,e
266266
When you hit this limit, then the recommendation is to consolidate sources using the model described in the FAQ question above. Note that when the 300 limit is reached, uploading new solutions to your app catalog can be impacted. If you're using an automated deployment system with unique script sources per build, then the 300 limit can be reached soon. Recommended workarounds are:
267267
268268
- Adding script sources in a way that covers all versions (see above)
269-
- Automatically removing the auto added scripts sources using the model described below
269+
- Resync the automatically added scripts source from the tenant app catalog (see below)
270+
- Automatically removing the auto added scripts sources (see below)
270271
271272
New trusted sources will only be added whenever none of the existing trusted sources cover the to be added script source, so if you've already added `*.jsdelivr.net` then a solution adding `https://cdn.jsdelivr.net/npm/jquery@3.6.4/dist/jquery.min.js` will result in nothing getting added given that URL is already covered by an existing script source.
272273
274+
### Resync script sources for solutions in the tenant app catalog
275+
276+
When rolling out CSP, all scripts sources for solutions in the tenant app catalog were added as trusted source, which could have led to too many or redundant script sources. If you want to consolidate the automatically added script sources you can resync them. This will remove the previously automatically added sources, and add them again taking in account redundancy: if there already is a trusted sources that works for the next script source to add, we'll not add that script source anymore. For example, if `https://cdn.jsdelivr.net/npm/` was added for solution 1 and solution 2 wants to add `https://cdn.jsdelivr.net/npm/solution2/` then we'll not add that URL as it was already covered by `https://cdn.jsdelivr.net/npm/`.
277+
278+
To trigger the resync use the [ResyncContentSecurityPolicyConfigurationEntries option](https://learn.microsoft.com/en-us/powershell/module/microsoft.online.sharepoint.powershell/set-spotenant?view=sharepoint-ps#-resynccontentsecuritypolicyconfigurationentries) in SPO Management Shell:
279+
280+
```powershell
281+
Set-SPOTenant -ResyncContentSecurityPolicyConfigurationEntries $true
282+
# IMPORTANT: List the applied setting again as mandatory step to correctly persist the setting (will be fixed)
283+
(Get-SPOTenant).ResyncContentSecurityPolicyConfigurationEntries
284+
```
285+
286+
> [!NOTE]
287+
>
288+
> - The sync can take up to 24 hours to complete
289+
> - Trusted sources for solutions in the **tenant app catalog** will be automatically removed and added again by the sync job, taking in account previously added trusted source to avoid too many entries
290+
> - Trusted sources which were automatically added via **site collection app catalogs** will never be deleted by the sync job, but also not re-added if they were removed from trusted sources
291+
> - Manually added trusted sources will never be deleted by the sync job
292+
273293
### I want to already enforce CSP today, is this possible?
274294
275295
This is possible via using the [ContentSecurityPolicyEnforcement option](https://learn.microsoft.com/powershell/module/microsoft.online.sharepoint.powershell/set-spotenant?view=sharepoint-ps#-contentsecuritypolicyenforcement) in SPO Management Shell:
276296
277297
```powershell
278298
Set-SPOTenant -ContentSecurityPolicyEnforcement $true
299+
# IMPORTANT: List the applied setting again as mandatory step to correctly persist the setting (will be fixed)
300+
(Get-SPOTenant).ContentSecurityPolicyEnforcement
279301
```
280302
281303
### Can I update the trusted script sources list using script or code?

0 commit comments

Comments
 (0)