Control 2.2: Sensitivity Labels and Copilot Content Classification — Portal Walkthrough
Step-by-step portal configuration for enforcing sensitivity label classification on Copilot-generated and Copilot-referenced content. This playbook covers the label groups taxonomy structure, Copilot Studio agent knowledge source label review, and auto-labeling policies with nested condition groups.
Prerequisites
- Microsoft Purview Information Protection Admin role
- Microsoft 365 E5 or E5 Compliance license
- Sensitivity label taxonomy deployed (see Control 1.5)
- Label inheritance policies defined
- Label groups migration status assessed (see Step 1a)
Steps
Step 1: Assess and Configure Label Taxonomy Structure (Label Groups)
Portal: Microsoft Purview portal Path: Solutions > Information Protection > Sensitivity labels
Microsoft Purview has replaced the parent/child label hierarchy with label groups as the modern label scheme (Microsoft 365 Roadmap ID 386900, general availability December 2025). Migration is rolling out gradually and might not yet be available in a given tenant; it is automatic for tenants created on or after October 1, 2025. Before configuring label policies, assess your current taxonomy state:
- Review existing labels — note whether they are currently organized as parent/child labels or label groups
- If still using parent/child structure, plan the migration timeline:
- Path: Solutions > Information Protection > Sensitivity labels — when the Migrate to the modern label scheme banner appears, select Get started, review the proposed scheme, resolve naming conflicts, then select Migrate
- Migration is irreversible — run it first in a test tenant that has the same label configuration as production
- Document all DLP policies that reference parent label names — these conditions must be verified after migration
- Label groups carry only name, description, color, and priority. Where a parent label was configured for label actions, published separately, or scoped differently from its sublabels, migration also creates a new sublabel with the same name, GUID, and settings; decide in advance whether to leave that sublabel published
- After migration, verify labels appear correctly grouped in the label groups structure
- Confirm that labels previously referenced as "sub-labels" now appear as individual labels within their label group
Impact on Copilot DLP policies: Label groups affect how DLP policies reference label hierarchies. After migrating, test the label-based DLP policy (Control 2.1, Type 1) with a document labeled under the new structure to confirm blocking behavior remains correct.
Step 2: Configure Label Inheritance for Copilot
Portal: Microsoft Purview portal Path: Solutions > Information Protection > Publishing policies > [Select policy]
Configure how sensitivity labels apply to Copilot-generated content. Copilot in Word, Copilot in PowerPoint, and Copilot in Outlook inherit the sensitivity label of the referenced source item for newly created content, and where more than one labeled source is referenced, the highest-priority label is used. Publish the labels that should be available for inheritance with the Files & other data assets and Emails scopes, and confirm the label's protection settings are the ones you want carried forward.
Step 3: Set Default Labels for Copilot Outputs
Portal: Microsoft Purview portal Path: Solutions > Information Protection > Publishing policies > [Policy] > Policy settings
Set the default sensitivity label for new documents created through Copilot. For FSI environments, the default should be at least "Internal — General" to prevent unlabeled content creation. Users can upgrade the label but should not be able to create unlabeled documents. A default label from a label policy never overrides an existing label — use a default sensitivity label for a SharePoint document library where a lower-priority label should be raised.
Step 4: Configure Mandatory Labeling for Copilot Content
Portal: Microsoft Purview portal Path: Solutions > Information Protection > Publishing policies > [Policy] > Policy settings > Require users to apply a label to their emails and documents
Enable mandatory labeling for all content types where Copilot generates output: - Documents created in Word, Excel, PowerPoint via Copilot - Emails drafted by Copilot in Outlook - Meeting notes generated by Copilot in Teams
Verify that the mandatory labeling prompt appears when Copilot creates content without a label.
Step 5: Review Copilot Studio Agent Knowledge Source Labels
Portal: Microsoft 365 admin center Path: Agents > All agents (Agent inventory tab, within the Copilot Control System)
Microsoft Purview sensitivity labels in Copilot Studio are in preview and are on by default for agents with supported knowledge sources (SharePoint, OneDrive for Business, SQL, Dataverse, Cosmos, Azure Blob Storage, Word, Excel, Outlook, Office groups, Office users). An agent response displays the highest-priority label from the content used for that response, plus a label on each citation — Microsoft does not assign a persistent effective label to the agent object. Before activating any Copilot Studio agent, review its knowledge source labels:
- In Microsoft 365 admin center > Agents > All agents, select the agent to review
- Navigate to the agent's knowledge sources configuration
- For each knowledge source, note the sensitivity label applied to the connected content (SharePoint sites, documents, or data sources)
- Identify the highest-priority label reachable through those knowledge sources — this is the label an agent response can display
- Document that label in the agent deployment record
- Confirm that the appropriate DLP policies are in place for that label tier before activating
Example: An agent with knowledge sources labeled "Confidential — Standard" and "Internal — General" can surface "Confidential — Standard" on its responses. Users interacting with this agent may trigger Confidential-tier DLP monitoring.
Note on encryption: Label-applied encryption is honored for the SharePoint knowledge source. For that supported source, Copilot Studio agents return encrypted-item text only where the requesting user holds EXTRACT. Validate additional knowledge sources separately rather than assuming encryption applied to external data is recognized.
Governance gate for Recommended/Regulated: Agents that can surface Confidential or higher labels require compliance sign-off as part of the deployment approval workflow.
Step 6: Configure Auto-Labeling Policies with Nested Conditions
Portal: Microsoft Purview portal Path: Solutions > Information Protection > Policies > Auto-labeling policies > + Create auto-labeling policy
Service-side auto-labeling policies support nested rule logic (AND/OR/NOT) through condition groups with logical operators between groups, the same way DLP complex rule design works. The client-side label setting auto-labeling for files and emails does not support nested rule logic. Auto-labeling policies can also override manually applied labels on files in SharePoint and OneDrive (Microsoft 365 Roadmap ID 558342, general availability April 2026), but only where the policy's label has a higher priority than the existing label — a manually applied higher-priority label is never overridden. Organizations should verify their label priorities and override settings to avoid unintended label changes on files where users have made deliberate classification decisions.
- Create or edit an auto-labeling policy
- In the conditions section, create condition groups:
- Add a condition group for each grouped set of conditions
- Within a group, select AND (all conditions must match) or OR (any condition matches)
- Between groups, select the operator that excludes the scenarios you do not want labeled
- FSI example — MNPI auto-labeling with contextual exclusion:
- Condition Group 1 (AND): Contains CUSIP/ISIN pattern AND contains earnings/M&A context keyword
- OR
- Condition Group 2: Contains MNPI keyword dictionary match
- NOT: File path contains "/public-disclosures/" (exclude investor relations materials)
- On the Additional label settings page, select All locations to override manually applied lower-priority labels on emails and on SharePoint and OneDrive files. Emails only limits the override to email
- New policies save in simulation mode — run simulation for 14 days before enforcing
- Review simulation false positive rate (target <3% before enforcement)
- If a SharePoint document library already has a default sensitivity label and you need that label applied to files that predate the library configuration, create the dedicated auto-labeling policy for default-library labels rather than rebuilding the library as a content-inspection rule
- Turn the policy on after validation
- After enforcement, review Coverage by simulation context and the policy's Labeled items tab, including the Failed view, to confirm which files were labeled, are pending, or could not be labeled
Step 7: Configure Label-Based Access Restrictions for Copilot
Portal: Microsoft Purview portal Path: Solutions > Information Protection > Sensitivity labels > [Label] > Encryption settings
For labels that include encryption, review how Copilot interacts with encrypted content: - Copilot accesses content using the current user's permissions - EXTRACT (shown as Copy) controls whether Copilot and agents can display encrypted-item text for the requesting user. With VIEW but not EXTRACT, Copilot normally does not summarize the item but can still return a link to it - OWNER includes EXTRACT, and the person applying encryption is the Rights Management owner; do not infer the OWNER outcome from the recipient template alone - Test unopened user-defined-permissions items, directly referenced items where supported, and an item open in an Office app; data-in-use is a distinct case - If Edge DLP is not deployed, test the active encrypted browser-tab behavior. Test external plugins/Graph connectors separately because their label/encryption metadata is not generally recognized by Microsoft Copilot Chat - New content inheritance depends on the supported source/surface and encryption configuration; record the observed result rather than assuming all encrypted sources inherit identically
Permission Level Names: The Microsoft Purview portal and the custom permissions dialog in Word, Excel, and PowerPoint for Windows (version 2411 and later) use updated permissions level names — Reviewer is now Restricted Editor, Co-Author is now Editor, and Co-Owner is now Owner. Other applications continue to use the original naming. Save As, Export is not included in the Editor level when it is configured in the Microsoft Purview portal — assign it through custom permissions where users need to create derivative documents. Existing labels using the old permission names continue to function, but new label configurations and documentation should use the updated names.
Step 8: Review Label Activity, Coverage, and Failures for Copilot Content
Portal: Microsoft Purview portal Path: Solutions > Information Protection > Reports; Solutions > Information Protection > Policies > Auto-labeling policies; Solutions > Data Lifecycle Management > Explorers > Content explorer; Solutions > Data Classification > Activity explorer
Use the current Purview monitoring surfaces together, because no single page answers every Copilot-label question: - Information Protection > Reports — monitor label application and adoption trends over the 30-day reporting window - Auto-labeling policy review pages — inspect Coverage by simulation context, Labeled items, and Failed results for service-side auto-labeling on SharePoint and OneDrive - Content explorer — export the current labeled-item snapshot by workload and label when you need inventory evidence. Encrypted sensitivity labels don't surface in Content explorer for SharePoint and OneDrive, so supplement this with Activity explorer, audit, or the auto-labeling policy review pages when those workloads use encrypted labels - Activity explorer — monitor recent label activity events and downstream handling, including label applies/changes/removals - DSPM / DSPM for AI (classic) — where enabled, review AI app and agent reporting alongside the label-specific surfaces above - Default labels for meetings and calendar events — verify the label policy setting Apply a default label to meetings and calendar events is configured for regulated user groups. For Teams, the default label applies to new calendar events but is not applied automatically when an existing unlabeled meeting is updated. Default labeling helps prevent unclassified meeting content (transcripts, notes, recordings) from being surfaced by Copilot without appropriate classification.
FSI Recommendations
| Tier | Recommendation |
|---|---|
| Baseline | Default label on Copilot-created content; label inheritance from source documents; assess label groups migration status; audit Copilot Studio agent knowledge source labels |
| Recommended | Mandatory labeling; highest-priority label inheritance; label groups migration completed and DLP policies tested; auto-labeling policies with nested condition groups for FSI data patterns; agent knowledge source label review as part of deployment approval |
| Regulated | Mandatory labeling with no downgrade option for Copilot content; full auto-labeling with nested conditions covering all FSI SIT categories; automated classification with justification auditing; agents require compliance sign-off; real-time label compliance monitoring |
Next Steps
- Proceed to PowerShell Setup for label enforcement automation
- See Verification & Testing to validate label behavior, label groups, and agent knowledge source labels
- Review Control 2.1 for DLP integration with sensitivity labels, including label-based response blocking (Type 1)
- Back to Control 2.2