Content reviewed: 12 October 2026
“We want to label contracts Confidential. Does everyone need E5?” A licence name alone does not answer that. Manual labelling, encryption, automatic content detection, DLP and meeting protection are different features. Define the required behaviour and the people who will use or benefit from it first.
Start with what the label must do
A sensitivity label is a classification tag defined in Microsoft Purview and published to users. Depending on its settings and the supported app, it can mark a document or email, add visual markings or restrict access through encryption. A label called “Confidential” does not encrypt anything by itself. Microsoft describes encryption as an optional label setting.
It's useful to separate the three questions: who assigns the label, what the label enforces after it is assigned, and whether another rule responds to the label. Manually tagging a file is a different capability than auto-tagging based on sensitive data. A DLP policy that tracks email content is a different capability than a rule that uses a label as one of its conditions. And the label for a Teams meeting does not automatically take over the label license for the file.
| Business requirement | Feature | First check |
|---|---|---|
| Employee labels a contract in Word | Manual file labelling | Supported client, published label and user licence |
| Only named people can open a confidential contract | Label with encryption and access rights | Rights configuration, external sharing and Rights Management |
| System detects personal data and applies a label | Client-side or service-side automatic labelling | Specific automation feature and higher-tier rights |
| Policy checks sensitive email and files | DLP for Exchange, SharePoint and OneDrive | User licensing and DLP rule scope |
| DLP acts on an existing label | Sensitivity label as a DLP condition | Supported location, feature and licensing matrix |
| Label restricts Teams meeting options | Meeting sensitivity labels | Separate meeting and Teams Premium requirements |
This table is a task map, not a one-size-fits-all SKU price list. Microsoft's Purview Overview varies by function, data location, and user group that benefits from protection. Each line must be assigned to a specific scenario before ordering.
Manual labels do not require E5 by default
The current Purview sensitivity-labelling matrix lists manual labelling for Microsoft 365 Business Premium and E3, among other plans. A company that wants users to label documents and emails in supported apps does not automatically need to move everyone to E5. Verify the specific app, version, platform and policy publication to the right group. Microsoft’s getting-started guide covers creation, publication and testing.
There are two levels to encryption. The license must allow for appropriate protection of information; at the same time, the Control access option must be explicitly enabled for the label and the rights must be set. Encryption documentation also notes that Azure Rights Management is enabled and that changing the label configuration later may not automatically overwrite all already tagged data in the same way. Therefore, test a new document, an existing document, and sharing outside the organization in the pilot.
For encryption, choose Configure access control settings under Control access and configure rights. Merely opening that section is insufficient: it also offers the opposite action, removing access protection.
A watermark or header is a visual marking; it does not make a file inaccessible to an unauthorised person. Encryption is also not a complete workflow on its own. Recipients need the right permissions, their app must support the configuration, and the organisation needs an exception and recovery process. Begin with a short set such as Public, Internal and Confidential, then expand it after testing.
Not every E5 covers the same automation
| Feature | Examples of coverage | Boundary |
|---|---|---|
| Manual document/email labels | Microsoft 365 Business Premium or E3 | Check app support and policy publication. |
| Client-side automatic labelling | Microsoft 365 E5, an eligible Purview add-on or EMS E5 | EMS E5 is different from Microsoft 365 E5. |
| Service-side automatic labelling | Microsoft 365 E5 or an eligible higher Purview plan | The matrix lists EMS E5 alone for client-side automation only. |
| SharePoint library default label | A separate higher-tier Purview entry | Not automatically part of basic manual labelling in Business Premium. |
The table follows specific Purview matrix rows. For add-ons, check the eligible base licence too. “E5” without the full product name is insufficient: EMS E5 and Microsoft 365 E5 can grant different automation rights.
Automatic labelling needs separate rights
Suppose a user writes a contract containing personal identification numbers and Office should recommend or apply a label automatically. That is different from manual labelling. Microsoft distinguishes client-side automatic labelling in Office apps from service-side policies for SharePoint, OneDrive and Exchange. Its automatic labelling guidance describes separate setup paths. The Purview licensing matrix lists higher-tier rights, such as Microsoft 365 E5 or an eligible Purview add-on, for both client- and service-side automation. Business Premium or E3 alone does not grant this whole automation scope.
Run service-side policies in simulation first; client-side automation does not have the same simulation mode. The documentation also distinguishes SharePoint/OneDrive files from Exchange email: Exchange policies evaluate messages being sent or received, not historical mailbox content. No results for old messages need not mean a missing licence. After enabling the policy, verify actual labelled items, not just simulation matches.
DLP and labels have separate licensing
Purview DLP for Exchange Online, SharePoint and OneDrive is available in Business Premium and E3, among other plans. A policy can inspect sensitive content in email and files. This does not imply rights to Teams-message DLP, endpoint DLP, automatic labelling or every advanced condition. Microsoft lists separate requirements for those features.
If a DLP rule must respond to a particular sensitivity label, check the supported locations and condition behaviour, then the exact licensing entry in the current matrix. Do not conclude that every integration is covered simply because you have both labels and DLP. Describe the intended rule precisely, for example “block emails labelled Confidential from leaving the company”, and confirm entitlements for everyone whose content the policy processes.
A control may be visible in the portal even when not every affected user is licensed. Microsoft explains that each user who benefits from a feature needs the appropriate rights. Shared locations require a function-specific assessment of owners and members. One administrator E5 licence does not unlock an E5 feature for the entire tenant.
Assess Teams meeting labels separately
“Business Premium includes labels” does not answer a question about meetings. The Purview matrix distinguishes manual labelling of scheduled meetings from sensitivity labels for Teams online meetings. For the latter, it lists higher Purview rights together with Teams Premium. Define whether the label should affect the invitation, meeting controls or content before buying add-ons.
The topic is related to our overview of Teams Premium and Rooms, but the meeting room license and the meeting protection license are different questions.
A site label does not encrypt every file
Group/site labels control the container, including privacy, external sharing and unmanaged-device access. Documents do not automatically inherit them or receive item encryption or markings. A library default label for files is a different feature with separate configuration and licensing. These controls are not interchangeable forms of “SharePoint protection”.
| Situation | Check |
|---|---|
| Internal site, uploaded Confidential document | The label mismatch alone does not block upload; a specific rule must address it. |
| External-user access disabled through label settings | Existing guests do not automatically lose access; check their memberships and permissions. |
| Unmanaged-device restriction | Requires related Conditional Access configuration; a weaker label cannot override stricter tenant settings. |
The container guide documents these exceptions and dependencies. Test actual access for an internal user, an existing guest and a disallowed device. Settings available to site owners should match the authority you intend to delegate.
Teams attachments differ from chat text
Sensitivity-label DLP conditions can evaluate attachments stored in SharePoint or OneDrive; that does not apply the same condition to Teams message text. The documentation also excludes legacy .doc, .xls and .ppt formats from the stated condition support. Check location and format first. Buying a higher licence does not remove an unsupported scenario’s functional limitation.
With mandatory label selection in Outlook, also test actual sending enforcement: the documentation says selecting the label in that prompt may not trigger a fresh policy tip even though the DLP action remains enforced. No warning and successful unauthorised sending are different test outcomes.
A decision model for 120 users
A company has 120 Business Premium users using manual labels and wants automation for selected contracts. First identify the policies, services and people benefiting from the new feature, rather than merely counting contract authors. Client-side recommendations for a selected group differ from a service policy over a shared site. Record feature, target location, access roles and qualifying plan. The advanced add-on order is not ready until that scope is confirmed.
Plan a licensing and technical pilot

