Microsoft Expands Purview Labels to Block Copilot From Analyzing Office Files

Microsoft is expanding a Purview sensitivity label setting so organizations can block Microsoft 365 Copilot and other connected experiences from analyzing protected Office files.

The change was announced in Microsoft 365 Message Center alert MC1297982. It applies to Word, Excel, and PowerPoint files that use a sensitivity label configured with the setting named “Prevent some connected experiences that analyze content.”

Once the update reaches a tenant, those labeled files will no longer be sent to Microsoft connected experiences for content analysis. Microsoft says the change applies automatically to existing labels that already use the setting, with no label configuration change required for those labels.

What Microsoft Is Changing

The existing setting previously blocked only some connected experiences that analyze file content. Microsoft is now expanding the behavior so the same setting blocks all Microsoft connected experiences that analyze content in Word, Excel, and PowerPoint.

Microsoft defines connected experiences that analyze content as Office features that use document content to provide services such as design recommendations, editing suggestions, data insights, translations, and similar functions.

That matters because Microsoft 365 Copilot also relies on access to organizational content to generate summaries, answers, and suggestions. Microsoft’s Set-Label documentation says BlockContentAnalysisServices can prevent Word, Excel, PowerPoint, and Outlook content from being sent to Microsoft for content analysis and affects services such as Microsoft Copilot for Microsoft 365.

Area	What changes
Apps	Word, Excel, and PowerPoint
Control	Purview sensitivity label setting that blocks connected experiences that analyze content
Previous behavior	Blocked only a subset of connected experiences
New behavior	Blocks all Microsoft connected experiences that analyze content in supported Office apps
Configuration impact	Applies automatically to existing labels that already use the setting

Why This Matters for Copilot Security

The update gives enterprises a clearer way to keep sensitive Office files out of AI-powered analysis workflows. That is important for documents containing legal material, financial data, acquisition plans, source code notes, employee records, board documents, or other restricted information.

Microsoft already offers a separate Purview option for Copilot controls through DLP policies for Microsoft 365 Copilot and Copilot Chat. That feature can exclude files and emails with selected sensitivity labels from being processed by Copilot responses.

The sensitivity label setting described in MC1297982 is broader inside Office apps because it targets connected experiences that analyze file content. For organizations adopting Copilot, both controls may form part of the same data governance strategy.

Rollout Timeline

Microsoft said the change entered Public Preview in mid-May 2026 and is expected to complete Public Preview rollout by mid-July 2026. General Availability began in mid-June 2026 and is expected to finish worldwide by late July 2026.

The updated timeline appears in MC1297982, which Microsoft revised on June 18, 2026. The update affects organizations using Microsoft Purview sensitivity labels in Word, Excel, and PowerPoint.

Support also depends on the Office app version and update channel. Microsoft’s minimum versions table lists support for “Prevent connected experiences that analyze content” across Office update channels.

Milestone	Timing
Public Preview start	Mid-May 2026
Public Preview completion	Expected by mid-July 2026
General Availability start	Mid-June 2026
Worldwide GA completion	Expected by late July 2026

How Sensitivity Labels Fit In

Microsoft Purview sensitivity labels let organizations classify and protect data as users create or edit Office files. Admins can publish labels so users see them directly in Microsoft 365 apps.

Labels can be used for classification, encryption, access restrictions, markings, and policy-driven handling. The expanded connected-experience block adds another layer for organizations that want to limit how highly sensitive content is processed by cloud and AI services.

This is especially relevant in regulated industries. Finance, healthcare, government, legal, defense, and research organizations often need to separate ordinary business content from documents that should not be analyzed by external or cloud-powered services.

Admins Still Need to Review Label Configuration

The update does not mean every sensitivity label will automatically block Copilot or other content analysis services. It applies to labels that already use the relevant setting.

For labels that do not already use it, administrators need to configure the advanced setting. Microsoft’s BlockContentAnalysisServices setting is configured through Security and Compliance PowerShell, not through the standard Purview portal label wizard.

Admins should review labels such as Confidential, Highly Confidential, Legal Privileged, Board, HR Restricted, or M&A to confirm whether they should block connected experiences that analyze content.

• Review labels that already use “Prevent some connected experiences that analyze content.”
• Decide which labels should block Microsoft 365 Copilot and connected analysis features.
• Confirm Office app version and update channel support.
• Update internal documentation for compliance and helpdesk teams.
• Warn users that some smart Office features may stop working on protected files.
• Test the behavior on sample Word, Excel, and PowerPoint files before broad rollout.

What Users May Notice

Users working with protected documents may see some Office experiences behave differently. Features that depend on content analysis may not work as expected when the document carries a blocking sensitivity label.

Examples can include AI summaries, certain intelligent suggestions, design assistance, data insights, translation features, and other cloud-backed services that need to inspect file content. Microsoft’s connected experiences documentation lists several services that analyze Office content to provide these kinds of capabilities.

This tradeoff is intentional. The goal is to let organizations choose stronger privacy and compliance controls for selected files while keeping productivity features available for less sensitive content.

How It Compares With Copilot DLP Controls

Microsoft’s Copilot DLP feature and the Purview label setting address related but different needs. The DLP option can stop labeled files and emails from being used in Copilot responses. The Office label setting blocks content from being sent to connected experiences for analysis in the Office apps themselves.

The Copilot DLP guidance says identified items can still appear in citations, but the content of those items is not used in the response or accessed by Copilot when excluded by policy.

Security teams should consider using both approaches where appropriate. One protects Copilot processing decisions, while the other protects Office file content from connected analysis services.

Compatibility and Deployment Checks

Before relying on the control, organizations should check client versions. Microsoft’s Office sensitivity label version guidance shows the minimum versions needed for “Prevent connected experiences that analyze content.”

Organizations should also make sure sensitivity labels are published to the right users. The Office apps sensitivity label guidance notes that labels appear in Office apps after admins publish them from the Microsoft Purview portal.

The change gives enterprises a more direct way to control how sensitive Office files interact with AI and cloud-powered analysis features. For companies rolling out Copilot, it also turns sensitivity labels into a more important part of AI governance.

FAQ