Skip to Content

MC1469958 Microsoft Purview Auto-labeling scalability, policy management, and reporting enhancements

Summary

Microsoft Purview Information Protection increases auto-labeling simulation capacity from 4 million to 20 million items, expands SharePoint site targeting, and enhances reporting with Sensitive Information Type summaries and processing charts. Rollout begins September 2026 with no end-user impact or required action.

Microsoft 365 Message Center ID: MC1469958
Last Modified: September 11, 2026
Category: Message Center
Tags: New feature
Status: Launched
Products & Platforms: Microsoft 365 suite, Microsoft Purview

Microsoft Message

Microsoft Purview Information Protection is enhancing auto-labeling policy management to help administrators deploy, validate, and monitor labeling policies across larger data estates. These updates increase policy scale limits, improve SharePoint targeting capabilities, and provide enhanced reporting and auditing insights to help organizations better understand policy effectiveness and processing activity.

Rollout schedule

  • Public Preview: Available beginning early September 2026 and expected to complete by mid-September 2026.
  • General Availability (Worldwide): Rollout will begin in late October 2026 and is expected to complete by late October 2026.

Impact on your organization

  • Auto-labeling simulation capacity will increase from 4 million items to 20 million items.
  • Administrators will be able to select up to 1,000 individual SharePoint sites when configuring policies.
  • Adaptive scopes will support up to 50,000 SharePoint sites per policy.
  • Audit and reporting experiences will provide additional visibility, including summaries of the Sensitive Information Types (SITs) detected when labels are applied.
  • SharePoint sites can be filtered using the SiteTemplate property during policy configuration.
  • A new 30-day processing chart will display the number of files processed each day, helping administrators monitor policy throughput and activity over time.

These enhancements are on by default and will be available automatically as the rollout reaches your organization. Existing auto-labeling policies will continue to function without modification.

There is no expected impact to end users.

Action required / Recommendations

No action is required.

  • Review existing auto-labeling policies that were previously constrained by simulation or scope limits.
  • Evaluate whether additional SharePoint sites can now be included in current policy configurations.
  • Update reporting and operational processes to leverage the new Sensitive Information Type reporting details and processing throughput metrics.
  • Review Microsoft documentation for auto-labeling policies and adaptive scopes.

Purview Auto-labeling link

Compliance considerations

Question: Does the change alter how existing customer data is processed, stored, or accessed?

Answer: Auto-labeling policies will continue to process customer content, but the scale of policy evaluation and simulation increases substantially. The change expands processing capacity rather than changing labeling behavior.

Question: Does the change modify Information Protection labels or Sensitive Information Types?

Answer: Reporting will include additional visibility into the Sensitive Information Types detected when labels are applied. No changes are made to label functionality or SIT definitions.

Question: Does the change modify Audit logging capabilities?

Answer: Additional auditing and reporting insights will be available, including detected SIT summaries and enhanced policy processing visibility.

Question: Does the change alter how admins can monitor, report on, or demonstrate compliance activities?

Answer: New reporting capabilities include SIT detection summaries and a 30-day processing chart showing files processed per day, improving administrative visibility into policy effectiveness and throughput.

Question: Does the change include an admin control?

Answer: Administrators can utilize expanded SharePoint site selection limits, adaptive scope limits, and SiteTemplate filtering during policy configuration.