Share via

EntraID backup and SG

Concerned citizen 0 Reputation points
2025-07-02T13:27:13.29+00:00

What is the best way to airgap entraID user and security group backups? I have looked at third party vendors and have yet to find one that can do a restore in the event you lose a tenant all together and have to rebuild from scratch

Azure
Azure

A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Chiugo Okpala 1,925 Reputation points MVP
    2025-07-02T20:34:52.5466667+00:00

    @Concerned citizen welcome to the Microsoft Q&A community.

    Airgapping Entra ID (formerly Azure AD) user and security group (SG) backups is critical for protecting against ransomware, malicious deletions, and tenant-wide disasters. However, you're absolutely right: restoring an entire tenant from scratch—including users and groups—is not natively supported in full fidelity by Microsoft or by most third-party tools due to how Entra ID is designed as a cloud-native identity provider.

    The Core Problem

    Entra ID does not provide:

    A native backup/restore capability that covers users, groups, roles, and configurations in a fully restorable format.

    A way to export and re-import all users/SGs/roles/configs in a way that fully preserves original metadata (e.g., object IDs, group memberships, conditional access policies, app assignments).

    Thus, airgapping Entra ID backups and ensuring disaster recovery (DR) is a layered approach.

    Best Practices for Airgapping Entra ID Backups

      1. Periodic Offline Export of Directory Data
      You can script and schedule exports of key objects using Microsoft Graph API and store the results in an airgapped environment (offline vault, secure storage, or physically disconnected systems). Key items to export:
      • Users and their attributes
      • Security and M365 groups (including members)
      • Conditional Access policies
      • Role assignments (e.g., Global Admins)
      • Application registrations and Service Principals
      Tools/Methods:
      • PowerShell + Graph API scripts
      • Azure Automation jobs to export regularly
      • Store results as JSON/CSV in secure, immutable storage (e.g., AWS Glacier, on-prem tape, or encrypted drives)

    Example script source: Microsoft Graph PowerShell SDK


    1. Use of Third-Party SaaS Backup Solutions

    While most third-party tools don't support full tenant rehydration, some provide partial protection:

    Vendor Notes
    HYCU for M365 Backs up Entra ID users and M365 groups
    HYCU for M365 Backs up Entra ID users and M365 groups
    AvePoint Can export user data, configs, policies; partial restore possible
    Quest On Demand Recovery One of the best for granular AD object backup/restore
    SkyKick Focuses more on mailboxes, less on Entra ID itself
    Veeam Backup for M365 No full Entra ID restore, but good for Exchange/OneDrive/Teams content

    ⚠️ Most vendors do not support complete re-creation of a deleted Entra ID tenant. Object IDs change on restore, causing downstream issues with app and role bindings.


    1. Immutable, Versioned Storage

    Exported backup files (from Graph or third-party tools) should be stored:

    • In immutable blob storage (e.g., Azure Immutable Blob, S3 Object Lock)
    • In airgapped, offline, or physically separate vaults
    • With versioning and tamper detection enabled
    1. Documentation and Terraform/Bicep for Reprovisioning

    Use Infrastructure as Code (IaC) to document and recreate:

    Entra ID custom domain config

    Conditional Access Policies

    Enterprise Applications

    Permissions and role assignments

    You can't fully export/import Entra ID, but you can script its structure for rebuild.


    1. DR Playbooks and Manual Reconstruction Planning

    Since no solution offers full restore:

    Maintain a disaster recovery runbook that includes:

    Recreating the tenant (new domain, domain validation)

      Redeploying exported users/groups via script
      
         Reapplying roles, policies, and apps
         
            Rebinding services to the new Entra ID tenant
            
    

    Run periodic tabletop exercises simulating a full tenant loss to assess readiness.

    Airgapping Strategy Summary

    Strategy Purpose Airgap Level
    Scheduled Graph API exports Backup users/groups/config Medium (requires secure storage)
    Scheduled Graph API exports Backup users/groups/config Medium (requires secure storage)
    Immutable blob storage Protect against ransomware High
    IaC templates (Terraform/Bicep) Recreate policy structure Medium
    DR Playbooks Human recovery aid High
    Third-party tools Partial restore automation Low to Medium

    What You Cannot Do Today

    Fully restore an Entra ID tenant to a previous state

    Preserve object IDs on restore (which affects apps and access)

    Offline cold backup of the entire Entra ID tenant with built-in Microsoft tools


    Final Thoughts

    The "airgap" for Entra ID backups is largely manual and hybrid: automation to export, security to store safely, and documentation to rebuild. Unfortunately, Microsoft does not currently provide a tenant-level snapshot/restore capability, and no third party offers full restore at that level.

    If you're protecting high-value assets, combining secure exports with comprehensive DR plans and immutable storage is your best line of defense.

    N/B: I have generated the above answer using co-pilot as an AI tool. Also I have validated and updated the AI output.

    I hope these helps. Let me know if you have any further questions or need additional assistance.

    Also if these answers your query, do click the "Upvote" and click "Accept the answer" of which might be beneficial to other community members reading this thread.

    User's image

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.