Microsoft Purview can now prevent content analysis by connected experiences using a new sensitivity label setting or Double Key Encryption. This feature is part of Microsoft 365 Roadmap ID 398991 and will be available in Public Preview in early June via Current Channel Preview v2406+ and for General Availability in late June/early July 2024 via Current Channel v2406+. The setting is off by default and requires PowerShell configuration.
Use a new sensitivity label setting or protection with Double Key Encryption to prevent content within Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis as a privacy control, even when these are stored in Microsoft’s cloud, such as SharePoint or OneDrive.
This helps your organization to optimize your data privacy needs on a per-content basis using the familiar configurations and end-user experiences available with Microsoft Purview.
This message is associated with Microsoft 365 Roadmap ID 398991
When this will happen:
Public Preview: Available early June via Current Channel Preview v2406+
General Availability: Available late June/early July 2024 via Current Channel v2406+ in worldwide environments.
How this will affect your organization:
This new label setting is off by default. When a sensitivity label is configured with BlockContentAnalysisServices=True
, files and emails with this label will not send content to Microsoft services for analysis.
If you’re already using Double Key Encryption in your organization, files and emails protected with DKE will automatically prevent content in use from being sent to analysis services.
What you need to do to prepare:
If your organization does not need to disable some connected experiences that analyze content in use, no action needed.
The sensitivity label configuration is not available in the Microsoft Purview portal or the Microsoft Purview compliance portal. You must use the PowerShell advanced setting BlockContentAnalysisServices with the Set-Label or New-Label cmdlet after you've connected to Security & Compliance PowerShell.
The sensitivity label capability requires the built-in labeling client for Microsoft Purview in Office apps; the label setting is not compatible with the legacy Azure Information Protection Add-in.
Learn more: Prevent some connected experiences that analyze content