Sensitivity labels and Microsoft 365 Copilot

How Copilot takes Microsoft Purview sensitivity labels into account, when new content inherits a label, and what happens to unlabeled files.

Topic
AI
Author
ARLITECH expert team
Published

Microsoft 365 Copilot reads with the permissions of the signed-in user. Who can access a SharePoint site or a Teams team is decided by the sharing settings; how to put those in order and how to schedule the Copilot rollout is covered in the article Copilot and overly broad sharing. This article goes through Microsoft Purview sensitivity labels, which mark the document or email itself and which Copilot also takes into account.

What a label changes in how Copilot behaves depends on the label's settings, and on whether the documents have been labeled at all.

What a sensitivity label marks

A sensitivity label records how confidential a piece of content is. Behind it is a classification decision: someone has decided which levels the organization uses and where each piece of data belongs. The article on data classification covers this in detail; the label is the machine-readable trace of that decision.

Technically, the label goes into the metadata of the file or email, so it stays with the content when the document is downloaded, forwarded by email, or copied to another site. A label can have several effects:

  • a visible marking on the document: header, footer, or watermark,
  • encryption, which determines who can open the content and what they can do with it,
  • a condition for other rules, for example a DLP rule can block external sending based on the label.

Labels have a priority order, which the administrator sets: the most sensitive label gets the highest priority. Changing a label counts as a downgrade when the new label has a lower priority, and label inheritance for content Copilot creates is also built on this order.

The container label has a similar name but a different job. It is applied to a Teams team, a Microsoft 365 group, or a SharePoint site and controls the container's settings: whether it is private, whether guests are allowed, whether external sharing is permitted, and whether the content can be opened from an unmanaged device. It does not label the files in the container one by one. A retention label serves a different purpose altogether: it controls how long content must be kept or when it must be deleted.

Labels and encryption: usage rights

If a label does not encrypt and no DLP rule refers to it, it is only an indicator: it does not narrow access, and the authorized user and Copilot read the file the same way they would without a label.

An encrypting label protects the content with the Azure Rights Management service. In the label's settings you can specify which users or groups get which usage rights. The most common rights:

Commonly used usage rights for an encrypting label
Usage rightWhat it allows
VIEW (view)Opening and reading the document
EDIT (edit)Changing the content and saving it to the same file
PRINT (print)Printing the document
EXTRACT (copy content)Copying text or images out of the document
EXPORT (save as)Saving to another format or to an unprotected copy
OWNER (owner)All rights, including changing or removing the protection

Permissions can be assigned in two ways. The administrator assigns them in advance in the label, for example “all members of the organization can view and edit”. Alternatively, the user specifies who gets what when applying the label. The first is more predictable; the second is more flexible, but it is harder to keep track of who got what.

SharePoint and OneDrive can only process the content of encrypted Office files, for example for search and co-authoring, once support for sensitivity labels in these services has been turned on in the tenant. Without it, the content of encrypted files stays closed to the service.

What Copilot sees in a labeled document

Copilot handles labeled content with the user's rights. What follows from this depends on the label's settings:

  • If the label does not encrypt and no DLP rule for Copilot refers to it, Copilot uses the document according to the user's access.
  • For an encrypted document, Copilot can work with the content only if the user has the EXTRACT right in addition to VIEW. A user with view rights only can open the document, but Copilot will not summarize or quote it for them.
  • Copilot cannot reach content protected with Double Key Encryption, because one of the keys stays in the organization's own system.
  • If a response relies on a labeled source, Copilot shows the label on the referenced item, and in chat it shows, next to the response, the highest-priority label among the referenced sources. This way the user can see how sensitive the source material was before forwarding the response.

It follows that two users can get different answers to the same question. From a management report protected by an encrypting label, a summary goes to the users whose label grants the copy right. For the others, Copilot does not work with it, even if the site where it is stored is shared too broadly. For a user who lacks even the view right, the file does not appear in Copilot at all. An encrypting label therefore also protects against faulty sharing, provided its permissions are narrower than the sharing, for example when they are granted to named groups. An encrypting label that gives every member of the organization view and copy rights does not protect against overly broad internal sharing. In neither case does it replace putting permissions in order.

A DLP rule that can be set for Microsoft 365 Copilot as a location works without encryption: it can exclude content with the specified label from response summaries, even for an authorized user. It is an option where encryption would get in the way of collaboration but Copilot still has to be kept away from the content. The file may still show up as a reference, and the rule's scope differs from one Copilot experience to another, so check the current Purview documentation before enforcement.

