Get started now

Microsoft 365 Sensitivity Labels: How to Set Them Up

Sensitivity labels are the classification and protection layer of Microsoft Purview Information Protection. You define a small set of labels such as Public, General and Confidential, and each label can encrypt content, mark it with a header, footer or watermark, and set the privacy and sharing rules of a Teams team or SharePoint site. The label is stored as metadata and follows the file wherever it goes.

Quick answer: In the Microsoft Purview portal, go to Solutions > Information Protection > Sensitivity labels, select + Create a label, name it, choose its scope and protection settings, then go to Publishing policies > Label policies and select Publish label to make it available to users. Allow up to 24 hours for it to replicate (Microsoft Learn).

Getting labels right matters more now that generative AI is part of daily work. In Microsoft’s 2026 Data Security Index, based on responses from more than 1,700 security leaders, 32% of surveyed organizations’ data security incidents involve the use of generative AI tools (Microsoft Security Blog, January 2026). Labels are one of the controls that let you decide, per item and per workspace, what can be shared and with whom.

What are sensitivity labels in Microsoft 365?

Sensitivity labels are part of Microsoft Purview Information Protection, formerly known as Azure Information Protection and Microsoft Information Protection. You manage them in the Microsoft Purview portal. The older Microsoft Purview compliance portal and the Security & Compliance Center are retired, so instructions that start there are out of date (Microsoft Learn).

A label has three properties worth knowing:

  • Customizable: you decide the names and how many levels you need. New customers get a default set: Personal, Public, General, Confidential and Highly Confidential, with sublabels such as All Employees and Specific People (Microsoft Learn).
  • Clear text: the label is stored as metadata in the file or email, so other apps and services can read it and act on it.
  • Persistent: the label and its protection settings stay with the content wherever it is stored or sent. Guests who sign in from other tenants do not see your labels.

Users see labels in Office apps, which have built-in labeling. The old Azure Information Protection unified labeling client and Office add-in are retired and replaced by the Microsoft Purview Information Protection client, which is Windows only.

What can a sensitivity label do?

Depending on its scope, a label can do the following (Microsoft Learn).

  • Encrypt content with usage rights. You choose who can view, edit, copy or print, whether access expires, and whether offline access is allowed.
  • Mark content. Add a header, footer or watermark. Watermarks are not applied to emails. Text limits apply: 255 characters for a watermark and 1,024 for a header or footer (255 in total in Excel) (Microsoft Learn).
  • Label automatically or recommend a label. Apply or recommend a label when content matches sensitive information types or trainable classifiers. Email can also inherit the highest-priority label from its attachments, through a label policy setting.
  • Protect meetings. Meeting labels can control lobby bypass, who can present, recording and transcription, end-to-end encryption, a watermark and copying of chat. Some settings require Teams Premium (Microsoft Learn).
  • Protect containers. Apply settings to Teams teams, Microsoft 365 groups and SharePoint sites (covered below). This also applies to Viva Engage communities and Loop workspaces.

Labels have a scope: Files and other data assets, Emails, Meetings (which needs Files and Emails), and Groups & sites. The last scope only appears after you enable container labels.

Sensitivity labels vs retention labels vs data classification

These three terms are often mixed up, but they do different jobs.

Sensitivity labelsRetention labelsData classification
Question it answersHow sensitive is this, and who may access it?How long do we keep it?What does this content contain?
What it doesEncrypts, marks, and sets container rulesRetains or deletes contentDetects content with sensitive information types and trainable classifiers
Where you see itTag in Office apps, Teams and SharePointLabel on the itemFeeds auto-labeling, DLP and reports

They work together. Classification finds the credit card numbers, a sensitivity label protects the file that holds them, and a retention label controls how long it lives. An item can have both a sensitivity label and a retention label at the same time.

Classic Microsoft Entra group classification, formerly Azure AD group classification, is different again: it is a plain text string on a group with no enforcement attached. Once container labels are enabled, classic classifications no longer apply to new groups. Microsoft documents the migration to sensitivity labels.

Which license do you need?

Licensing is where many rollouts stall, so check it before you design the label set (Microsoft Purview service description).

CapabilityMicrosoft 365 E3 / Business PremiumMicrosoft 365 E5 tier
Manual labeling by usersYesYes
Automatic labeling (client-side and service-side)NoYes
Meeting labelsNoYes
Default label for a SharePoint document libraryNoYes
Container labels (Teams, groups, sites)Requires Microsoft Entra ID P1 to enableRequires Microsoft Entra ID P1 to enable

“E5 tier” means Microsoft 365 E5, or the E5 Compliance / Information Protection and Governance add-on, or Office 365 E5 for the auto-labeling case. Manual labeling is also available with Office 365 E3/E5, A3/A5, G3/G5, F1/F3 and EMS E3/E5, among others. Confirm your exact SKU in the service description before you promise auto-labeling to stakeholders.

How to create and publish sensitivity labels in Microsoft Purview

You need an Information Protection role group (Admins, Analysts, Investigators or Readers) or the Sensitivity Label Administrator role. The Compliance Administrator role also works (Microsoft Learn).

  1. Open the Microsoft Purview portal and go to Solutions > Information Protection > Sensitivity labels.
  2. Select + Create a label. (Tenants on the modern label scheme see + Create > Label or Label group instead.)
  3. Enter a name, a display name and a description. The description is the tooltip users see, so write it for them. Pick a label color.
  4. Under Define the scope for this label, choose Files and other data assets, Emails, Meetings and, if enabled, Groups & sites.
  5. Configure the protection settings for each scope: encryption, content marking, auto-labeling, and container settings.
  6. Review and create the label. It does nothing for users until you publish it.
  7. Go to Solutions > Information Protection > Publishing policies > Label policies and select Publish label. Choose the labels, the users or groups, and the policy settings.
  8. Wait. Labels and policies can take up to 24 hours to replicate to users and services (Microsoft Learn).

The label policy is where behavior is decided:

  • Default label: applied automatically to new content. You can set separate defaults for documents, emails, meetings, new containers and Power BI.
  • Mandatory labeling: users must choose a label before they save or send.
  • Justification: require users to explain why they remove or downgrade a label.
  • Help link: point users to your internal guidance.

Label order sets priority: keep the least restrictive label at the top and the most restrictive at the bottom. Priority drives the downgrade justification prompt and the “highest priority” logic when labels are inherited. Note that sublabels do not inherit settings from their parent, except color.

New tenants from 1 October 2025 use the modern label scheme, where a parent label becomes a “label group” with only a name, description, color and priority. Migrating an existing tenant to it is irreversible, so plan it (Microsoft Learn).

How to apply sensitivity labels to Teams, groups and SharePoint sites

Labels on containers control the workspace itself, not the files in it. You must enable them once (Microsoft Learn).

  1. In the Microsoft Entra directory settings, set EnableMIPLabels to True using Microsoft Graph PowerShell. This needs Microsoft Entra ID P1 (Microsoft Entra ID is the new name of Azure AD) (Microsoft Learn).
  2. In Security & Compliance PowerShell, run Execute-AzureAdLabelSync.
  3. The Groups & sites scope now appears when you create or edit a label.

A container label can control:

  • Privacy (public or private)
  • External user access (guests)
  • External sharing from SharePoint sites
  • Access from unmanaged devices (requires Conditional Access)
  • Authentication context
  • Discoverability of private teams
  • Shared channel controls: internal only, same label only, or private teams only
  • The default label for channel meetings

Four behaviors surprise admins:

  • Shared channels inherit the parent team’s label, and it cannot be removed or changed. See our guide to Teams shared channels.
  • Files do not inherit the container label. If someone uploads a document with a higher-priority label to a site with a lower label, it is not blocked. Purview logs a “Detected document sensitivity mismatch” audit event and sends an email.
  • Changes are not retroactive. Editing a label’s group and site settings is not pushed to groups that already carry the label.
  • Guests need to be planned for. Combine container labels with clear external sharing rules. Our guide on collaborating with people outside your organization covers the Teams side.

Turn on labels for SharePoint and OneDrive files

Container labels do not label files. To use labels on files in SharePoint and OneDrive, enable the integration once per tenant (Microsoft Learn).

  • Select Turn on now on the Sensitivity labels page (Information Protection), or run Set-SPOTenant -EnableAIPIntegration $true. This enables labels in Office for the web, co-authoring, search, eDiscovery and DLP on encrypted files, and auto-labeling at rest.
  • For PDFs, run Set-SPOTenant -EnableSensitivityLabelforPDF $true.
  • Co-authoring on encrypted files is a separate opt-in under Settings > Solution settings > Information Protection > Co-authoring for files with sensitivity labels. It changes how label metadata is stored and cannot be turned off in the portal (Microsoft Learn).
  • A default sensitivity label for a document library needs an E5-tier license (Microsoft Learn).

Sensitivity labels and Microsoft 365 Copilot

