★ First page of Microsoft's 100,000-partner directory, sorted by responsiveness✓ Microsoft Solutions Partner — Security, Modern Work, Infrastructure, App Innovation, Data & AI● Microsoft partner since 2006◆ 1,100+ organizations under management

Sensitivity Labels in Word and Excel: Set Up, Apply, and Enforce

Can Word and Excel protect a sensitive file on their own? Yes, once Microsoft Purview sensitivity labels are published to the user: the Sensitivity button on the Home tab classifies the file, and the label can add a header, a watermark or encryption that travels with the document. This guide gives the setup in the Purview portal, the user steps in the apps, the policy settings that make labeling stick, and which Microsoft 365 plan covers manual labeling versus automatic labeling.

The short answer: labels are built into Word and Excel, but someone has to publish them

Word, Excel, PowerPoint and Outlook in Microsoft 365 Apps carry sensitivity labeling as a built-in feature. The Azure Information Protection add-in that older guides describe was retired on April 11, 2024, and Microsoft disabled it in Office between May and December 2024, so a tenant still relying on it has users with no labels at all.

What the user sees depends on three things:

  • A label exists in Microsoft Purview and is published to that user through a label policy. No policy, no Sensitivity button.
  • The user is signed in with a work or school account; a personal Microsoft account shows nothing.
  • The app build supports the feature in use. Manual labeling has been available for years; some policy settings need a newer build (details below).

Licensing follows one split. Manual labeling, where a person picks the label, is covered by Microsoft 365 Business Premium ($22.00 per user per month on an annual term, Microsoft list price, October 2026 price list), Microsoft 365 E3 ($39.00) and Microsoft 365 E5 ($60.00). Automatic labeling, where Purview applies or recommends a label because the content matches a pattern, needs Microsoft 365 E5 or the Microsoft 365 E5 Information Protection and Governance add-on ($7.00).

What a label can do to a Word or Excel file

A sensitivity label is a piece of metadata stored in the file. On its own it classifies. Each label can also carry settings that act on the file:

Label setting What happens in Word or Excel What the recipient sees
Classification only The label name shows in the title bar and in the file's properties Nothing changes; the file opens anywhere
Content marking Purview inserts the header, footer or watermark text you define The marking prints and travels with every copy
Encryption with assigned permissions The file is encrypted; only the people or groups you listed can open it, with the rights you chose (view, edit, print, copy) Someone outside the list signs in and is denied

Markings are cheap and visible. Encryption is the setting that breaks workflows when it is wrong, usually a vendor who cannot open a quote; encrypt only the labels whose files must not leave a named group, and keep that group small.

Labels sit in an ordered list in Purview, and a label further down the list counts as more sensitive; that order decides what a downgrade is, which is what the justification prompt keys on. The same taxonomy feeds the data loss prevention policies in Purview DLP for a 50-user firm.

Step 1: design four labels before you open the portal

Most label projects fail at the taxonomy, not the technology. Rules that hold up:

  1. Four labels, named for the business: Public, General, Confidential, Highly Confidential. Six or more and users stop reading the menu.
  2. Give each label one sentence a receptionist would understand.
  3. Decide the settings per label: Public and General carry nothing; Confidential adds a footer marking; Highly Confidential adds a watermark and, if needed, encryption limited to a named group such as Finance or Leadership.
  4. Use sublabels only when a parent needs two behaviors (Confidential for all employees versus Confidential for leadership only); they appear as a submenu in Word and Excel.
  5. Write down who owns the taxonomy; labels are hard to retire once documents carry them.

The default label is the one decision users never make, so choose it deliberately. General is the usual choice: it marks everything as internal without encrypting anything.

Step 2: create the labels in Microsoft Purview

