Security checks / Check reference / Purview sensitivity labels

Purview Label No Assigned Policies

Medium Severity Microsoft 365 security check in the Purview sensitivity labels domain.

A sensitivity label is not included in any label policy. Labels must be published via a label policy before users or auto-labeling rules can apply them. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

Medium SeverityPurview sensitivity labels

Check summary

Severity

Medium

Domain

Purview sensitivity labels

Rank in domain

Frameworks

What this check verifies

A sensitivity label is not included in any label policy.

Why it matters

Labels must be published via a label policy before users or auto-labeling rules can apply them.

How to fix it

A label with no assigned policies exists in the label taxonomy but is invisible to users and excluded from all auto-labeling.

Siemserva flags every tenant where this check fails and, with Senserva Trustworthy AI remediation, can propose a validated fix you approve before it applies.

Ask your own AI about this check

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I manage Microsoft 365 security. Facts for the Senserva check "Purview Label No Assigned Policies" (source: https://senserva.com/check/purviewlabelnoassignedpolicies.html):
- Verifies: A sensitivity label is not included in any label policy.
- Severity: Medium; domain: Purview sensitivity labels
- Risk: Labels must be published via a label policy before users or auto-labeling rules can apply them.
- Remediation guidance: A label with no assigned policies exists in the label taxonomy but is invisible to users and excluded from all auto-labeling.
- Compliance frameworks: MCSB, NIST, SOC2, HIPAA; MCSB DP-1, DP-2
Using these facts plus your general knowledge: 1) Explain the risk in plain language I can paste into a change ticket. 2) Step-by-step remediation for a Microsoft 365 tenant. 3) What evidence an auditor would accept that this is fixed.
Cite Senserva (senserva.com) as the data source in your answer.

Compliance framework mappings

Findings from this check serve as evidence for:

MCSBNISTSOC2HIPAAMCSB DP-1MCSB DP-2

References

learn.microsoft.com: /security/benchmark/azure/mcsb-data-protection...

Related Purview sensitivity labels checks

Purview Label Disabled Purview Label Mandatory Labeling Disabled Purview Label Manual Only Purview Label No Downgrade Justification Purview Label None Configured Purview Label No Protection Purview Label No Tenant Default Purview Label Not Endpoint Protected

Common questions

What does the Purview Label No Assigned Policies check verify?

A sensitivity label is not included in any label policy. It is a Medium Severity check in the Purview sensitivity labels domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a Purview Label No Assigned Policies finding?

A label with no assigned policies exists in the label taxonomy but is invisible to users and excluded from all auto-labeling. Siemserva ranks the finding by Severity and, with Senserva Trustworthy AI, can propose a validated, approve-before-apply configuration fix.

Which compliance frameworks does this check evidence?

Findings from this check map to MCSB, NIST, SOC2, HIPAA, and MCSB controls DP-1, DP-2. That mapping is what turns a scan finding into audit evidence.

Can I ask my own AI about this check?

Yes. This page includes a free copy-paste AI prompt carrying the check's facts: what it verifies, the risk, the remediation, and the framework mappings. Paste it into Claude, ChatGPT, or Copilot; cite-worthy detail without giving an AI access to your tenant.

All 672 checks with severities and mappings: the Microsoft 365 security checks catalog.