Smarter Microsoft Purview Sensitivity Labels To Block Content Analysis In Connected Experiences (Now extended to Office Apps)

Protecting sensitive information in Microsoft 365 is no longer something to think about later. It is now part of how you keep documents, presentations, and spreadsheets safer every day. 

With Microsoft’s latest update to Purview sensitivity labels, content marked with the right label can now be blocked from all connected experiences that analyse content in Word, Excel, and PowerPoint. That gives you stronger control over how sensitive files are handled across Microsoft 365.

What This New Update Offers

Microsoft is expanding an existing sensitivity label setting that controls whether connected experiences can analyse file content. The update now applies more broadly across Word, Excel, and PowerPoint. 

Before this change, the setting blocked only a subset of connected experiences. Now it blocks all connected experiences that analyse content in these apps, helping sensitive files stay more protected. 

Key changes at a glance

• The “Prevent some connected experiences that analyse content” setting now blocks all connected experiences that analyse content in Word, Excel, and PowerPoint. 
• Labelled files are not sent to Microsoft services for content analysis when this setting is applied. 
• Existing sensitivity labels that already use this setting automatically receive the expanded behavior. 

Why This Matters For Security And Compliance

If you work with confidential business information, this update matters because it adds another layer of protection around how that content is processed. It reduces the chance of sensitive data being analysed by connected Microsoft experiences when stricter protection is needed. 

That is especially useful when documents contain financial data, legal information, strategic plans, or other regulated content. It helps align everyday collaboration with stronger privacy and compliance expectations. 

Security and compliance benefits

• Stronger protection for sensitive files that should not be analysed by cloud-based content services. 
• Better support for privacy, governance, and compliance goals across Microsoft 365. 
• More control over how AI powered and smart features interact with labelled content. 

Who Is Affected By This Update

This update is relevant if you already use Microsoft Purview sensitivity labels in your organization. It directly affects how labelled content behaves in Word, Excel, and PowerPoint. 

It is also important for anyone responsible for security, compliance, governance, or user support. When labelled content behaves differently in Office apps, these are usually the teams that need to explain and manage the experience. 

Impacted audiences

• Organizations using Microsoft Purview Information Protection and sensitivity labels. 
• Security and compliance teams managing data classification policies. 
• End users working with files that use the “Prevent some connected experiences that analyse content” setting.

Do You Need To Change Your Label Configuration?

In most cases, no action is needed. Microsoft has designed this update so existing labels that already use the setting can automatically enforce the broader blocking behavior. 

That means you can benefit from stronger protection without rebuilding your labels from scratch. Still, reviewing current label settings is a smart way to make sure they match your data protection goals. 

Configuration impact

• No major label redesign is required to get the updated behavior. 
• The setting commonly associated with BlockContentAnalysisServices now has broader enforcement in Office apps. 
• Existing labels using this setting automatically receive expanded coverage. 

How To Enable the Setting To Block Content Analysis

To enable the blocking behavior, an admin must turn on the advanced BlockContentAnalysisServices setting for the label using PowerShell.

Prerequisites

• A sensitivity label already created in Microsoft Purview.
• Permissions to manage labels in Purview or Security & Compliance PowerShell.

Quick setup steps

• Open PowerShell and connect:
  • Install-Module ExchangeOnlineManagement (if needed)
  • Connect-ExchangeOnline
  • Connect-IPPSSession
• Find the label to update:
  • Get-Label | Select-Object DisplayName, ImmutableId 
• Enable the block setting on that label:
  • Set-Label -Identity “<Sensitivity Label Name>” -AdvancedSettings @{BlockContentAnalysisServices=”True”}
• Verify the setting:
  • Get-Label -Identity “<Sensitivity Label Name>” | Format-List DisplayName,Settings
  • Confirm [BlockContentAnalysisServices, True] appears in the output.
• Ensure the label is published to users through a label policy in the Purview portal so it shows up in Word, Excel, and PowerPoint.

Preparing for the Update: Admin Checklist

Even though this update does not require a large rollout project, a quick review can save time later. It also helps reduce confusion for users who may notice changes in smart or AI based experiences. 

A short internal readiness check is usually enough to make sure the update supports your policies and user expectations. 

Admin checklist

• Review labels that use the connected experiences restriction and confirm they are still assigned to the right types of content. 
• Identify teams that work with highly sensitive files, such as legal, finance, leadership, or product strategy. 
• Update internal help articles or support notes so users understand why some features may not be available on protected files. 
• Brief security, compliance, and helpdesk teams so they are prepared to answer questions. 

Compliance And Governance Considerations

From a compliance perspective, this update strengthens control over how labelled content interacts with Microsoft analysis services. That matters when your organization needs tighter boundaries around confidential information. 

It also changes how Information Protection labels affect AI and machine learning based experiences in Microsoft 365. For many organizations, that makes labelling decisions even more important than before. 

Key compliance notes

• Labelled files can now be fully blocked from Microsoft connected experiences that analyse content. 
• Existing sensitivity label enforcement becomes stronger without changing label names or structures. 
• AI and machine learning experiences that rely on content analysis may be restricted for these protected files. 

Frequently Asked Questions