# Intune Disaster Recovery Plan: Checklist | TenuVault

Build an Intune disaster recovery plan: a checklist for before, during and after an incident, recovery scenarios, keys and restore drills with TenuVault.

Canonical: https://www.tenuvault.com/intune-disaster-recovery

Practical guide

# Intune disaster recovery plan: a checklist for configuration recovery

An Intune disaster recovery plan prepares you for lost or changed policies, a compromised tenant, an unavailable admin computer and rebuilding configuration in another tenant. A usable plan combines configuration backups with keys, access, dependencies and an exercised procedure.

[Download for Windows](https://www.tenuvault.com/download/windows)[![Get it from Microsoft](https://www.tenuvault.com/_next/image?url=%2Fdesktop%2Fmicrosoft-store-badge.png&w=1920&q=75)](https://apps.microsoft.com/detail/xpfp6qq47l0gdk?cid=website-intro)

[Download for Mac](https://www.tenuvault.com/download/mac-arm64)

For Apple silicon Macs.Intel Mac? [Get the Intel build](https://www.tenuvault.com/download/mac-x64)

Free to download. Every new tenant starts with 14 days of Pro, with no card and no email. [Plans and features](https://www.tenuvault.com/pricing)

## At a glance

-   An Intune disaster recovery plan needs more than backups: recovery keys, admin access, a source for external artifacts such as app installers, and an exercised restore procedure.
-   Microsoft documents no recycle bin or restore path for deleted Intune policies; recovery means recreating configuration from a prior export or backup.
-   TenuVault backups on a device or network share can be read on another computer only with the recovery key, so store the key separately from the admin device. Backups in your own Azure storage can be read by anyone with data access to that storage account.
-   On TenuVault Pro and MSP, replace in place recreates deleted items under their original names with new IDs; MSP adds unassigned copies into another tenant when both tenants are on MSP.
-   Configuration recovery does not enroll or migrate devices. Line-of-business apps need their original installers, and so do Win32 apps unless App Backup captured them.

## Checklist: before an incident

Work through these items for every tenant you protect, and record the owner of each one in your recovery plan.

-   Schedule backups: weekly on Community, daily on Pro and MSP. Confirm that scheduled runs actually complete on the admin computer.
-   Save the recovery key in a password manager or another secure store, separate from the admin computer.
-   Keep backups off the admin device: an Azure storage account on Pro and MSP, or a network share for encrypted local backups.
-   Keep an independent copy of important backups: download the backup as a ZIP export and store it somewhere a storage administrator for the backup location cannot delete. ZIP exports are plain JSON and not encrypted, so protect them; TenuVault can import them later with Import backup ZIP. Copying older encrypted Azure backup files to another storage account does not work, because each of those files is bound to its storage account and path.
-   Open a recent backup in the restore wizard and review Recovery readiness. Record the items that need manual work.
-   Record where app installers and Apple tokens come from and who can renew them.
-   Keep the app registration, Intune roles and storage permissions documented and usable by more than one administrator.
-   Consider Intune Multi Admin Approval, which Microsoft describes as requiring "that a second administrative account approves a change before the change is applied".
-   Run a restore drill with Create copies and record the result.

-   [Microsoft Learn: Multi Admin Approval](https://learn.microsoft.com/en-us/intune/fundamentals/role-based-access-control/multi-admin-approval)
-   [Set up and verify a backup schedule](https://www.tenuvault.com/guides/intune-backup-setup)

## Checklist: during an incident

Restore only what you have reviewed. A fast restore of the wrong scope creates a second incident.

-   Find the cause first. Intune audit logs show who changed what; Microsoft states that you can "use Graph API to get two years of audit events". Remove compromised or unintended access before restoring.
-   Take a backup of the current state. Replace in place does not keep the versions it overwrites.
-   Pick the last backup from before the problem. Use View Changes or drift detection to see what changed between backups.
-   Select the affected items and restore their dependencies, such as scope tags, assignment filters and categories, in the same selection.
-   On Pro and MSP, decide on Restore assignments, and restore Windows Autopilot profiles, Apple user enrollment profiles, terms and conditions and Intune roles in a separate selection with assignments off. On Community, restore unassigned copies one at a time and assign them in Intune.
-   Check the labels on the Review step, confirm, and resolve incomplete objects and uncertain writes before retrying.

-   [Microsoft Learn: Intune audit logs](https://learn.microsoft.com/en-us/intune/governance/monitor-audit-logs)
-   [Intune drift detection](https://www.tenuvault.com/intune-drift-detection)

## Checklist: after an incident

Recovery is complete when configuration, assignments and external artifacts are back and the evidence is recorded, not when the restore wizard finishes.

-   Complete external artifacts: restore Win32 apps that App Backup captured, upload the installers of all other apps again and renew Apple tokens. For profiles whose backup holds a masked OMA-URI value, take a new backup while the profile still exists, or re-enter the secret in Intune.
-   Validate recovered settings and assignments, and account for new object IDs created by recreated items.
-   Review Intune role memberships so the restore did not reinstate access you revoked.
-   Observe device behavior separately. Assigned policies reach devices at their next check-in.
-   Run a fresh backup of the recovered state.
-   Record the timeline, the backup used, original and created IDs and manual steps. Update the plan and schedule the next drill.

## Recovery scenarios and recommended actions

Match the incident to a workflow before you start writing to Intune. Plan availability is enforced in the app.

| Scenario | Recommended action | Plan |
| --- | --- | --- |
| A deleted policy | Replace in place recreates it under its original name with a new ID; add Restore assignments if its targeting must come back. On Community, restore an unassigned copy and assign it yourself. | Replace in place on Pro and MSP; copies on all plans |
| A bad change to a policy | Run a backup, use drift detection to see the changed settings, then Revert or Replace in place. To inspect first, restore the old version as a copy. | Revert and replace on Pro and MSP; copies on all plans |
| Tenant compromise or mass deletion | Secure admin access first. Back up the current state, choose the last backup from before the incident and Replace in place with several items selected, adding Restore assignments where needed. Review Intune roles afterwards. | Pro and MSP |
| Lost or reinstalled admin computer | Install TenuVault, sign in with the same app registration and activate your license, deactivating the old installation in the customer portal if the installation limit is reached. Import the recovery key for local backups and point the tenant at the existing backup location. | All plans |
| Tenant migration | Copy selected items into the new connected tenant. Copies are unassigned with the Default scope tag; recreate groups and filters, enroll devices separately, and upload app installers unless App Backup holds the Win32 installer (a Pro or MSP restore into the new tenant). | MSP |

-   [How TenuVault backs up Intune](https://www.tenuvault.com/intune-backup)
-   [Restore Intune policies](https://www.tenuvault.com/intune-restore)

## Define the scope and recovery requirements

Inventory the Intune configuration you need to recover and the time and data-loss limits your organization expects. Map those requirements to backup frequency, retention and the people who can run recovery.

A configuration backup does not recover enrolled devices, endpoint files or every application artifact. Keep the coverage and limitations attached to the plan so the incident team knows what needs a separate procedure.

-   [Configuration backup coverage](https://docs.tenuvault.com/backups/coverage/)

## Keep files, keys and access recoverable

Document where backups are stored and how an authorized administrator can retrieve them if the usual computer is lost. Store the recovery key separately and verify the documented import procedure on an approved device.

Keep a usable app registration, admin roles and storage permissions available. Licensing checks, Microsoft authentication and network availability have their own requirements; offline verification does not make live tenant operations offline.

-   [Encryption and recovery key](https://docs.tenuvault.com/security/encryption/)
-   [Security and access model](https://www.tenuvault.com/trust)

## Review dependencies and external artifacts

Use recovery readiness to identify items that can be restored automatically, missing mappings and manual actions. Record installers, certificates and tokens that Microsoft Graph cannot export and define their separate recovery source.

For a configuration copy into another tenant, both tenants need MSP; an App Backup restore of a Win32 app needs Pro or MSP on the destination only, and a Pro trial counts. Check licensing, copy scope tags and assignment filters as dependencies, map apps and app categories, and plan to recreate group targeting. Cross-tenant copies remain unassigned until reviewed; restoring configuration does not enroll or migrate devices.

-   [Cross-tenant recovery](https://docs.tenuvault.com/restore/cross-tenant/)
-   [Manual artifacts and restore limits](https://docs.tenuvault.com/restore/limitations/)

## Exercise the plan and retain evidence

Start with a small unassigned policy-copy drill. If production recovery relies on replacement or assignment restoration, exercise those modes separately in an approved test scope.

Retain timestamps, app version, backup status, original and created IDs, setting comparisons and manual steps. Use the measured outcome to revise the plan; do not treat an export count as proof of full recovery.

-   [Run the restore drill](https://www.tenuvault.com/guides/intune-restore-drill)

## Recover, reconcile and validate

During an incident, select a verified backup, review the recovery plan and restore only the approved scope. Reconcile partial writes before repeating an operation.

Validate recovered settings and assignments, account for new object IDs and complete the external-artifact procedures. Observe intended endpoint behavior separately, then document remaining gaps and the next recovery test.

-   [Understand restore modes](https://www.tenuvault.com/intune-restore)

## Read the technical guides

-   [Detailed disaster recovery guide](https://docs.tenuvault.com/restore/disaster-recovery/)

Product scope reviewed 15 November 2026. Check your installed release and the current plan table before using a workflow.

## Frequently asked questions

### Q: What should an Intune disaster recovery plan include?

A: 

An Intune disaster recovery plan should include scheduled configuration backups, a recovery key stored away from the admin computer, documented admin access and storage permissions, a source for app installers and Apple tokens, recovery steps for each scenario and a restore drill whose result you have recorded. TenuVault covers the configuration backup and restore part, and its free App Backup can hold Win32 installers.

### Q: How often should I back up Intune configuration?

A: 

Choose the Intune backup frequency from how much configuration change your organization can afford to lose. TenuVault Community schedules weekly backups and Pro and MSP add daily backups. Desktop schedules need an awake computer with TenuVault running and a valid sign-in, so check that scheduled runs complete.

### Q: Can Microsoft support recover a deleted Intune policy?

A: 

Microsoft documents no recycle bin or support path to recover a deleted Intune policy. Intune audit logs show who changed what, but they record changed properties rather than the full policy, so recovery depends on an earlier export or a backup such as TenuVault.

### Q: What happens if I lose the computer that runs TenuVault?

A: 

Install TenuVault on another computer, sign in to the Intune tenant with the same app registration and activate your license; if the installation limit is reached, deactivate the old installation in the customer portal. Point the tenant at the existing backups in Azure storage or on a network share, importing your recovery key first for a network share. If the original computer is lost and you have no recovery key, nobody can decrypt the local backups, including TenuVault.

### Q: Can I rebuild Intune configuration in a new tenant?

A: 

Yes, with TenuVault MSP on both the source and the target tenant. It copies selected Intune items from a backup of one connected tenant into another; TenuVault checks the plan of every tenant involved before it writes anything. Copies are never assigned, so you recreate groups and filters and enroll devices separately in the new tenant. Win32 apps captured with App Backup can be restored there as new unassigned apps when the new tenant has Pro or MSP; every other app needs its installer uploaded again.

## Related guides

-   [What an Intune restore drill finds that a backup report never will](https://www.tenuvault.com/blog/what-an-intune-restore-drill-finds)

## Review your setup before the first change

Community is free for one tenant. Try Pro free by connecting a new tenant in the app, no email or card needed. Tenant access, supported restore types and scheduling requirements still apply.

[Download for Windows](https://www.tenuvault.com/download/windows)[![Get it from Microsoft](https://www.tenuvault.com/_next/image?url=%2Fdesktop%2Fmicrosoft-store-badge.png&w=1920&q=75)](https://apps.microsoft.com/detail/xpfp6qq47l0gdk?cid=website-guide-end)

[Download for Mac](https://www.tenuvault.com/download/mac-arm64)

For Apple silicon Macs.Intel Mac? [Get the Intel build](https://www.tenuvault.com/download/mac-x64)

[Start free trial](https://www.tenuvault.com/trial?src=cta)[Book a 30-minute demo](https://cal.com/ugur-koc/tenuvault-demo)[Permissions and data flows](https://www.tenuvault.com/trust)
