Most labeling projects collapse not in the technical settings but in the fifteen-option menu that appears in front of users in the first week. Users pick at random, “Confidential” documents go out with a “General” label, and DLP rules work with the wrong input. A sensitivity label is written into the metadata of the file and email; it can encrypt the content, stamps a marking on the document and gives DLP a decision input. This guide explains for Microsoft 365 administrators and information security leads how to set up the scheme, which setting addresses which risk, and in what order to turn on automatic labeling.
From the classification scheme to the label structure
Start with an approved classification policy. A labeling project doesn’t replace writing this policy; if there’s no policy, that discussion comes first. A policy usually has four levels: General, Internal, Confidential and Highly Confidential. A mistake we often see is multiplying these levels by department, project or customer name. Users decide in a few seconds while saving a document. A long menu produces guesses.
The real need for distinction usually comes from protection behavior. Some “Confidential” data may be open to all employees, some only to a specific team. In that case, sublabels are defined under the main label. A main label with sublabels can’t be applied directly; the user always picks a sublabel. The scheme below was prepared as an example for a mid-sized manufacturing company.
| Label | Example content | Protection | Marking |
|---|---|---|---|
| General | Catalog, press release | None | None |
| Internal | Procedures, internal announcements | No encryption | Footer |
| Confidential / All Employees | Budget, draft contract | Encryption for internal users | Header and footer |
| Confidential / Specific People | Quotation, customer drawing | The user assigns permissions | Header, watermark |
| Highly Confidential | Merger, prototype data | A fixed group, time-limited access | Watermark |
The order in the list sets the priority: sensitivity increases as you go down. Automatic labeling decides which label to choose by looking at this order; the “require justification when moving to a lower label” setting also reads from here what counts as a downgrade. You can change the order later, but reports and DLP rules will have been written to this order. Set the order right from day one.
Label settings: encryption, marking, scope
Scope
Each label is defined for one or more scopes: files, emails, meetings, groups and sites. The scope names in the portal can change over time; go by the options you see in your own tenant. Keeping file and email labels separate from site labels simplifies management. If you manage both the document and the Teams team with a single label, you lock two separate decision processes together. When you want to change one, the other moves too.
Encryption
Encryption is done with the Azure Rights Management service, and the protection travels with the file. Even if the file is copied to a USB stick, someone without permission can’t open it. There are two basic approaches:
- Assign permissions now: The administrator decides which user, group or domain gets access at which permission level (Co-Owner, Co-Author, Reviewer, Viewer or custom). The content access expiry date and the offline access period are set here.
- Let users assign permissions: In Outlook, the Do Not Forward or Encrypt-Only behavior appears, and in Office apps a window where the user picks people. It suits quotations and project documents whose recipients change every time.
Encryption has an operational cost. For search, eDiscovery and co-authoring on encrypted files, label integration must be on in SharePoint and OneDrive; if it’s off, files silently drop out of search results. Plan the Rights Management super user feature with a controlled account to recover content when the label owner has left or permissions were granted incorrectly. Try in a pilot whether mobile and third-party apps can open encrypted content. On the device, not on paper.
# Label integration for Office files in SharePoint and OneDrive
Connect-SPOService -Url https://contoso-admin.sharepoint.com
Set-SPOTenant -EnableAIPIntegration $true
# Checking labels and their order (Security & Compliance PowerShell)
Connect-IPPSSession
Get-Label | Format-Table DisplayName, Priority, ContentType -AutoSize
Get-LabelPolicy | Format-Table Name, Labels -AutoSize
The first place to look in the console is the Priority column in the Get-Label output. If the order you see in the portal doesn’t match the priority here, automatic labeling stamps a label you didn’t expect.
Content marking
Headers, footers and watermarks are the visible face of the label; they raise awareness in printed content or screenshots. With dynamic variables (${Item.Label}, ${User.Name}, ${Event.DateTime}), the label name, the user who labeled the document and the date are written into the marking. The marking text should match the label name. If a document labeled “Confidential” says “For Official Use” at the bottom, an auditor will note it as an inconsistency.
Default and mandatory labeling
Labels are published to users or groups through label policies. Policy settings directly determine adoption:
- Default label for documents: Assigned to new and unlabeled documents. In most organizations, “Internal” is the default. If “Confidential” is made the default, external sharing constantly gets stuck and users make downgrading the label a reflex.
- Default label for emails: Can be set separately from documents. In teams with heavy external correspondence, giving email an encrypting default label causes delivery and reading problems.
- Mandatory labeling: The user can’t save or send without choosing a label. When turned on together with a default label, users often never see the mandatory warning; observe the combined behavior of the two settings in your own Office versions in a pilot.
- Downgrade justification: When a label is removed or changed to a lower label, the user is asked for a justification; the justification is written to the audit log.
Create a separate policy for the pilot group and give it higher priority. New labels and default changes are then tested without spreading across the whole tenant. A rollout without a pilot is a rollout that’s hard to undo.
Client-side and service-side automatic labeling
Some data types aren’t left to the user’s choice: national ID numbers, IBANs, card numbers, health data. Large piles of legacy content aren’t labeled by hand either. In these two cases, automatic labeling is needed, and two mechanisms complement each other.
| Feature | Client-side | Service-side |
|---|---|---|
| Where it runs | Office apps, Outlook | Exchange transport, SharePoint, OneDrive |
| Behavior | Recommend or apply automatically | Apply automatically |
| User interaction | Can reject the recommendation | None |
| Legacy content | Only the document being opened | Files at rest (existing) too |
| Test | Pilot policy | Simulation mode |
Start with the “recommend” behavior on the client side: when a user types a national ID number into a document, Office suggests the “Confidential” label with a tip. How often the recommendation is rejected shows the rule’s quality; a recommendation that’s constantly rejected is a badly written condition. Run service-side policies in simulation mode first. Which files and messages would be labeled is reported, samples are reviewed one by one, and only then is the policy turned on. Service-side labeling doesn’t change a label the user applied manually. This is deliberate design.
When writing conditions, don’t stamp a label on a single match; use confidence level and instance count thresholds. An order list containing a single 11-digit number isn’t “Confidential”. A staff listing containing dozens of validated national ID numbers is “Confidential”. Sensitive information types and custom patterns are set up with the same logic as DLP policies; details are in the Purview DLP policy design guide. If you know in advance how much sensitive data is on which file server, you set the thresholds by measurement, not guesswork; for that, follow the steps for sensitive data discovery on file servers.
Site and group labels
Labels scoped to groups and sites carry container-level Microsoft 365 security settings for Microsoft 365 groups, Teams teams and SharePoint sites: privacy (public or private), whether guest members can be added, the site’s external sharing level and limiting access from unmanaged devices. For these labels to appear in the portal, label support must be turned on in the Entra ID directory settings and the labels must be synchronized. Without synchronization, the label option doesn’t appear; that’s a common cause of support tickets.
# After group label support has been enabled in Entra ID
Connect-IPPSSession
Execute-AzureAdLabelSync
A site label doesn’t label the files in the site; it only manages the container’s behavior. Say this clearly in user training. If you don’t, everyone assumes the files in a Teams team labeled “Highly Confidential” are protected too. An assumption isn’t protection. How external sharing is narrowed at the site level is explained in the SharePoint and OneDrive external sharing security article.
Adoption and common mistakes
Like most enterprise cybersecurity work, a labeling project depends less on settings than on users choosing the right label. The problems we run into again and again in the field, and their remedies:
| Problem | Symptom | Fix |
|---|---|---|
| Too many labels | Random selection | 4–5 main labels, limited sublabels |
| Vague names | “Sensitive” and “Confidential” get mixed up | Write example content in the label description |
| Encrypting too early | External recipients can’t open it | Marking first, then encryption |
| A high default | Mass label downgrades | Keep the default at “Internal” |
| Unmeasured usage | Unlabeled content piles up | Monthly tracking with Activity explorer |
Roll out in phases. First labels without encryption and marking; then user-controlled encryption such as “Confidential / Specific People”; last, the fixed-permission “Highly Confidential” label and service-side automatic labeling. At each stage, monitor label apply, change and downgrade events with Activity explorer in Purview, and where labeled content sits with Content explorer. If the same sentence keeps recurring in downgrade justifications, the label definition conflicts with the workflow. Fix the definition, not the user.
The label scheme should also match the information asset inventory; how asset owners and classification levels are recorded is in the preparing an information asset inventory guide. For the current list of features, rely on Microsoft’s sensitivity labels documentation; portal behavior can change between versions.
Implementation checklist
- The classification policy is approved; label names match the policy exactly.
- Label order goes from low to high; sublabels only where needed.
- SharePoint and OneDrive label integration is on; search and co-authoring on encrypted files have been tested.
- The super user and recovery process is written down.
- The pilot label policy is separate and has higher priority.
- Service-side policies have been reviewed in simulation, and sample files verified.
- Sharing encrypted content with external partners has been tested with at least two different organizations.
Teams that want to set up labeling together with DLP and external sharing controls can find the scope on the data loss prevention and DLP service page.
Frequently asked questions
Is a Microsoft 365 E5 license required for sensitivity labels?
Manual labeling and label-based encryption are available across a wider range of licenses. Automatic labeling, service-side policies and some advanced features, however, usually require an E5 or E5 Compliance license. Because the coverage changes from time to time, check the Microsoft 365 security and compliance licensing guidance at the start of the project.
Can an external partner open a file with an encrypted label applied?
They can, but they need to be able to authenticate: an Entra ID account, a Microsoft account, or a guest identity defined in your tenant. A user not in the list of people or domains authorized in the label can’t open the file. For outbound content, granting permission by domain is more sustainable than adding users one by one.
Does a site label also label the files in the site?
No. A label scoped to groups and sites manages the container’s privacy, external sharing and unmanaged device access settings; it doesn’t stamp a label on the files inside. For files, assign a default label to the document library or use an automatic labeling policy.
How many labels is it right to start with?
Four or five main labels are enough. If a distinction is needed, use sublabels at the most sensitive levels; multiplying sublabels by department or project name increases selection errors.