Microsoft 365 sensitivity labels can classify client and finance files and apply encryption that remains with them after download. A label named “Confidential” provides no access restriction unless its protection settings are configured.
For contracts, payroll records and financial reports, distinguish the classification from the permissions it enforces. Start with a small label scheme, then test what authorised and unauthorised recipients can actually do.
Key takeaways
- File-level labels and container labels control different things; labelling a Team does not automatically encrypt its documents.
- Publishing policies determine who receives labels and whether downgrades require justification.
- Test protected-file behaviour, external sharing, offline access and application support before wider deployment.
What Microsoft 365 sensitivity labels protect
Item-level protection follows the content
Sensitivity labels are stored in file and email metadata. Depending on their configuration and the application, they can classify sensitive data, protect content and add visible markings. Older guidance may use the term Office 365 sensitivity labels.
Microsoft’s sensitivity label guidance explains how labels remain associated with supported content outside Microsoft 365. Downloading a protected document from SharePoint or OneDrive does not, by itself, remove its protection.
A label’s permissions determine who can open a document and which actions they can take. The label name alone doesn’t set those access rules.

Container settings protect the workspace
A container label applies settings to a Team, Microsoft 365 group or SharePoint site. These can govern privacy, external sharing and other supported workspace controls.
It doesn’t automatically apply the same label to every file inside that workspace. Individual documents still need item-level labels when access controls are required.
Remove unnecessary access separately. Our guidance on Microsoft 365 access reviews explains why reviewing access and confirming its removal are separate tasks.
Build a four-tier scheme people can distinguish
Use labels that reflect business handling rules. Employees need to understand the difference without interpreting security terminology each time they save a spreadsheet.
This proposed scheme supports data classification while separating it from the protection decision.
| Label | Suitable information | Protection approach |
|---|---|---|
| Public | Approved published accounts and brochures | Classification only |
| General | Routine internal working documents | Internal handling guidance |
| Confidential | Client contracts and unpublished financial reports | Access limited to approved employees and recipients |
| Highly Confidential | Payroll, bank details and other sensitive data | Access limited to restricted groups, with tighter usage controls |
The important distinction is who may receive the information, rather than how serious the label sounds. Not every client document needs identical permissions.
Record whether external accountants, auditors, solicitors or clients need access. A finance-only restricted-access group can obstruct legitimate external collaboration unless the label design accommodates it.
Labels can support documented handling of personal data, but they don’t by themselves establish compliance with UK GDPR.

