Purview Scanner SQL Reporting Targets September 2026 GA

Microsoft is planning a scanner-data export capability for the Microsoft Purview compliance portal, aimed at organizations that need their own reporting on scanned repositories rather than relying solely on the portal’s built-in views.
The Microsoft 365 Roadmap entry, ID 494839, was updated on July 13, 2026 and remains marked In development. Microsoft says labeling, classification, and protection actions from Information Protection scanner runs will be stored in SQL tables, providing a data foundation for custom reports.

Illustrated cybersecurity dashboard showing protected servers, cloud storage, file controls, databases, and analytics charts.What is changing​

The Purview Information Protection scanner runs on Windows Server and crawls supported on-premises file repositories, including SMB and NFS shares and supported SharePoint Server libraries. It can identify sensitive information, apply sensitivity labels, and protect files based on Purview policies.
Today, scanner operators can review results in the Purview portal and through locally generated reports. Microsoft’s documentation says completed scans produce text summaries and detailed CSV reports in the scanner’s local reports directory. Those files include per-file information and scan results, but they are less convenient for scheduled dashboards, long-term trend analysis, or joining scanner findings with other security and compliance data.
The planned change appears intended to address that reporting gap by retaining scanner action data in SQL tables. Microsoft’s roadmap description specifically calls out the ability to assess the state of scanned repositories and build custom reports from labeling, classification, and protection activity.

Why it matters​

For compliance teams, the useful outcome is not merely another export button. A structured SQL-backed dataset could let administrators build recurring reports in Power BI, SQL Server Reporting Services, or internal tooling without scraping CSV output from each scanner host.
Potential reporting uses include:
  • Tracking how many files were scanned, classified, labeled, or protected by repository and time period.
  • Identifying repositories with recurring sensitive-data findings.
  • Comparing discovery-only results with the effect of enforcement and labeling policies.
  • Feeding scanner activity into broader governance, audit, or data-loss-prevention reporting.
Microsoft already requires an SQL Server instance for scanner configuration data, and its documentation notes that scanner-generated reports can be queried to investigate file exposures. The roadmap item suggests a more explicit, standardized reporting surface for scanner outcomes, although Microsoft has not yet published table schemas, retention behavior, permissions requirements, or supported reporting tools.

Timing and availability​

Microsoft lists preview availability as May 2026 and general availability as September 2026. However, the item is still labelled In development as of July 13, so admins should treat both dates as targets rather than release confirmations.
The feature is planned for worldwide commercial tenants as well as GCC and GCC High, with both Preview and General Availability release rings listed. Despite the roadmap’s “Desktop” platform label, the affected component is the Information Protection scanner service deployed on Windows Server.
Organizations already using the scanner should keep their existing CSV-report collection and retention processes in place until Microsoft documents and ships the SQL-table reporting capability.

References​

  1. Primary source: Microsoft 365 Roadmap
    Published: 2026-07-13T23:07:14.8221961Z
  2. Official source: learn.microsoft.com
  3. Official source: cdn-dynmedia-1.microsoft.com
 

Back
Top