Microsoft Purview sensitivity labels — a deep dive

Sensitivity labels in Microsoft Purview are the mechanism for classifying and protecting content across Microsoft 365. A label is a piece of metadata stamped on a file, email, meeting, or container — and, crucially, a bundle of enforcement that follows the stamp. They're the centrepiece of Microsoft's information protection story, and since Copilot arrived they've been promoted from "compliance project" to "prerequisite for the AI rollout."

What a label does

When applied, a sensitivity label can:

• Apply encryption with usage rights — only defined users or groups can open the content, with optional restrictions on editing, printing, forwarding, and copying. This is Azure RMS underneath, and it travels: an encrypted file mailed outside the tenant stays encrypted.
• Add visual markings — headers, footers, watermarks.
• Set the default sharing link type and scope for labelled files.
• At the container level (sites, Teams, Microsoft 365 Groups): cap external sharing, control unmanaged-device access, set privacy, and bind Conditional Access authentication contexts.
• Act as a condition in DLP policies ("block external email containing Highly Confidential files") — see the DLP deep dive.
• Be mandatory, with a default label applied and users prompted on save or send.

Note what a label without encryption does: mostly nothing, directly — it marks and it feeds policy. That's fine. Classification-only labels plus DLP is a legitimate architecture, and much easier to live with than encrypting everything.

Taxonomy design — where projects live or die

The label taxonomy is the highest-stakes decision, because changing it after adoption is miserable. A shape that works for most organisations:

• Public — cleared for release. No controls.
• General (or Internal) — the default for everyday work. No encryption, no markings.
• Confidential, with sub-labels:
  • Confidential \ All Employees — encrypted, everyone in the org can open.
  • Confidential \ Specific People — the user picks recipients at labelling time.
• Highly Confidential, with sub-labels for the genuinely restricted material — named-audience encryption, no external sharing, strict container controls.

Rules of thumb that repeat across successful deployments:

• Five top-level labels maximum. Users have to make this choice dozens of times a day; a taxonomy they can't hold in their head is a taxonomy they'll misuse.
• Name labels by sensitivity, not by department or regulation. "Confidential" beats "GDPR-Art-9-Special-Category" every time.
• The default label matters more than the exotic ones. Ninety-something percent of content is General; make that path frictionless.
• Don't encrypt General. Broad encryption breaks third-party tools, complicates eDiscovery, and can wall content off from services that legitimately need it. Encrypt where the risk justifies the friction.

File labels vs container labels

Labels apply at two distinct levels, and the two are complementary, not redundant:

• Files and emails get encryption, markings, and DLP hooks.
• Containers (Teams, Microsoft 365 Groups, SharePoint sites) get sharing, privacy, and access posture — the controls covered in SharePoint external sharing.

A site labelled Confidential constrains the container — who can be invited, from which devices — while the files inside carry their own labels. A Confidential site full of General documents is normal and correct.

Automatic and recommended labelling

Users misclassify, so Purview supplements them:

• Recommended labelling — Office suggests a label when content matches sensitive information types ("This document appears to contain credit card numbers"). Low-friction, good adoption tool.
• Automatic labelling — client-side (as users type) or service-side auto-labelling policies that stamp labels on matching content at rest across SharePoint, OneDrive, and Exchange. This is how you deal with the terabytes that predate the labelling project — covered further in auto-labelling policies.

Start with recommendations, graduate to automatic once false-positive rates are understood. Auto-labelling that encrypts aggressively on a noisy classifier is a support-ticket machine.

Copilot readiness

Microsoft 365 Copilot respects labels in two ways: encrypted content the user lacks usage rights to won't surface in Copilot answers, and Copilot-generated content inherits the label of its source material. That makes labels one of the few controls that constrain Copilot by content sensitivity rather than by raw permission — which is why every Copilot readiness checklist now includes "publish a baseline label taxonomy." Pair this with the permissions work in Copilot data access and permissions; labels without permission hygiene solve half the problem.

Licensing

Manual labelling of files and emails is included from Microsoft 365 E3 (and Business Premium). Automatic and recommended labelling, and the ML-based classifiers, require E5 or the Purview compliance add-ons. Container labelling sits in the E3-and-up tier but is commonly deployed alongside the E5 features. As ever with Purview, check the current service descriptions before building a business case — the packaging moves.

Rollout order

1. Design the taxonomy on paper, with the people who own the data — not just IT.
2. Publish labels in classification-only mode (no encryption) to everyone; make General the default.
3. Add container labels to new Teams/sites at creation time.
4. Turn on recommended labelling for the obvious sensitive information types.
5. Introduce encryption on the Confidential tier once support is ready for "I can't open this" tickets.
6. Point auto-labelling at legacy content, report-only first.

Labels are a change-management project wearing a technology costume. Small taxonomy, boring defaults, encryption last — that's the version that sticks.