Delegate administration and establish licensing
Use label-management permissions rather than broad administration
Global Administrator access isn’t required for routine sensitivity-label management. Microsoft’s information protection setup guidance identifies delegated roles for this work.
The permissions and role distinctions differ between administration and review.
| Role or role group | Appropriate use |
|---|---|
| Information Protection Admin | Administer information protection configuration through delegated roles |
| Sensitivity Label Administrator | Create and manage sensitivity labels |
| Sensitivity Label Reader | Inspect label configuration without changing it |
Global Administrator grants much wider administrative access. Reserve it for tasks that require that access, rather than assigning it to someone who maintains labels.
Separate manual labelling from advanced controls
E3 and Business Premium include manual sensitivity labelling. Automatic labelling requires additional qualifying entitlements, commonly through E5-level information protection capabilities.
Microsoft Information Protection is a framework, not a separate licence to purchase. Third-party applications can integrate classification and protection through the Microsoft Information Protection SDK.
Intune and Microsoft Defender for Cloud Apps, formerly Microsoft Cloud App Security, have their own licensing considerations. Sensitivity-label availability doesn’t establish entitlement to either service.
Build the deployment around licensed capabilities, rather than designing a policy that depends on unavailable controls.
Create and publish labels in Microsoft Purview
Create labels first, then publish them to the people who need them. An unpublished label does not automatically become available throughout Office.
Follow Microsoft’s label creation and publishing process, beginning with a limited pilot group.
- Open the Microsoft Purview portal. Navigate through Solutions, Information Protection and Sensitivity labels, then select Create a label.
- Configure the identity fields. Set the internal name, display name, description for users, description for administrators and label colour. Explain the handling rule in the user description.
- Select the scope. Include files and emails for document protection. Add workspace scope only where the label must also control supported Teams, groups or sites.
- Configure protection. Set who can open files and which actions they can take, then add supported content markings. A header, footer or watermark is a visible content marking, not an access control.
- Publish through a label policy. Select the users or groups, establish label ordering and configure permissions, defaults, mandatory labelling and downgrade justification where appropriate.
A policy can require an explanation when someone removes a label or replaces it with a lower-priority label. That requirement must be configured; it is not an inherent property of every label.
Allow time for policy distribution before checking whether a label is missing. After publication, check supported Office apps to confirm labels appear. Keep the pilot audience narrow enough to investigate problems without disrupting the whole organisation.
Configure encryption around actual working requirements
Decide who assigns permissions
Encryption can use permissions assigned by an administrator or let users assign them themselves. Administrator-defined access is more consistent for restricted finance groups; user-defined access offers flexibility when authorised external recipients change frequently.
Available rights depend on the content and configuration. They can include viewing, editing, printing and copying, while email rights cover replying, replying to all and forwarding.
Apply only the rights required for the workflow. An auditor may need to read financial statements without editing them, whilst the finance team needs to maintain the source workbook.
Set offline access and expiration deliberately
Offline access determines how long protected content remains available without reconnecting for authorisation. Options include always, never or a defined number of days, depending on configuration.
Shorter offline access reduces the time before another authorisation check. It can also interrupt travelling staff or recipients with unreliable connectivity.
Content expiration limits access after a configured date or interval. It isn’t a retention policy and doesn’t delete the file.
Account for protection-owner exceptions. The issuer can retain access beyond restrictions that apply to ordinary recipients, so expiry shouldn’t be described as a universal destruction mechanism.
Introduce automation and advanced encryption selectively
Review automatic labelling before enforcement
Auto-labelling can detect sensitive information types and apply labels when configured conditions match. Detection can misclassify legitimate content or miss sensitive material, so human review remains necessary.
Microsoft’s automatic labelling documentation describes simulation for service-side policies. Use it to review likely matches from automatic labelling (auto-labeling) before enforcement.
Review false positives, missed documents and the effect of DKE protection on collaboration. A detection rule that identifies financial information does not automatically identify the correct recipients.
Reserve Double Key Encryption for defined requirements
Double Key Encryption (DKE) requires two keys together to decrypt protected content. One key remains under the organisation’s control, whilst Microsoft holds the other.
DKE requires additional service configuration and brings application and collaboration constraints. It shouldn’t be the default simply because a document is highly confidential.
Microsoft’s DKE setup guidance also identifies configuration restrictions, including limits on changing a saved DKE label. Establish the business requirement before selecting it.
Test sharing, Copilot and day-to-day access
Test allowed and prohibited behaviour using approved test content. Include internal staff, external recipients, Windows and Mac users, downloaded copies and offline access where those scenarios matter.
Record whether each recipient can open, edit, copy, print and forward the relevant content. A successful label application doesn’t prove that every restriction works as intended.
Label activity reporting can help identify adoption gaps and unexpected changes. Review the findings alongside access reviews rather than treating classification coverage as the only measure.
Copilot requires separate attention. A “Confidential” label doesn’t automatically exclude a file from responses; configured access rules and data loss prevention (DLP) controls determine the restrictions.
Our guidance on Microsoft Purview controls for AI explains the relationship between classification, access and enforced restrictions. Remove broad sharing before expanding AI access to sensitive repositories.
Questions employees commonly ask
Where can you find the sensitivity label in Word?
Look for the Sensitivity control in a supported Word application whilst signed in with the organisation’s account. Its location and presentation vary by application version and platform.
Available labels come from the organisation’s publishing policies. If the expected label is absent, IT should investigate policy assignment, application support and distribution.
Can you use sensitivity labels in OneNote?
OneNote supports sensitivity labels in supported environments after administrator opt-in. Do not assume its capabilities match Word, Excel or Outlook.
Automatic labelling through sensitive information types and DKE are not available in OneNote. Include notebook use in the deployment scope rather than applying document assumptions to it.
Does Microsoft provide a label template?
Eligible new tenants can receive Microsoft’s default labels, including Public, General, Confidential and Highly Confidential. These are starting points, not a guarantee of suitable protection.
Existing tenants may have different configurations. Choose the label whose documented handling rules match the information and intended recipients.
Put the access rules behind the label
A useful label scheme connects classification to tested access rules. Keep labels understandable, delegate administration and establish how protected files behave outside their original location.
Our Microsoft 365 assessment guide describes the permissions, licensing and configuration areas that support this work.
Speak to our team about reviewing your Microsoft 365 environment and configuring practical protection for confidential client and finance files.




