Microsoft Purview | Information Protection: Apply default SharePoint library sensitivity labels to data at rest
Microsoft Purview will enable an auto-labeling policy to apply default SharePoint library sensitivity labels to existing files, improving labeling coverage without user action. This opt-in feature, rolling out in October 2026, requires administrator configuration and supports up to 10 SharePoint sites per policy. Microsoft Purview is introducing a new auto-labeling policy that applies a SharePoint document library’s default sensitivity label to existing files stored in that library. Previously, default library sensitivity labels were applied only to new or modified files. With this update, organizations can extend labeling to historical content, including files that existed before the default library sensitivity label was configured for the site, without requiring users to open or edit files and without creating content inspection rules. This capability helps improve labeling coverage, reduce the number of unlabeled files, and support information protection objectives across existing SharePoint content. Rollout schedule General Availability (Worldwide): Beginning in early October 2026 and expected to complete by mid-October 2026 Impact on your organization Who is affected Microsoft Purview administrators who manage sensitivity labels and auto-labeling policies Organizations using SharePoint document libraries with default sensitivity labels configured Users are affected only if administrators enable and configure this new policy Platforms and services Microsoft Purview Information Protection Microsoft Purview Auto-labeling SharePoint Online What will happen After an administrator creates and enables this policy: Auto-labeling will evaluate existing files in selected SharePoint document libraries. Files that do not have a sensitivity label applied will receive the library’s default sensitivity label. Files that existed in a library before the default sensitivity label was configured can now be labeled automatically. Files that have a lower-priority sensitivity label applied may be upgraded to the library’s default sensitivity label (depending on the policy setting). Users are not required to open or edit files for labeling to occur. Content inspection conditions, such as sensitive information types or trainable classifiers, are not required for this policy. Labeling occurs as a background service process and is not immediate. The same default sensitivity label already applied to new or modified files in the library is used for existing files. The feature is opt-in […]
The post Microsoft Purview | Information Protection: Apply default SharePoint library sensitivity labels to data at rest appeared first on M365 Admin.
Published on:
Learn moreWe can help you with Microsoft Purview | Information Protection: Apply default SharePoint library sensitivity labels to data at rest
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
Dynamics 365 Contact Center: Quality evaluation – One-Time Evaluation Frequency
Quality evaluation plans now support a Once frequency type for both case evaluations and conversation evaluations. When creating an evaluation...
Microsoft Teams: Phishing Detection in Teams Messaging
Microsoft Teams is introducing AI-powered phishing detection that uses conversation context to identify phishing and social engineering in hig...
Microsoft Purview: Data Loss Prevention-Admin Units Support for Copilot & Cowork DLP
Microsoft Purview Data Loss Prevention is extending Administrative Units support to Microsoft 365 Copilot, Copilot Chat, and Cowork. This enab...
Take action: NTLMv1 hardening changes might affect network connections on devices without Credential Guard
Beginning with the October 2026 security update, Windows 11, versions 26H2, 25H2, and 24H2, along with Windows Server 2025 enforce restriction...
Power Platform – Recreate connections made to the Azure DevOps connector prior to September 2024
We identified that an app, flow, or agent in your environment utilizes a connection to the Azure DevOps connector that was created prior to Se...
Microsoft Purview | Data Loss Prevention: Count of labeled documents condition for Exchange Online
Microsoft Purview DLP introduces a new Exchange Online condition to detect emails with a high count of sensitivity-labeled attachments, enhanc...
Microsoft Teams: Automatic recording and transcription options align with admin policies
Microsoft Teams will update meeting options to show only automatic recording and transcription settings allowed by assigned policies, adding a...
Copilot Studio – Information regarding the end of support for selected AI models
We are announcing the end of support for selected AI models on the Standard and GitHub Copilot harnesses in Copilot Studio. Beginning on each ...
Updates available for Microsoft 365 Apps for all channels
We’ve released updates to the following update channels for Microsoft 365 Apps: Current Channel Monthly Enterprise Channel Semi-Annual E...
Microsoft Planner: AI-generated status reports in Planner Agent
Microsoft Planner now includes AI-generated status reports via Planner Agent in Microsoft 365 Copilot, summarizing plan progress, risks, and n...