Copilot and agents recognize sensitivity labels, and Copilot Chat responses show the highest-priority label among the sources used (Microsoft Learn). A label on its own does not hide a file from Copilot, though. Two mechanisms do the enforcing:

  • Encryption usage rights. For encrypted content, Copilot returns data only if the user has the VIEW and EXTRACT usage rights. New content created with Copilot in Word, PowerPoint and Outlook inherits the source label, and the highest priority wins (Microsoft Learn).
  • DLP. A DLP policy with the “Microsoft 365 Copilot and Copilot Chat” location can use the condition Content contains > Sensitivity labels to prevent Copilot from processing labeled content (Microsoft Learn).

For a walkthrough of referencing protected files safely, see Microsoft 365 Copilot with sensitivity labels. For DLP setup, see our Teams DLP guide.

Best practices for sensitivity labels

Keep the taxonomy small. Microsoft states that effectiveness is noticeably reduced when users have more than five main labels or more than five sublabels per main label (Microsoft Learn). Tony Redmond, writing on Practical365, puts the reason plainly:

“Users will do the right thing to protect sensitive information if they are guided by good names, descriptions, and limited choices.” (Tony Redmond, Practical365)

Then follow this order of work:

  • Start with classification, then add encryption. Begin with labels that mark and classify, and introduce encryption once people understand the taxonomy. Do not use an encrypting label as the default for documents.
  • Pair mandatory labeling with a default label. Microsoft warns that unless you also set a corresponding default label, mandatory labeling can frustrate users with frequent prompts.
  • Pilot first. Publish to a small group before the whole tenant, and collect feedback on names and tooltips.
  • Use simulation mode for auto-labeling. Service-side auto-labeling policies (Information Protection > Policies > Auto-labeling policies) run in simulation mode first and cover SharePoint, OneDrive and Exchange. Review the matches before enforcing (Microsoft Learn).
  • Use few label policies. Microsoft’s aim is as few as possible, and one policy for the whole organization is not uncommon.
  • Monitor. Use Activity explorer and the Information Protection reports in the Purview portal to see how labels are used, and review audit events for label changes.

Labels are one part of a wider governance model. Our Teams governance best practices put them in context.

Apply container labels consistently with workspace templates

Container labels only help if every team and site actually gets one. nBold workspace templates can carry the Microsoft Purview sensitivity label and the privacy setting you define, so every team and SharePoint site created from a template inherits them. Your security team still defines and publishes the labels in Purview; nBold applies them when each workspace is provisioned, so classification never depends on who clicked “create”.

FAQs

What are sensitivity labels in Microsoft 365?

Sensitivity labels are part of Microsoft Purview Information Protection. They classify content (files, emails, meetings, and containers such as Teams, Microsoft 365 groups and SharePoint sites) by how sensitive it is, and can enforce protection such as encryption, content marking (header, footer, watermark) and container settings like privacy and guest access. The label is stored as clear-text metadata, so it travels with the file.

What is the difference between sensitivity labels, retention labels and data classification?

Sensitivity labels protect content and control who can access it. Retention labels decide how long content is kept or deleted. Data classification is the detection layer: sensitive information types and trainable classifiers that identify what your content contains, which can then trigger automatic or recommended sensitivity labels. An item can carry both a sensitivity label and a retention label.

Do I need Microsoft 365 E5 for sensitivity labels?

Not for manual labeling. Microsoft 365 E3, E5 and Business Premium (among others) support labels that users apply themselves. Automatic labeling (client-side and service-side), meeting labels and a default label for a SharePoint document library need an E5-tier license, such as Microsoft 365 E5 or the E5 Compliance / Information Protection and Governance add-on. Container labels also need Microsoft Entra ID P1 to enable.

How do I apply a sensitivity label to a Teams team or SharePoint site?

First enable container labels: set EnableMIPLabels to True in the Microsoft Entra directory settings with Microsoft Graph PowerShell, then run Execute-AzureAdLabelSync in Security & Compliance PowerShell. The Groups & sites scope then appears when you create a label. Publish the label, and users can pick it when they create a team, group or site. Files inside do not inherit the container label.

Do sensitivity labels stop Microsoft 365 Copilot from reading a file?

Not by themselves. Copilot recognizes labels, but for encrypted content it returns data only if the user has the VIEW and EXTRACT usage rights. To block Copilot from processing labeled content, use a data loss prevention (DLP) policy with the Microsoft 365 Copilot and Copilot Chat location and the condition Content contains > Sensitivity labels.