Published May 5, 2025
Microsoft Purview has introduced collection policies for targeted signal discovery and data collection, allowing administrators to specify which Sensitive Information Types and activities are collected. Public Preview is available now, with General Availability starting late June 2025. This feature impacts several Purview solutions and requires no immediate action until an initial policy is created.
Updated June 27, 2025: We have updated the timeline below. Thank you for your patience.
We have introduced a new configuration option in Microsoft Purview called collection policies for targeted signal discovery and collection. Collection policies will allow administrators to fine tune the signals and data collected for Purview solutions at the tenant level. This includes specifying which Sensitive Information Types (SITs) are classified and what activities are collected on Windows endpoint devices.
This message is associated with Microsoft 365 Roadmap ID 479760.
When this will happen:
Public Preview: Available now.
General Availability (Worldwide): We will begin rolling out late June 2025 (previously early June) and expect to complete by mid-July 2025 (previously late June).
How this will affect your organization:
Key benefits of collection policies
Purview solutions impacted
There is no immediate impact of this feature release. If you choose to leverage collection policies, admins can now choose which signals to discover in devices.
After you enable collection policies, you may see various updates to the Purview DLP audit experience. These updates may affect your organizations current configuration in the following ways:
This feature is available by default for admins to configure.
What you need to do to prepare:
There is no immediate impact of this feature release until you create an initial collection policy and Always audit is enabled in DLP (Windows endpoint devices only). To prepare for this upcoming enhancement to the Purview portal, we recommend you:
This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation.