Skip to content

Conversation

@Manoj-Kesana
Copy link
Collaborator

Auto-Labeling Policies Enabled for SharePoint and OneDrive

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new security assessment test (Test ID 35021) that checks whether auto-labeling policies are properly configured and enabled in enforcement mode for SharePoint and OneDrive locations. The test evaluates if organizations have automated sensitivity label classification for file-based content stored in these primary Microsoft 365 repositories.

Changes:

  • Adds PowerShell test script to assess auto-labeling policy enforcement for SharePoint and OneDrive
  • Adds comprehensive markdown documentation with remediation steps and best practices

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
src/powershell/tests/Test-Assessment.35021.ps1 Implements the assessment logic to query auto-labeling policies, filter for SharePoint/OneDrive workloads, verify enforcement mode, and generate detailed reports with policy status and coverage information
src/powershell/tests/Test-Assessment.35021.md Provides detailed rationale, remediation steps, best practices, and reference documentation for implementing auto-labeling policies

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@Manoj-Kesana
Copy link
Collaborator Author

@alexandair - made changes according to copilot suggestion, can you please review it now.

Copy link
Collaborator

@alexandair alexandair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@SagarSathe SagarSathe merged commit 434e5be into main Jan 13, 2026
4 checks passed
@Manoj-Kesana Manoj-Kesana deleted the Feature-35021 branch January 16, 2026 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants