# Purview Sensitivity Labels: Licensing by Plan and the First Five Labels

> Which Microsoft 365 plans include Purview sensitivity labels, which add auto-labeling, the five labels to publish first and how Copilot inherits them.

Canonical: https://o365hq.com/blog/purview-sensitivity-labels-licensing-by-plan-and-the-first-five-labels
Provider: IT Partner LLC — US Microsoft partner since 2006. Book: https://o365hq.com/book

Published: 2026-11-09 · IT Partner

Sensitivity labels are the one Microsoft Purview control that follows a file out of the tenant and into a Microsoft 365 Copilot answer, and manual labeling is already paid for in Microsoft 365 Business Premium, Microsoft 365 E3 and Office 365 E3. This article sorts the licensing by plan, gives the five-label taxonomy we publish in most tenants, sets the publishing order, explains how Copilot inherits labels, and lists the mistakes that make organizations switch labels off again.

## What a sensitivity label does

A sensitivity label is a tag in the metadata of a file or email that travels with it. What it does depends on four settings.

- **Classification.** The label name, visible in the Office ribbon, Outlook and SharePoint columns. Even alone, it tells DLP, Defender for Cloud Apps and eDiscovery what the item is, so a policy can block external email carrying Highly Confidential files.
- **Encryption.** Azure Rights Management decides who can open the item, what they can do with it (view, edit, print, copy, forward) and whether access expires. It stays with the file when downloaded, emailed or copied to a USB drive.
- **Visual marking.** A header, footer or watermark such as "Confidential - Internal only" stamped into the document.
- **Container labels.** The same label, with different settings, applied to a Team, a Microsoft 365 Group or a SharePoint site: public or private, guests or none, external sharing on or off, and full, web-only or no access from unmanaged devices. A container label governs the site, not the files inside it.

## Which plans include manual labeling

Manual labeling means a person picks the label from the sensitivity button in Office and Teams, or a default applies. Microsoft's licensing guidance places it in these plans:

| Plan | Manual labeling | Container labels | Automatic labeling |
|---|---|---|---|
| [Microsoft 365 Business Premium](/subscriptions/microsoft-365-business-premium) | Yes | Yes | No |
| [Microsoft 365 E3](/subscriptions/microsoft-365-e3) | Yes | Yes | No |
| [Office 365 E3](/subscriptions/office-365-e3) | Yes | Yes, with Microsoft Entra ID P1 for the device and sharing conditions | No |
| [Microsoft 365 E5](/subscriptions/microsoft-365-e5) | Yes | Yes | Yes |
| [Microsoft Purview Suite](/subscriptions/microsoft-purview-suite), add-on to E3 | Yes | Yes | Yes |
| [Microsoft 365 E5 Information Protection and Governance](/subscriptions/microsoft-365-e5-information-protection-governance), add-on to E3 | Yes | Yes | Yes |

Business Premium and Microsoft 365 E3 carry Azure Information Protection Plan 1 and Microsoft Entra ID P1 together, so every manual setting works. Office 365 E3 carries Azure Rights Management for Office 365, which lets a label encrypt, but not Entra ID P1; a container label's unmanaged-device and external-sharing conditions need [Microsoft Entra ID P1](/subscriptions/microsoft-entra-id-p1). The two add-ons sit alongside an E3 license.

Prices are on each subscription page, bound to the current Microsoft price list; the licenses are the customer's own subscription at list price. The [Business Premium versus E3 article](/blog/microsoft-365-business-premium-vs-e3) covers the choice most 20 to 500 person organizations face.

## Which plans add automatic labeling

Automatic labeling is two features under one license requirement.

**Client-side auto-labeling** runs inside Word, Excel, PowerPoint and Outlook: if a document contains a US Social Security number or a credit card number, the app applies Confidential or recommends it.

**Service-side auto-labeling policies** run from the Purview portal against content at rest in SharePoint, OneDrive and Exchange Online: define the sensitive information types, run in simulation mode, read the matches, then turn it on. This is what labels the ten years of files nobody will open one by one.