The work happens in the Microsoft Purview portal, not in the Microsoft 365 admin center.

  1. Sign in with a Compliance Administrator or Information Protection Admin role. Go to Solutions, then Information Protection, then Sensitivity labels.
  2. Select Create a label. Enter the name, the display name and the one-sentence description for users.
  3. Choose the scope: Files & other data assets and Emails. Leave Meetings off unless you run Teams Premium. Groups & sites is the container scope; add it on a second pass, since it needs a separate setting in Microsoft Entra ID.
  4. On the protection settings page, turn on Apply content marking for Confidential and Highly Confidential and type the text. Turn on Apply or remove encryption only for the labels you decided to encrypt, assign the group and the rights, and set offline access and expiry.
  5. Skip the Auto-labeling for files and emails page unless the tenant has E5 or the E5 Information Protection and Governance add-on; without the license the setting cannot be used.
  6. Review and create. Repeat for each label, then arrange the list with Public at the start and Highly Confidential at the end.

Creating a label publishes nothing. Until a label policy includes the user, Word and Excel show no Sensitivity button.

Step 3: publish with a label policy and set the rules users feel

Still in Information Protection, open Label policies and select Publish labels.

  1. Choose the labels. Publish all four to everyone; keep a separate policy with the encrypted sublabels for the groups that need them.
  2. Assign the policy to a pilot group of 5 to 10 people from the departments that handle the most sensitive files.
  3. The policy settings decide behavior:
    • Apply this label by default to documents and, separately, to emails. Set General.
    • Users must provide a justification to remove a label or lower its classification. Turn this on from day one; it writes the reason to the audit log.
    • Require users to apply a label to their documents and emails. This is mandatory labeling: off for the pilot month, then on, after which an unlabeled save or send prompts for a label and cannot be skipped.
    • Provide users with a link to a custom help page: a one-page intranet article with the four labels and their sentences.
  4. Name the policy, review, and submit.

Minimum app builds matter here. Microsoft's version table lists a default label for new documents from Current Channel 1910 on Windows, and a default label applied to existing unlabeled documents from Current Channel 2208 on Windows and 16.63 on Mac. Semi-Annual Enterprise Channel receives label features later, so check the channel first.

Step 4: enable labels for files in SharePoint and OneDrive

One tenant-level switch controls whether SharePoint and OneDrive understand labels on Office files. Without it, Office for the web shows no labels and the services cannot read encrypted files, so co-authoring, search, eDiscovery and data loss prevention do not work on them.

In the SharePoint Online Management Shell, check the state:

(Get-SPOTenant).EnableAIPIntegration

If it returns False, turn it on:

Set-SPOTenant -EnableAIPIntegration $true

It covers new and changed files encrypted with a cloud key, not Double Key Encryption. Container labels for Teams and SharePoint sites use a different setting (the EnableMIPLabels group setting in Entra ID), so this switch does not light them up.

How users apply a label in Word, Excel and Outlook

The user steps are the same on Windows, Mac and the web:

  1. In Word or Excel, open the file, select the Home tab and select Sensitivity. Pick the label. The label name appears in the title bar and under File, then Info.
  2. To change a label, select Sensitivity again and choose another. If the new label is lower in sensitivity and the policy requires justification, a dialog asks for the reason before the change is saved.
  3. To remove a label, open the Sensitivity menu and clear the selection. When the policy requires a label, the remove option is not available.
  4. In Outlook, while composing, select Sensitivity on the Message tab.
  5. When mandatory labeling is on, saving an unlabeled file or sending an unlabeled email shows a prompt to choose a label; the user cannot proceed without one.

Licensing: what Business Premium covers and when you need the E5 add-on

Microsoft enforces the split. Since January 2024 new customers have needed the right license to use sensitivity labels, and existing customers had a grace period that ended in early April 2024.

Capability Business Premium ($22.00) Microsoft 365 E3 ($39.00) Microsoft 365 E5 ($60.00) E5 Information Protection and Governance add-on ($7.00)
Manual labeling in Word, Excel, PowerPoint, Outlook Included Included Included Not needed
Content marking and encryption on a manual label Included Included Included Not needed
Default label, mandatory labeling, justification Included Included Included Not needed
Client-side automatic or recommended labeling No No Included Adds it to E3 or Business Premium
Service-side auto-labeling for SharePoint, OneDrive and Exchange No No Included Adds it

