Purview roadmap 572677 extends the auto-labeling coverage report to government clouds
An auto-labeling policy applies a sensitivity label when content meets conditions set by an administrator. Before enforcement, the administrator runs the policy in simulation: Purview evaluates potential matches without applying the label. Once the policy is turned on, the coverage report relates subsequent file-labeling activity to the latest simulation run.
The government-cloud roadmap entry names GCC, GCC High, and DoD, the web platform, and November 2026 general availability. That scope is important. Microsoft's separate communication for the worldwide rollout, associated with roadmap ID 568935, described a September 2026 public preview and a worldwide general-availability rollout beginning in late September. Those dates should not be used as availability dates for the three government clouds in roadmap item 572677.
Microsoft Learn documents the experience as Coverage by simulation context. For an eligible policy, an administrator opens Information Protection > Policies > Auto-labeling policies in the Purview portal, selects a policy that has completed simulation and is turned on, and chooses View coverage in the Coverage column. The report is a review surface; the documented change does not require an administrator to enable a new labeling action. In a government tenant, the presence of that action is the practical availability check as the planned rollout approaches.
The Purview report connects enforcement outcomes to one simulation snapshot
A simulation answers which items a policy would match during that run. Enforcement answers what happens when the active policy processes content. Files and classifications can change between those stages, so a raw simulation match count is a poor substitute for reviewing actual labeling outcomes. Microsoft describes simulation results as estimates and cautions that the enforcement count can differ.
The coverage report gives administrators two ways to read the intervening work. It separates files labeled during enforcement from those not labeled during enforcement, and identifies whether an observed file was found in simulation or has no simulation match found. “Observed files” includes files found during simulation, enforcement, or both. An administrator can therefore look beyond a single total: a file may have appeared in the simulated snapshot and then received a label, or it may have been processed during enforcement without a match in that snapshot.
The not labeled side needs closer inspection before it becomes a troubleshooting conclusion. Microsoft's documented breakdown includes files still pending, files enforcement has not yet attempted, and files for which applying a label failed. Those are different operational states. A pending file calls for a different judgment from an attempted file with an available failure reason.
Likewise, no simulation match found is a prompt to investigate timing and file state, not a diagnosis by itself. A file could have been created, modified, or classified after the latest simulation. The report is most useful when an administrator examines the relevant item and its activity rather than assuming every difference between simulation and enforcement represents a policy fault.
A 30-day Purview coverage window limits what the counts can prove
Microsoft says coverage reflects labeling activity after the latest simulation and remains available for 30 days for that simulation run. When the period expires, View coverage is unavailable for that run; an administrator needs another simulation to obtain updated coverage. A new run also changes the snapshot against which subsequent activity is understood.
That boundary prevents a tempting but misleading comparison. The coverage report is neither an all-time total for the policy nor an exact reconciliation of every simulated match against every later enforcement result. An all-time labeled figure can include activity outside the coverage window, so its count need not equal the number shown in coverage. Administrators preparing a status report should describe which simulation and review period their figures represent.
Workload boundaries matter too. Microsoft's policy-level enforcement metrics and Labeled items view report SharePoint and OneDrive files, not Exchange email or voicemail messages stored in Exchange. For an Exchange message, Microsoft directs administrators to Activity explorer and advises allowing 60 to 90 minutes for activity to appear. The file-focused coverage view should not be presented as one combined proof of labeling across every workload an auto-labeling policy can target.
What this means for you
If you administer Purview auto-labeling in GCC, GCC High, or DoD, plan to use the report to review an enforced policy against its most recent simulation, but wait for View coverage to appear in your tenant before treating the November 2026 roadmap target as delivered. For a policy already eligible for the report, review it within the 30-day window and investigate file states before drawing conclusions from aggregate counts.
- Confirm that the policy completed simulation and was turned on before looking for View coverage in the auto-labeling policy list.
- Compare successfully labeled files with those pending, not yet attempted, or failed; these categories describe different stages or outcomes of enforcement.
- Examine files with no simulation match in the context of changes since the latest simulation, rather than counting every unmatched file as a failure.
- Record the simulation and coverage period when sharing counts, and use Activity explorer separately when verifying Exchange email labeling.
Roadmap item 572677 offers government-cloud administrators a more precise way to answer a familiar operational question: what became of the files around the time an auto-labeling policy moved from simulation into enforcement? If the planned November rollout reaches their tenants, the report will make that review easier—provided its snapshot, 30-day window, and file-focused scope remain attached to every conclusion drawn from it.