Both need Microsoft 365 E5, the Microsoft Purview Suite (Microsoft's name since 1 October 2025 for what was Microsoft 365 E5 Compliance), the E5 Information Protection and Governance add-on, or Enterprise Mobility + Security E5 through Azure Information Protection Plan 2. For Business Premium tenants Microsoft sells a Purview Suite add-on, which we quote on request. The [E3 versus E5 article](/blog/microsoft-365-e3-vs-e5-upgrade-cost-2026) covers when an add-on beats the step to E5.

A Business Premium or E3 tenant is not stuck: manual labels with a sensible default cover new content, and DLP on the same plans reads the labels, as the [DLP starter article](/blog/purview-dlp-for-a-50-user-firm-the-first-five-policies-and-what-they-catch) shows. Automatic labeling is what you buy when the backlog is the problem.

## The five-label starter taxonomy

We publish the same five labels in almost every tenant we start, because people can hold five choices in their heads. Labels are ordered from lowest to highest sensitivity, and Purview uses that order to decide what counts as a downgrade and which label wins when Copilot combines content.

| Label | Encryption | Visual marking | Container settings |
|---|---|---|---|
| Public | None | None | Public group, guests allowed, external sharing allowed |
| General | None | Footer "General" | Private group, guests allowed, sharing with new and existing guests |
| Confidential | None at first | Header and footer "Confidential" | Private group, guests allowed, sharing with existing guests only, web-only access from unmanaged devices |
| Confidential - Internal only | Yes: all employees co-author, no external access | Header and footer "Confidential - Internal only" | Private group, no guests, no external sharing, web-only access from unmanaged devices |
| Highly Confidential | Yes: owner assigns permissions, Extract right removed, optional expiry | Watermark "Highly Confidential" | Private group, no guests, no external sharing, no access from unmanaged devices |

**Public** marks material approved for release. **General** is the default: business content not for publication that would not hurt the company if it leaked. **Confidential** marks the item and tightens the container but does not encrypt, so a contract can still go to outside counsel. **Confidential - Internal only** is the first label that encrypts: people inside the company can open and edit it, nobody outside can. **Highly Confidential** is for payroll, board papers and merger documents: the person applying it chooses who may open it, and the Extract usage right is removed so Microsoft 365 Copilot cannot summarize or reuse the content.

Resist a sixth label in the first month; department names and retention periods belong in retention labels and DLP policies. The [Word and Excel labeling article](/blog/labeling-capabilities-in-word-and-excel-helps-you-protect-sensitive-data) shows what each label looks like to the user.

## Publishing order: the label policy sequence

A label policy decides who sees which labels. This order has survived many rollouts.

1. **Create all five labels, in order,** with marking only and no encryption. Confirm the setting that lets SharePoint and OneDrive process labeled Office files is on.
2. **Publish a pilot policy** to 10 to 20 people from different departments: General as the default, no mandatory labeling, no justification prompt. Give it two weeks and read Activity explorer.
3. **Turn on encryption for Confidential - Internal only,** still for the pilot group, and have two users send an encrypted file to a personal address to see what an outsider sees.
4. **Enable container labels.** Set the Microsoft Entra group setting EnableMIPLabels through Microsoft Graph PowerShell, add the container settings to each label, and ask the pilot group to label their Teams.
5. **Publish to everyone,** with General as the default, and add the Highly Confidential encryption.
6. **Add mandatory labeling and downgrade justification** 30 days after the tenant-wide publish.
7. **Auto-labeling in simulation,** for E5 and Purview Suite tenants: a service-side policy for Social Security and credit card numbers, two weeks in simulation first.

## How labels reach Microsoft 365 Copilot

Microsoft 365 Copilot reads the label on everything it touches, and three things follow.

First, encryption permissions are the gate: without the Extract right on a Highly Confidential file, Copilot will not summarize, quote or use it, even when the user can open it in Word.

Second, Copilot output inherits labels. A document drafted from three source files takes the highest-priority label among them, which is why label order matters, and a chat answer that draws on a Confidential file is marked Confidential.

Third, a label is the only control that follows content into a Copilot summary; site permissions stop at the site. The [Copilot oversharing article](/blog/copilot-oversharing-hidden-risk-how-to-fix-it) and the [Purview data governance for Copilot](/services/microsoft-purview-data-governance-for-copilot) service both start from the five labels above.

## Four mistakes we undo most often

**Encrypting too early.** Encrypt Confidential on day one and scanned PDFs drop out of search, a shared mailbox cannot open the attachment and the e-signature tool rejects the file. Encrypt one label first, test it with the pilot group, then widen.

**Breaking external collaboration.** A label encrypted to all employees lands on a proposal emailed to a prospect, who gets a sign-in prompt and gives up. The fix is the taxonomy: Confidential stays unencrypted so it can leave the company, and Confidential - Internal only is named for what it does.

**Label sprawl.** Every department asks for its own label, and eighteen months later the picker has fourteen entries nobody applies the same way. Hold the line at five.

**Skipping the pilot.** Mandatory labeling for everyone on day one teaches people to click the first label in the list, which is Public.

## Frequently asked questions

### Do I need Microsoft 365 E5 to use sensitivity labels?

No. Manual labeling, encryption, visual marking and container labels come with Business Premium, Microsoft 365 E3 and Office 365 E3; E5, the Purview Suite and the E5 Information Protection and Governance add-on add automatic labeling.

### Does Microsoft 365 Business Premium include sensitivity labels?

Yes. Business Premium includes Azure Information Protection Plan 1 and Microsoft Entra ID P1, so manual labels, encryption, markings and container labels all work; automatic labeling needs the Purview Suite add-on.

### Can people outside the company open an encrypted file?

Only if the label's permissions include them. If outsiders must open the file, use a label that lets the user assign permissions, or leave Confidential unencrypted and rely on DLP and container settings.

### Which label should be the default?

General. It marks business content as internal without encrypting it, so nothing breaks, and it makes an unlabeled file the exception rather than the rule.

## Sources

- [Learn about sensitivity labels](https://learn.microsoft.com/en-us/purview/sensitivity-labels) — Microsoft Learn, consulted November 2026
- [Microsoft 365 guidance for security and compliance](https://learn.microsoft.com/en-us/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance) — Microsoft Learn, consulted November 2026 (plans with manual and automatic labeling)
- [Apply a sensitivity label to content automatically](https://learn.microsoft.com/en-us/purview/apply-sensitivity-label-automatically) — Microsoft Learn, consulted November 2026
- [Use sensitivity labels to protect content in Microsoft Teams, Microsoft 365 Groups, and SharePoint sites](https://learn.microsoft.com/en-us/purview/sensitivity-labels-teams-groups-sites) — Microsoft Learn, consulted November 2026
- [Microsoft Purview data security and compliance protections for Microsoft 365 Copilot](https://learn.microsoft.com/en-us/purview/ai-microsoft-purview) — Microsoft Learn, consulted November 2026 (Extract right, label inheritance)
- Subscription pages on this site for the plans in the table, bound to the November 2026 Microsoft price list

## Key takeaways

- Manual sensitivity labeling, with encryption, visual marking and container labels, is included in Microsoft 365 Business Premium, Microsoft 365 E3 and Office 365 E3; automatic labeling needs Microsoft 365 E5, the Microsoft Purview Suite or the E5 Information Protection and Governance add-on.
- Office 365 E3 can encrypt through Azure Rights Management but lacks Microsoft Entra ID P1, which the container label's unmanaged-device and external-sharing conditions rely on.
- Start with five labels: Public, General, Confidential, Confidential - Internal only and Highly Confidential, with General as the default and encryption on the last two only.
- Publish to a pilot group of 10 to 20 people first, enable encryption on one label, turn on container labels, then publish to everyone and add mandatory labeling 30 days later.
- Microsoft 365 Copilot honors label permissions, skips content without the Extract right and marks its output with the highest-priority label among its sources.
- The mistakes that make tenants switch labels off are encrypting too early, breaking external collaboration, label sprawl and skipping the pilot.

---

Publish the five labels to a pilot group of 10 to 20 people this month, with General as the default and no encryption yet. If you would rather have the design, the pilot and the tenant-wide publish done for you, the [Azure Information Protection Implementation](/services/azure-information-protection-implementation) service is a fixed-price project, quoted in writing before work begins.