Microsoft Purview is introducing on-demand classification of files in SharePoint and OneDrive, allowing discovery and classification of sensitive historical data. This pay-as-you-go feature will roll out in public preview from late March to early April 2025 and be generally available by late June 2025. Admins can configure this feature, which will automatically apply relevant policies. No immediate action is required from admins before the rollout.
Coming soon to Microsoft Purview | Information Protection: On-demand classification of files is a new capability that will help you discover and classify sensitive content in historical data in Microsoft SharePoint Online and Microsoft OneDrive. This includes files that have never been scanned or files that have not been scanned in some time.
On-demand classification of files is a pay-as-you-go (PAYG) feature (not part of the E5 license).
This message is associated with Microsoft 365 Roadmap ID 475062.
When this will happen:
Public Preview: We will begin rolling out late March 2025 and expect to complete by early April 2025.
General Availability (Worldwide): We will begin rolling out mid-June 2025 and expect to complete by late June 2025.
How this will affect your organization:
Before this rollout, classifying files for sensitive data only applies to new or modified items (but not to existing content that has not been edited or opened by users) after a new classifier is created in Purview.
After this rollout, this new feature will help in the following situations:
After you execute an on-demand classification, any policy configured in DLP, MIP, or DLM will be automatically triggered to apply action if corresponding classifiers are found.
This feature will be available by default for admins to configure. This screenshot shows how to configure the feature in the new Purview portal > Data Loss Prevention > Classifiers > Data scans > PHI scan:
What you need to do to prepare:
This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.
Before rollout, we will update this post with new documentation.