Label inheritance in content Copilot creates

Copilot often builds something new from existing documents: a Word summary from three reports, a PowerPoint deck from a proposal. If the sources had labels, the new content cannot stay unlabeled either, or an extract of highly confidential material would travel on without protection.

In the supported scenarios, the new content therefore inherits the highest-priority label among the source files. If the new document already carries a higher-priority label, that label stays. With an encrypting label, the protection usually carries over together with the label, but the Purview documentation also lists exceptions, for example labels that encrypt with user-defined permissions. With such sources, do not assume the new document gets the same protection.

Because inheritance follows the priority order, a badly set order means Copilot passes on the wrong label. The range of supported scenarios differs by app, and Microsoft keeps extending it, so before the rollout it is worth testing in the apps you use what label a new document gets from sources with different labels.

The inherited label is not final: if it is too strict or too loose, the document's author can replace it. If the label policy requires a justification for a downgrade, the reason for the change can be traced later.

Unlabeled content: default and automatic labeling

Copilot applies no label-based restriction to a file without a label: only the sharing permissions count. Where the labels arrived later than the documents, the existing files stay unlabeled, and the effect of the labels depends on how many of them get a label afterwards. Several tools do this, with different scopes:

Default label in the label policy

A label policy can specify a default label for documents and emails. The Office apps apply it to new content and to unlabeled content that is opened and edited. Old files that are never opened are not affected. Mandatory labeling can be added: the user cannot save the document or send the email without a label.

Default label for a document library

A SharePoint document library can be given its own default label. New and edited files get it; files already in the library that stay unchanged do not. In sensitive locations, for example the HR or legal document library, this is the simplest way to make sure newly created content does not stay unlabeled.

Automatic labeling in the apps

Client-side automatic labeling watches the content during editing. If it finds a sensitive information type, for example a bank account number or an identity document number, it either recommends the label or applies it itself, depending on the setting. The user can reject a recommendation; automatic application does not need the user's decision.

Service-side automatic labeling

A service-side policy scans and labels files stored in SharePoint and OneDrive and emails passing through Exchange in the background, without the user's involvement. This is the option that reaches old content that is never opened. In simulation mode the policy does not label yet; it only lists the files it would mark, so false matches can be filtered out before enforcement.

In practice the four tools are used together. Default labels take care of new content, service-side labeling takes care of old content, and manual labeling stays where a machine cannot judge the content, for example the notes of an internal investigation.

Label structure before the rollout

Labels can be changed later, but reworking labels that are already applied and the priority order takes more effort than designing them well at the start. Before turning on Copilot, it is worth thinking through the following:

  1. Few parent labels. Four or five levels that users can tell apart without explanation. Each label's description (which users see) should say in one sentence what belongs there.
  2. Sublabels for the encryption variants. Within the Confidential level, there can be a separate sublabel for the “all employees” and the “named people only” variant. This way users do not have to set permissions, only choose.
  3. Order by sensitivity. Inheritance and downgrades both rely on it, so the order has to follow the real risk.
  4. Where to encrypt. Where the content must also be kept from Copilot, you need an encrypting label or a DLP rule for Copilot. A view-only variant blocks both copying and Copilot use for the people concerned, so decide this label by label.
  5. Collaboration with external parties. If guests or partners also need to open the encrypted documents, settle this in the label's permissions in advance, otherwise the label will hold up the work.
  6. A pilot in a small group. A label policy can also be published to groups, so a pilot group gets it first. The pilot shows which labels are hard to understand and where co-authoring gets stuck.

Once the labels are rolled out, Content explorer and Activity explorer in Purview show which locations hold labeled content and who changed labels in which direction. These show whether the structure works, before Copilot is rolled out widely.

Related service: Secure Copilot and Microsoft 365 AI rollout →

Contact

Ready to secure your critical systems?

Our experts will assess where your security stands and build a roadmap that fits your organization.

ARLITECH's office in Gödöllő

Visit us

You are welcome to visit our Gödöllő office in person.

Address
Centrum Office Building, 2100 Gödöllő, Dózsa György út 13, 3rd floor, office 309
Office hours
Mon–Fri, 9 a.m. to 5 p.m.
Get directions (opens in a new tab)