Microsoft Entra ID Governance

Create configuration snapshots

In brief

Learn how to create configuration snapshots in Microsoft Entra Tenant Governance to capture tenant configuration for baselines or audit evidence

What Entra admins need to know

Review the documentation change to determine whether it affects tenant configuration, security posture, or rollout plans.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

Open on Microsoft Learn ↗

The comparison below is an extract of the Microsoft Learn article showing only the changed content. Open the full article for complete context.

new file mode 100644

title: Create configuration snapshots titleSuffix: Microsoft Entra ID Governance description: Learn how to create configuration snapshots in Microsoft Entra Tenant Governance to capture tenant configuration for baselines or audit evidence ms.topic: how-to ms.date: 07/28/2026

Create configuration snapshots

Configuration snapshots capture the current state of selected tenant configuration resources. Create a snapshot when you want to establish a configuration baseline for monitoring configuration drift of a tenant in a known-good configuration, or to collect configuration data for audit evidence.

Prerequisites

  • The tenant has licenses for Tenant Governance Basic or Tenant Governance Premium. For current licensing requirements, see Microsoft Entra Tenant Governance licensing.
  • Tenant Governance Basic includes a quota for the number of resources that you can snapshot. A tenant gets additional quota for snapshotted resources for each Tenant Governance Premium license it has. If your tenant exceeds its monthly quota, you can't create new snapshots.
  • The signed-in user is in a Microsoft Entra privileged role and has read permissions for every resource type included in the snapshot.
  • The Tenant Configuration Management service has service authorization for every workload and resource type included in the snapshot. To assign or remove permissions for the service, see Configure configuration management service permissions.

Create a snapshot

To create a configuration snapshot, follow these steps:

  1. Sign in to the Microsoft Entra admin center as a user with the required role and permissions.

  2. Browse to Tenant Governance > Snapshots.

  3. Select New snapshot.

  4. On the service and resource selection step, select the resource types to include in the snapshot.

  5. On Settings, enter a unique display name of at least eight characters and an optional description.

  6. On Permissions, review whether the service has permission to:

    • Read the required Microsoft Graph resources, to snapshot Microsoft Entra or Intune resources.
    • Authenticate to Exchange, to snapshot Exchange, Defender, or Purview resources.
    • Use the Teams Reader role, to snapshot Teams resources.
  1. On Review and create, review the summary and create the snapshot.

Check snapshot status

Snapshot creation is asynchronous. A snapshot progresses from Not started to In progress. Select Refresh in the command bar to check progress until the snapshot succeeds, fails, or is partially successful. The time it takes to complete a snapshot is roughly proportional to the number of resources being snapshotted.

View snapshot details

To view the details of a completed snapshot, follow these steps:

  1. Open a completed snapshot from the snapshots list.
  2. On the Overview tab, review the name, description, creation time, completion time, expiration time, status, and included resource counts. Errors, if any, appear on this page. You can expand an error to see details.
  3. On the Configuration baseline tab, view or download the generated configuration baseline JSON.

Create a monitor from a snapshot

To create a configuration monitor from a completed snapshot, follow these steps:

  1. Open a completed snapshot.
  2. Select Create as Monitor.
  3. The monitor creation wizard opens with the snapshot baseline imported. Snapshot-only fields, such as @odata metadata and object ID, are removed from the baseline. Continue with the remaining steps in the monitor creation experience, such as setting a name for the monitor and reviewing permissions, as described in Create a configuration monitor.

Related content