Kommentar
Åtkomst till den här sidan kräver auktorisering. Du kan prova att logga in eller ändra kataloger.
Åtkomst till den här sidan kräver auktorisering. Du kan prova att ändra kataloger.
Before you enforce an auto-labeling policy, run it in simulation mode. Simulation shows which items the policy would label without changing them. Review the match results and source distribution to decide whether the policy is ready for enforcement.
This article describes the newer simulation overview page. Available fields and review options can vary by portal experience. To review policy results after you turn on a policy, see Monitor your auto-labeling policy.
Important
Before you begin, make sure that you have the required roles and permissions. For more information, see Policy-level labeling activity for SharePoint and OneDrive.
To view matched text in a file on Items to review, you also need the Data Classification Content Viewer role.
Review the simulation overview
Make sure the policy is running in simulation mode and has started scanning the configured locations. Then follow these steps:
- Sign in to the Microsoft Purview portal.
- Select Solutions > Information Protection > Policies > Auto-labeling policies.
- Select the name of a policy that is running in simulation mode.
- In the policy details panel, select Summary > View details to open the Simulation overview page.
On the Simulation overview page, the following key metrics about the policy are available:
| Field | Description |
|---|---|
| Label | The sensitivity label that the policy applies to matched items. |
| Status | Simulation status: Simulation in progress, Simulation almost complete, Simulation complete, Simulation expiring soon, Expired, or Policy can't be published. |
| Duration | The length of time the simulation has been running in days and hours. |
| Matched items | The total number of items that matched the policy conditions across all workloads. |
| Sample items | When displayed, the number of sampled items available for review. Samples are retained for 30 days. |
| Policy matches per rule | Shows details about the policy rules and their matches: - Total Rules: the number of rules in the policy, not the number of rules with matches. - Total Matches: the number of items that matched rules. - Rule name: the name of the rule in the policy. - Matches: the number of items that matched this rule. - Location: The workload where matches occurred (Exchange, SharePoint, or OneDrive). Use the per-rule match counts to identify which rules matched and whether each rule produces the expected results. |
| Matches by source | A donut chart showing matches distributed across workloads, with an item count and percentage for each of the following workloads: - Exchange: Email messages that matched the policy. Matched Exchange items are based on sampled data and might not represent all mailboxes in the policy scope. - SharePoint: Files in SharePoint sites that matched. - OneDrive: Files in OneDrive accounts that matched. |
| Sensitive info types | This table lists the sensitive information types (SITs) detected across the matched items and the number of matches for each type. Use it to identify which SITs produce the most matches. |
| Configuration details | Shows the policy's locations, exclusions, and rule configuration. Review these details alongside the match results to check the policy scope. |
| Review sample items | Select Review sample items, when displayed, to open Items to review. For each item, you can: - Preview the file or email content, where supported and with the required permissions. - View properties such as the file location, modified date, and detected SITs. - Read a Contextual summary, in supported portal experiences, that explains why the item matched. Viewing matched content requires the Data Classification Content Viewer role. |
Note
The Matched items count is an estimate. During simulation, the service samples content across your configured locations. The actual enforcement count might differ slightly.
Next steps
Based on the simulation results, choose the appropriate next step:
- Turn on policy when the policy is eligible and you've reviewed the results and warnings. Simulation complete, Simulation almost complete, and Simulation expiring soon can be eligible states, but eligibility doesn't replace checking that the matches meet your requirements.
- Edit the policy when the policy produces too many false positives (match count is high) or too few matches. Edit the conditions, and then restart the simulation to get updated results.
Important
If you configure a scheduled turn-on date, the policy is scheduled to turn on automatically without waiting for your review. The displayed date isn't confirmation that activation succeeded. Cancel the scheduled turn-on date if you need more time.