Globally published sensitivity labels don't exceed the recommended maximum
Overview
Section titled “Overview”Publishing too many labels globally creates confusion and decision paralysis for users, reducing adoption and increasing misclassification. When users face more than 25 labels, they struggle to identify the appropriate classification, leading to incorrect labels or avoiding the feature entirely.
Microsoft recommends no more than 25 labels in global policies, ideally organized as five main labels with up to five sublabels each. Use scoped policies to publish specialized labels only to specific users, groups, or departments, keeping the global label set focused on common scenarios.
Remediation
Section titled “Remediation”Run it
Section titled “Run it”The check runs as part of the whole assessment, with the ZeroTrustAssessment module installed:
Install-Module ZeroTrustAssessment -Scope CurrentUserConnect-MaesterInvoke-Maester -Pack ZTA -SkipBuiltInLeave out -SkipBuiltIn to run Maester’s own checks in the same run.
About this check
| Severity | Medium |
| Effort to fix | Medium |
| Impact on users | High |
| Pillar | Data, AI |
| Category | sensitivity-labels |
| Product | Purview |
| Feature | Information protection |
| Area | Data protection |
| Licence | RMS_S_PREMIUM, Microsoft 365 E3 |
| Tenant | Workforce |
Product, feature, area and ATT&CK are Maester’s: the assessment does not record them, so Maester keeps them in the pack’s taxonomy.json.
A Microsoft check, part of the Zero Trust Assessment pack. Text from ZeroTrustAssessment 3.1.0, © Microsoft, MIT licence.