Skip to content

Microsoft Entra ID backup

Entra ID backup for the identities behind Microsoft 365

Every sign-in to Microsoft 365 runs through Entra ID. Mindtime backs up your users, groups, roles, administrative units, apps, Conditional Access and Intune policies, plus your audit and sign-in logs. Restore a whole object or one property from any restore point, from Dutch and German data centres.

Protects
Users · Groups · Roles · Apps · Policies
Logs
Audit · Sign-in
Restore
Object · Property · JSON export
Data centres
NL · DE

In short

What is Entra ID backup?

Entra ID backup is an independent copy of your Microsoft Entra ID tenant: the users, groups, roles, apps and policies that decide who can reach Microsoft 365 and Azure. Mindtime backs up the tenant on a schedule without installing agents. Every run creates a restore point. From any restore point you can restore whole objects, restore selected properties of one object, or export items as JSON.

What we back up
Users, groups, administrative units, roles, applications, service principals, Conditional Access policies and Intune policies, plus audit and sign-in logs
How often
Daily by default, or every few hours or minutes if your tenant changes often
How you restore
Full object restore, property restore after comparing versions, or JSON export
Where it is stored
Mindtime-owned infrastructure in the Netherlands and Germany, outside Microsoft

The risk

Why Entra ID needs its own backup

Entra ID is the front door to Microsoft 365. Lose a group, an app registration or a Conditional Access policy, and people lose access or attackers gain it. Microsoft's own safety nets are short and incomplete.

  1. 30 days

    The recycle bin is narrow

    Only eight object types are soft-deleted, including users, groups, applications, administrative units and Conditional Access policies. They stay in the recycle bin for 30 days, then they are gone for good.

  2. Hard delete

    Everything else is gone at once

    Microsoft states that every other object type is hard-deleted. Changed properties, such as a removed group member or an edited policy, never reach the recycle bin at all.

  3. 7 days

    Native snapshots are short

    Microsoft Entra Backup and Recovery keeps daily snapshots inside the same tenant: seven days on the standard plan with Entra ID P1 or P2, 30 days on the Premium plan, which is in preview. A change you spot after that can't be rolled back that way.

What's covered

What can you back up in Entra ID?

Eight item types, each with its own set of protected properties. Contacts and devices are kept as well, so you can export their details.

  • Identities

    Users

    • 42 user properties, from name and job title to licences and usage location
    • Manager, direct reports and group memberships
    • On-premises sync attributes for hybrid users
    • Role assignments (Entra ID P2 or Governance)
  • Identities

    Groups

    • Members and owners
    • Dynamic membership rules
    • Assigned licences
    • Type, visibility and classification
  • Administration

    Roles and administrative units

    • Custom role definitions and their permissions
    • Role assignments to users and groups
    • Administrative units and their members
    • Scoped directory role members
  • Access

    Apps and service principals

    • App registrations: API settings, app roles, redirect URIs, owners
    • Federated identity credentials and optional claims
    • Enterprise apps: SSO settings, permission grants, app role assignments
  • Access

    Conditional Access

    • Conditions: users, apps, locations, platforms
    • Grant controls, such as MFA or a compliant device
    • Session controls
    • Policy state: on, off or report-only
  • Devices

    Intune policies

    • Device configuration and compliance settings
    • Defender, BitLocker and firewall settings
    • Windows Update rings and passcode rules
    • Policy assignments

How backup works

From connected tenant to restore points

No agents and no change to how your team signs in. The backup reads your tenant through Microsoft's own APIs and our team sets it up with you.

  1. 01

    Connect your tenant

    We connect through an Entra app registration. Backup uses read permissions in Microsoft Graph. Restore runs only when an admin from your tenant signs in.

  2. 02

    Set the protection scope

    By default the scope covers users, groups, administrative units, roles, applications, Conditional Access policies, Intune policies and logs. Optional item types can be left out.

  3. 03

    Schedule and retain

    The backup runs daily, every few hours or minutes, or back to back. Each run creates a restore point, kept for the number of days you choose. Failed items are retried automatically.

  4. 04

    Keep a second copy

    Backups can be copied to a second location with their own retention and their own encryption password, so one lost copy doesn't mean lost history.

How restore works

Restore exactly what changed

Pick a restore point, see what is different from your tenant today and put back only what you need. Every restore is logged with the reason you give for it.

  • Full object restore

    Restore one or more items of the same type, up to 1,000 per restore, from the latest or any earlier restore point. Existing items with the same object ID are overwritten, or you can choose to skip them.

  • Compare, then restore properties

    See each property side by side in the chosen restore point, the latest restore point and your live tenant, filtered to what changed. Then restore only the properties you pick.

  • Relationships come back too

    Group memberships and ownerships, role assignments, administrative unit memberships and manager links are restored with the item, as they were at that restore point.

  • Object IDs kept where possible

    If a deleted user, group or app is still in the Entra ID recycle bin, it is restored from there and keeps its object ID. Otherwise it is rebuilt from the backup.

  • Safe sign-in after restore

    Passwords are never restored. Restored users get a temporary password, set once for all or per user, and have to change it at first sign-in.

  • Hybrid users and JSON export

    Users synced from Active Directory can be restored with their Entra ID relationships. Any item, including contacts and devices, can also be exported as JSON with its permissions and memberships.

Audit and sign-in logs

Keep Entra ID logs longer than Microsoft does

