Add -DelayContentSecurityPolicyEnforcement parameter#1065
Add -DelayContentSecurityPolicyEnforcement parameter#1065Ruchika-mittal01 merged 1 commit intoMicrosoftDocs:mainfrom
Conversation
Added -DelayContentSecurityPolicyEnforcement parameter to control enforcement timing of Content Security Policy checking.
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 63f98f2: ✅ Validation status: passed
For more details, please refer to the build report. |
|
|
||
| > Applicable: SharePoint Online | ||
|
|
||
| This parameter allows administrators to delay the [enforcement of Content Security Policy checking](https://aka.ms/spfx/csp) from March 1, 2026 to June 1, 2026. |
There was a problem hiding this comment.
as this resolves to a learn.more link, let's use it:
/sharepoint/dev/spfx/content-securty-policy-trusted-script-sources
There was a problem hiding this comment.
@samkabue : I on purpose added an aka.ms link as we might want to change this a blog post. If that's an option then let's indeed change to the learn link
There was a problem hiding this comment.
@jansenbe for docs links they prefer linking directly (in this case using relative link). that said let's not block this PR since I know there's the server code waiting for this.
(ideally the aka.ms are, e.g., for sharing with customers, while in here we reference the actual doc link directly)
Added -DelayContentSecurityPolicyEnforcement parameter to control enforcement timing of Content Security Policy checking.