Prices are Microsoft list prices per user per month on an annual term, October 2026 price list. Microsoft 365 F1 and F3 are on Microsoft's manual labeling list as well.

The decision rule: buy the add-on for the people whose files Purview should label without asking, usually finance, HR and anyone handling client identifiers. Everyone else labels by hand.

A 60-day rollout for a 50-user firm

Days Work Setting state
1 to 7 Agree the four labels; create them in Purview; enable the SharePoint and OneDrive switch Nothing published
8 to 14 Publish to the pilot group with General as default and justification on Mandatory off
15 to 30 Fix names from pilot feedback; write the help page; check update channels Mandatory off
31 to 45 Publish to all 50 users; ten-minute training per department Mandatory off
46 to 60 Turn on mandatory labeling; add the encrypted sublabel for Finance or Leadership Mandatory on
After day 60 Review label usage; add container labels; decide on the E5 add-on Steady state

The milestones are ours; the settings behind them are Microsoft's.

Frequently asked questions

Do I need Microsoft 365 E5 to use sensitivity labels in Word and Excel?

No. Manual labeling, including content marking and encryption, is covered by Microsoft 365 Business Premium, E3, E5, F1 and F3. E5 or the E5 Information Protection and Governance add-on ($7.00 per user per month on an annual term, Microsoft list price, October 2026 price list) is needed only for automatic and recommended labeling.

Why do my users not see the Sensitivity button?

In almost every case the user is not in a published label policy, is signed in with a personal account, or the app is on a build below the minimum for that feature. Check the policy scope first, then the account, then the Office update channel.

Can a label encrypt an Excel file so only my team can open it?

Yes. A label with encryption and assigned permissions limits opening to the users or groups you name, with the rights you set. The file stays encrypted when it is emailed, copied or downloaded.

Does the Azure Information Protection add-in still work in Office?

No. Microsoft retired the add-in on April 11, 2024 and disabled it in Office between May and December 2024. Built-in labeling in Microsoft 365 Apps replaces it; the Purview Information Protection client 3.0 keeps the scanner, viewer and file labeler but no Office add-in.

Does labeling a Team or SharePoint site label the files inside it?

No. A container label controls the site's privacy, external sharing and unmanaged-device access; the files keep their own labels. Container labels also need the separate Entra ID group setting, not the SharePoint file switch.

Sources

Key takeaways

  • Sensitivity labeling is built into Word, Excel, PowerPoint and Outlook; the Azure Information Protection add-in was retired on April 11, 2024.
  • Users see the Sensitivity button only when a Purview label policy includes them and they are signed in with a work account.
  • Manual labeling with markings and encryption is covered by Business Premium ($22.00), E3 ($39.00) and E5 ($60.00); automatic labeling needs E5 or the $7.00 E5 Information Protection and Governance add-on.
  • Four labels, a General default and justification on downgrade cover most organizations; mandatory labeling comes after a pilot month.
  • Enable the SharePoint and OneDrive integration with Set-SPOTenant -EnableAIPIntegration $true, or co-authoring, search and DLP skip encrypted files.
  • Container labels for Teams and sites are a separate setting and do not label the files inside.

Want the labels designed, published and enforced without the pilot-month mistakes? Our Azure Information Protection Implementation service builds the taxonomy, the Purview labels and policies, the SharePoint integration and the user training as one fixed-price project, quoted in writing before work begins; the Microsoft 365 licenses stay on your own invoice at Microsoft's list price.

Didn’t find your question?

Ask it here. A real engineer answers by email within one business day — and if it’s a good one, it becomes part of this page so the next person finds it.

Answered by a person, one time, to your inbox. Nothing you type here is published without a human reviewing and anonymizing it first.

Questions this article didn’t answer?

Thirty minutes with Mike — our CEO, not a sales rep. Bring the hard version of the question.