- Write down three to five scenarios. For example, label a Word contract, encrypt a proposal for outside counsel and block an email marked Confidential. Identify affected users.
- Separate the capabilities. State whether each scenario needs manual labels, encryption, automatic labelling, DLP or meeting protection.
- Check the current matrix and assigned SKUs. Business Premium or E3 may cover basic use; verify advanced functions separately. Resolve unclear entries with Product Terms or a licensing partner before purchasing.
- Publish a small label taxonomy to a pilot group. Test documents, email, external recipients and supported clients. Avoid dozens of labels at the start.
- Assess mistakes and user experience. Check whether people understand the labels, legitimate sharing remains possible and encryption enforces the intended rights. Simulate automation first.
- Assign ownership. Decide who changes labels, approves exceptions and reviews effects on existing files.
Frequently asked questions
Does everyone need E5 for manual labels in Word?
Not by default. Microsoft’s matrix lists manual labelling for Business Premium and E3, among other plans. Verify the specific function and each user’s entitlement.
Does a label named Confidential encrypt the file automatically?
No. Encryption is an optional label setting. Configure access rights and satisfy the technical prerequisites; the name alone is not a security control.
Is one administrator E5 licence enough for automatic labelling of all files?
No general rule permits that. Microsoft requires suitable rights for users benefiting from the Purview feature, including those within the policy’s scope.
Does Business Premium DLP include Teams chat DLP?
Do not infer that from the general term DLP. Microsoft lists Exchange, SharePoint and OneDrive DLP separately from Teams-message and endpoint DLP, with different licensing requirements.
Is a sensitivity label the same as a retention label?
No. A sensitivity label classifies content and can control access. A retention label governs how long content is kept or when it is deleted. See our guide to retention, archiving and backup.
Do documents automatically inherit their Teams or SharePoint site label?
No. Container labels control the container. File classification or encryption requires the appropriate content-level feature and configuration.
Define the rule before buying
First define exactly what should happen to which content and for whom. Manual classification, encryption, automatic detection and DLP are separate layers. That distinction helps you choose licences without an unnecessary move to the highest tier while still covering the capabilities the pilot actually uses. Base the quote on Microsoft’s current matrix and approved scenarios, not on the controls visible in the portal.