Microsoft keeps Entra ID audit and sign-in logs for 7 days on the free tier and 30 days with P1 or P2. A log backup keeps them for as long as your investigations, audits or NIS2 evidence need.

  • Retention

    Days, months or years

    • Audit logs and sign-in logs in one backup
    • Retention set in days, months or years
    • A second copy with its own retention
  • Integrity

    Checked and encrypted

    • Compression and password-based encryption
    • Scheduled health checks that verify every restore point
    • Damaged blocks are copied again in the next run
  • Restore

    Logs when you need them

    • Restore the latest logs or an earlier point in time
    • Delivered to a file share for your auditor or SOC
    • Sign-in logs need Entra ID P1 or P2

Good to know

What Entra ID backup doesn't cover

A few items are limited by how Microsoft Entra ID works. Knowing them up front keeps a restore free of surprises.

  • Not restored

    Microsoft-owned and mail objects

    • Built-in Entra ID roles, which Microsoft manages
    • Distribution groups and mail-enabled security groups
    • Contacts and devices: export only
  • Do by hand

    App certificates

    • App certificates aren't backed up, because of Microsoft throttling limits
    • Keep a copy of your certificates, or create new ones after a restore
    • Restore apps together with their service principals
  • Not supported

    Special tenants

    • Tenants in China and Azure Government tenants
    • External tenants and Azure AD B2C tenants
    • Conditional Access policies are restored without relationships

The difference

Entra ID recycle bin vs. an independent backup

Microsoft's tools are a useful first line. An independent backup is the copy you still have when they run out.

Microsoft native Entra ID recovery vs. Mindtime Entra ID backup
CapabilityMicrosoft nativeMindtime Entra ID backup
Where the copy livesInside the same Microsoft tenantSeparate, on Mindtime-owned infrastructure in NL and DE
Deleted objectsRecycle bin for 8 object types, 30 daysAll 8 protected item types, for as long as your retention says
Hard-deleted objectsCan't be recoveredRestored from the backup, with their relationships
Changed settingsDaily snapshots, 7 days (P1 or P2) or 30 days (Premium, preview)Compare versions and restore single properties from any restore point
Audit and sign-in logsKept 7 days (Free) or 30 days (P1 and P2)Kept for days, months or years, with a second copy

FAQ

Common questions about Entra ID backup

Does Microsoft back up Entra ID?

Only partly, and only inside your own tenant. Eight object types, including users, groups, applications, administrative units and Conditional Access policies, stay in the Entra ID recycle bin for 30 days after deletion. Other object types are hard-deleted straight away. Microsoft Entra Backup and Recovery adds daily snapshots, but keeps seven days of history on the standard plan (Entra ID P1 or P2) and 30 days on the Premium plan, which is in preview. An independent backup keeps your own history, outside Microsoft.

What exactly is backed up in Entra ID?

Eight item types: users, groups, administrative units, roles, applications, service principals, Conditional Access policies and Intune policies. Each is backed up with a fixed set of properties, for example 42 properties per user, including licences, manager and group memberships. Audit and sign-in logs are backed up in a separate log backup. Contacts and devices are kept for export only.

How often is Entra ID backed up?

Daily by default. If your tenant changes often, the backup can run every few hours, every few minutes or back to back. Every run creates a restore point, which is kept for the number of days you choose. Items that fail are retried automatically.

Can I restore a single property, such as a group membership?

Yes. Choose an item and a restore point, and you see each property side by side in that restore point, the latest restore point and your live tenant. By default only changed properties are shown. You then restore just the properties you select, for one item at a time.

Are group memberships and role assignments restored with a user?

Yes. When you restore an item, its relationships are restored as they were at that restore point. For users this covers group memberships and ownerships, role assignments, administrative unit memberships, app ownerships, manager and direct reports. Relationships are only restored to items that still exist in your tenant. Conditional Access policies are restored without relationships.

Are user passwords restored?

No. Passwords are never part of the backup. Restored users get a new temporary password, either one for everyone or a separate or generated one per user, and have to change it when they first sign in.

Can Conditional Access policies be restored?

Yes. Whole policies and individual settings, such as conditions, grant controls, session controls and state, can be restored to your tenant. The admin account used for the restore needs the Conditional Access Administrator role, or Global Administrator together with Conditional Access Administrator or Security Administrator.

Can hybrid users synced from Active Directory be restored?

Yes. A synced user is restored to Entra ID with a new object ID and with its Entra ID relationships, such as group memberships, roles and licences. After the next sync with Microsoft Entra Connect, the user becomes a hybrid identity again. If the user was also deleted from Active Directory, it has to be restored there as well.

What can't be restored?

Built-in Entra ID roles, distribution groups and mail-enabled security groups can't be restored. Contacts and devices can be exported as JSON but not restored. App certificates aren't backed up, so keep a copy or create new ones after a restore. Tenants in China, Azure Government tenants, external tenants and Azure AD B2C tenants aren't supported.

Do we need Entra ID P1 or P2?

Not for the tenant backup itself. Sign-in logs can only be backed up with Entra ID P1 or P2, and role assignments of users are protected with Entra ID P2 or Governance licences. Without them, the rest of the tenant and the audit logs are still backed up.

Does Entra ID backup replace Microsoft 365 backup?

No, they protect different layers. Microsoft 365 backup protects the data in Exchange, SharePoint, OneDrive and Teams. Entra ID backup protects the identities, groups, apps and policies that decide who can reach that data. Most organisations need both.

Sources

  1. Recover from deletions in Microsoft Entra IDMicrosoft Learn, 2026
  2. Microsoft Entra Backup and Recovery overviewMicrosoft Learn, 2026
  3. Microsoft Entra data retentionMicrosoft Learn, 2026