Skip to content

Commit e538e9f

Browse files
committed
clarify that DelayContentSecurityPolicyEnforcement can only be set from mid Feb
1 parent 7f791e6 commit e538e9f

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,9 @@ If the enforcement on March 1, 2026, is too soon because you need more time to r
2424
Set-SPOTenant -DelayContentSecurityPolicyEnforcement $true
2525
```
2626

27+
> [!NOTE]
28+
> Above `DelayContentSecurityPolicyEnforcement` option can be set as of February 9, 2026. If you do this before, the setting is not persisted.
29+
2730
## How Content Security Policy Works in SharePoint Online
2831

2932
When a browser requests a script, if CSP is enabled on the site, the browser checks the script location against the CSP rules. If the CSP restrictions allow the location of the script to be loaded by the browser, the browser proceeds with the request. However, if CSP rules to not allow the location, the browser doesn't load the script and logs the error in the browser's Console.

0 commit comments

Comments
 (0)