Skip to main content

Microsoft Entra ID Backup and Recovery Guide

Rawson Wade, , Updated , 16 min read
Microsoft Entra ID Backup and Recovery Guide

TL;DR: Microsoft Entra Backup and Recovery has been generally available since 30 June 2026. It's included with Microsoft Entra ID P1 or P2 in workforce tenants, it runs automatically, and it keeps seven days of daily backups of your core tenant objects: users, groups, applications, service principals, Conditional Access policies, named locations and key tenant policies. You compare a backup with the live tenant in a difference report, then recover individual objects, whole object types or everything in scope. No user or app can delete or switch off the backups, not even a Global Administrator. It isn't a complete identity backup strategy (seven days is short, and hard-deleted objects can't be brought back), but it's the fastest way to undo a bad change.

What Changed When Entra Backup and Recovery Reached General Availability

We first wrote this guide during the public preview, which began in March 2026. Microsoft announced general availability on 30 June 2026. The changes that matter:

Public preview (March 2026)General availability (30 June 2026)
Retention5 days7 days
LicensingNot announcedIncluded with Microsoft Entra ID P1 or P2
Tenant typesNot announcedWorkforce tenants only. External ID and Azure AD B2C tenants aren't supported
Longer retentionNoneA 30-day extension through Microsoft 365 Backup is on the Microsoft 365 roadmap for December 2026 (not yet released)

Everything below reflects the GA service. Where something comes from our own preview testing rather than Microsoft's documentation, we say so.

Why Microsoft Entra ID Needed a Native Backup Solution

If you've spent any time managing an Entra ID tenant at scale, you already know the sinking feeling: someone modifies a Conditional Access policy at 2 AM, a bulk user import goes sideways, or, worst case, an attacker with compromised admin credentials starts methodically deleting service principals. Until this service shipped, your options for recovery ranged from "hope you exported a config backup recently" to "call Microsoft Support and pray."

Third-party identity backup products exist and they're excellent, but they add licensing cost, integration overhead, and another vendor to manage. Many smaller organisations simply never adopted one, leaving their identity plane completely unprotected.

That gap is exactly what Entra Backup and Recovery targets. It's built into the admin center, it's automatic, and there's nothing to configure. For quick, in-place recovery, think "undo" for your tenant, it's a massive quality-of-life improvement.

Fig 1. The Backup and Recovery overview in the Microsoft Entra admin center, your starting point for backups, difference reports and recovery. Screenshots in this guide were captured during the public preview.

How Entra Backup Works: Daily Backups With 7-Day Retention

Microsoft backs up the supported objects in your tenant automatically, once a day, and keeps up to seven days of backup history. There's no toggle to flip, no agent to deploy and no storage account to wire up. You'll find it in the Microsoft Entra admin center under Backup and recovery.

Two properties make it more useful in an incident than a script you run yourself:

  • The backups are immutable. In Microsoft's words, "no signed-in user or application, even with the highest admin privileges, can turn off, delete, or modify backups in the tenant." An attacker who gets Global Administrator can damage your configuration, but can't destroy your recovery points.
  • The data stays in your tenant's geography. Backup data resides in the same geo-location as your Entra tenant.

To use it, the tenant must be a workforce tenant licensed for Microsoft Entra ID P1 or P2. External ID and Azure AD B2C tenants aren't supported, so customer identity tenants still need their own backup approach.

The supported object types cover the most critical identity and access configuration in your tenant:

Users · Groups · Applications · Service principals (with their OAuth2 permission grants and app role assignments) · Conditional Access policies · Named locations · Authentication methods policy · Authorization policy (selected properties) · Organization (tenant per-user MFA settings)

Microsoft Entra Agent ID objects are covered through their underlying directory object types. Recovery applies only to the supported properties of each object, so it's not a full object rollback. Microsoft lists the exact properties per object type in its supported objects and limitations article, and says that list expands over time.

Entra Difference Reports: Compare Tenant State Before Restoring a Backup

This is where the feature gets really interesting. Rather than forcing you to blindly restore a backup and hope for the best, Entra lets you generate a difference report that compares the current state of your tenant with a chosen backup.

The report shows exactly what changed: which objects were modified, which attributes differ, and which links (such as group memberships) were added or removed. You decide whether to recover, and what to target, with the evidence in front of you.

Fig 2. The backups list shows each daily backup. Select one and choose your scope to generate a difference report.

You can scope a difference report (and a recovery) three ways:

All supported objects: compares everything in scope against the backup. The broadest view.

Selected object types: narrow the report to the types you care about, such as Conditional Access policies or applications. In the admin center, service principals, OAuth2 permission grants and app role assignments are grouped under a single filter.

Specific object IDs: pinpoint individual objects by their object ID.

If you already know that one Conditional Access policy got mangled, you don't need a full-tenant comparison. Target it by ID, get your delta, and move on. Microsoft also notes that creating a difference report before recovering preloads the data, which shortens the recovery itself.

What's Inside an Entra Backup Difference Report: Attribute-Level Change Tracking

Once a difference report completes, you get a table of every object that has changed since the backup was taken. In our testing, each row showed the display name, object type, recovery action, how many attributes and links changed, and whether the object is synced from on-premises.

Fig 3. A completed difference report. Each row is a changed object. Drill into attribute-level differences, then recover individual items or the whole scope.

You can drill into each object to see exactly which properties changed and their before-and-after values. In our testing we found a Conditional Access policy whose grant control had been changed from compliantApplication to mfa, exactly the kind of subtle policy drift that goes unnoticed until something breaks.

Group membership changes also surface clearly. If a user was removed from a security group, the report shows the specific member delta, so you know precisely who was affected.

On-premises synced objects: changes to objects synced from on-premises Active Directory appear in difference reports, but (except for group memberships) they're automatically excluded from recovery. Those objects are mastered on-premises and should be fixed at source. And if a user or group was converted to cloud-managed after the backup was taken, recovering from that backup doesn't switch its source of authority back to on-premises.

Entra Tenant Recovery: Restore Objects, Object Types or the Full Scope

Once you've reviewed the difference report, you can recover all supported objects, selected object types or specific object IDs. Recovery puts the supported properties of those objects back to their state when the backup was taken.

How recovery treats objects that were created or deleted since the backup is worth understanding before an incident:

  • Objects created after the backup are soft-deleted, not destroyed. Microsoft never hard-deletes customer objects during recovery. Users, Microsoft 365 groups, cloud security groups, app registrations and service principals stay restorable from deleted items for 30 days, so a rollback that goes too far can be partly undone.
  • Soft-deleted objects are restored, not recreated. They come back with their original object IDs.
  • Hard-deleted objects can't be recovered or recreated. Only modified or soft-deleted objects are in reach.

There's no undo button for the attribute values recovery overwrites, which is exactly why the difference report comes first: inspect, then recover. The time a recovery takes depends mostly on how many changes it includes.

Afterwards, Recovery history lists completed and in-progress recovery operations: when they ran, what they covered and their status.

Entra Backup and Recovery Microsoft Graph API Endpoints

Backup and Recovery is exposed through the Microsoft Graph beta endpoint under the /directory/recovery/ namespace. Microsoft's beta APIs can change, so pin your tooling to the documentation rather than to this post. These are the calls we used:

# List backups (snapshots)
GET https://graph.microsoft.com/beta/directory/recovery/snapshots
 
# List difference report (preview) jobs
GET https://graph.microsoft.com/beta/directory/recovery/jobs?$filter=isof('microsoft.graph.entraRecoveryServices.recoveryPreviewJob')
 
# Get a specific job's details
GET https://graph.microsoft.com/beta/directory/recovery/jobs/{jobId}
 
# Get the changed objects from a difference report
GET https://graph.microsoft.com/beta/directory/recovery/snapshots/{snapshotId}/recoveryPreviewJobs/{jobId}/getChanges

The permissions are EntraBackup.Read.All for reading, EntraBackup.ReadWrite.Preview for difference reports and EntraBackup.ReadWrite.Recovery for recovery. Each changed object in a report includes its currentState and deltaFromCurrent, giving you the full before-and-after picture programmatically. You could build automated alerting on top of this: imagine a Logic App or Azure Function that runs a nightly difference report and posts to a Teams channel if anything unexpected changed.

One design constraint to plan around: only one difference report or recovery job can run in a tenant at a time. Schedule automated reports for quiet hours, so a routine job never sits in front of an urgent recovery.

New Entra RBAC Roles: Entra Backup Administrator and Entra Backup Reader

Microsoft introduced two built-in roles to govern access, which is exactly what you want to see from a least-privilege perspective:

RoleWhat it can doKey distinction
Entra Backup AdministratorEverything the Reader can do, plus create difference reports and trigger recoveryCan change your tenant
Entra Backup ReaderView backups, difference reports and recovery historyCan investigate, can't trigger recovery

All Entra Backup Administrator permissions are also included in the Global Administrator role. Give the Reader role to your security operations team so they can investigate without any risk of an accidental restore, and make Backup Administrator a PIM-eligible role held by a small group, not a standing assignment.

Native Entra Backup vs Third-Party Backup Tools: When the Built-In Service Is Enough

The obvious question at GA is whether native backup replaces a third-party identity backup product. It depends on how long you need to look back, what you need to restore, and what you need to prove to an auditor.

Native Entra Backup and RecoveryMicrosoft 365 Backup extension (roadmap)Third-party identity backup productsScripted configuration exports
Retention7 days, fixed30 days, rollingSet by the product and your licenceAs long as you keep the files
CoverageSupported properties of core directory objects and key tenant policiesEntra objects (detailed scope not yet published)Varies by productWhatever you script, usually configuration
RestoreIn place, in the same tenantPoint-in-time restore of Entra objectsVaries by product; some support restoring to another tenantYou build, maintain and test the restore
Hard-deleted objectsNot recoverableNot yet publishedVaries by productRecreate from the export, with new object IDs
Evidence beyond a weekNoUp to 30 daysYes, if retention allowsYes, if stored in version control
Protected from a compromised adminYes, backups are immutableNot yet publishedDepends on where the data lives and who can delete itDepends on where you store the exports
CostIncluded with Entra ID P1 or P2Not yet publishedSeparate licenceEngineering time
StatusGenerally available (30 June 2026)In development, GA planned December 2026AvailableAvailable

The built-in service is enough when your main risk is accidental change or an attack you'll detect within a week, your tenant is a workforce tenant on P1 or P2, and you don't need to produce configuration evidence older than seven days.

Add longer retention when your time-to-detect for identity changes is longer than a week, you need to recover hard-deleted objects, you must evidence your identity configuration over months for audit or regulation, or you run External ID or Azure AD B2C tenants, which native backup doesn't cover. Even then, keep the native service: it's immutable, it's free with your licence, and it's the fastest rollback you have.

How to Turn On Entra Backup and Test a Restore: A Checklist

There's nothing to switch on, but there's plenty to get ready before you need it. Run this once now and again every quarter:

  1. Confirm eligibility. Workforce tenant, licensed for Microsoft Entra ID P1 or P2.
  2. Check backups exist. In the Microsoft Entra admin center, open Backup and recovery and confirm you can see up to seven daily backups.
  3. Assign the roles. Entra Backup Reader for your security operations team; Entra Backup Administrator as a PIM-eligible role for a small group of identity administrators.
  4. Create a safe test object. A security group with no access attached, or a Conditional Access policy in report-only mode scoped to a test group. Wait for the next daily backup so it's captured.
  5. Change it. Rename it, change a membership, or change a grant control.
  6. Run a difference report scoped to that object ID. Confirm the attribute-level change appears.
  7. Recover that object only. Confirm the change is reverted, then check recovery history and your audit logs.
  8. Write it into your incident runbook. Who holds Backup Administrator, the seven-day window, the one-job-at-a-time limit, and the on-premises synced objects you'll need to fix in Active Directory instead.

Entra Backup Limitations: What It Won't Recover

This is a fantastic addition to the platform, but it's important to frame it accurately before you rely on it as your only safety net.

Seven days of history. If an attacker makes a subtle change that isn't detected within a week, or you need to compare against a known-good state from a month ago, this won't help.

No hard-deleted objects. Only modified or soft-deleted objects can be recovered.

Not every property is in scope. Manager and sponsor changes, group ownership changes, dynamic group rule changes and permission grants created through user consent aren't covered. Recovery restores only the supported properties of each object.

On-premises synced objects are excluded from recovery. Their changes (except group memberships) show up in difference reports, but you fix them in Active Directory.

One job at a time. Only one difference report or recovery job can run in a tenant at once, which can slow you down in a fast-moving incident.

Workforce tenants only. External ID and Azure AD B2C tenants aren't supported.

Where Entra Native Backup Fits in Your Identity Protection Strategy

Think of Entra Backup and Recovery as your first responder, the tool you reach for in the first five minutes of an incident when you need to revert a known bad change. Someone accidentally disabled a critical Conditional Access policy? Restore it in a couple of clicks. If you're finding out about policy drift from a backup diff, though, a Conditional Access review will tell you what else has quietly changed. A service principal's properties got modified during a compromised admin session? Pull up the diff, confirm the damage and roll it back, then work out how that principal accumulated its permissions in the first place with an application governance assessment.

It is not a replacement for a comprehensive identity backup strategy. Seven days is too short for compliance, long-term audit, or disaster recovery where the time to detection might be weeks or months. If you're in a regulated industry or managing a large, complex tenant, run a longer-retention backup alongside it, and keep a sound Active Directory backup for anything synced from on-premises. For what no backup can bring back, such as a hard-deleted app registration, keep your applications and tenant configuration defined as code, so recovery is a redeploy rather than a rebuild from memory. Native backup, configuration as code and drift monitoring together make a workable Entra ID disaster recovery plan.

For the vast majority of day-to-day "oops" moments and rapid-response incidents, though, this will save organisations enormous amounts of time, stress and support tickets. Because it's native, automatic and immutable, even organisations that never had any identity backup now have a safety net.

Final Thoughts: Entra Backup and Recovery at General Availability

Microsoft listened to the preview feedback. Retention went from five days to seven, licensing landed in Entra ID P1 and P2 rather than a separate SKU, and a 30-day extension is on the roadmap. The difference report workflow is still the standout, and immutable backups make it a genuine incident-response tool rather than a convenience.

Seven days is still the main limitation, so treat it as your fastest rollback, not your only backup. Then do the one thing most tenants haven't: run the test-restore checklist above before you need it. You might be surprised what the first difference report shows you.

Sources

Rawson Wade

Written by

Rawson Wade

Labs Lead, Modern 42

Rawson leads Modern 42's Labs team with deep expertise in Microsoft Entra ID and Azure identity platforms. He has delivered countless IAM and PAM implementations for Australian government and large enterprises.

Let’s talk about your identity platform

No pitch decks. No pressure. Just a straightforward conversation about your Entra ID environment, what’s working, and what needs to change.

  • Review your current Entra ID and identity architecture
  • Identify migration paths and modernisation opportunities
  • Get practical engineering guidance, no strings attached

Free 30 min discussion

No commitment required

Book a time that works for you. We’ll come prepared with initial observations about your identity platform and common engineering challenges.

We use cookies

We use cookies and similar technologies to help personalise content, measure the performance of our site, and provide a better experience. By clicking Accept, you consent to the use of all cookies.
Learn more.