Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code Update: Removal of decommissioning Custom Script SharePoint Online Settings from the rego and yaml files #1400

Open
6 tasks
ahuynhMITRE opened this issue Nov 4, 2024 · 0 comments
Assignees
Labels
bug This issue or pull request addresses broken functionality
Milestone

Comments

@ahuynhMITRE
Copy link
Collaborator

🐛 Summary

Microsoft is making updates to the custom scripting configuration options for Sharepoint and OneDrive. The purpose of this issue is to determine if we need to remove or revise policies MS.SHAREPOINT.4.1v1 and 4.2 based on the changes.

https://techcommunity.microsoft.com/t5/sharepoint/removing-custom-scripting-on-sharepoint-sites/m-p/4055563

As a result of #1216, two separate issues will be created to address this setting. This issue will address the removal of all references of policy group 4, Custom Scripting and its policies to include the baselines and rego.

Why does this work belong in this project?

This would be useful because as Microsoft rolls out this update, users of ScubaGear will experience errors as a result of the missing setting. This allows the ScubaGear and the SCBs to be update to date with this setting deprecation.

Implementation notes

Removal of all references to SharePoint policy group 4: custom scripting and its policies in baselines and rego.

Acceptance criteria

How do we know when this work is done?

  • The following files will be updated to remove references to SharePoint policy group 4: custom scripting and its policies
    • SharepointConfig.rego
    • ReportDetails.rego
    • SharepointConfig_01_test.rego
    • sharepoint.pnp.testplan.yaml
    • sharepoint.spo.testplan.yaml
@ahuynhMITRE ahuynhMITRE added the bug This issue or pull request addresses broken functionality label Nov 4, 2024
@ahuynhMITRE ahuynhMITRE added this to the Kraken milestone Nov 4, 2024
@ahuynhMITRE ahuynhMITRE self-assigned this Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue or pull request addresses broken functionality
Projects
None yet
Development

No branches or pull requests

1 participant