Practical guide
How to back up and restore Intune policies
Use this checklist before relying on an automatic schedule. It covers authentication, storage, the first backup and a restore drill. Follow your organization's normal approval process for app registration and tenant access.
Also for Mac: Apple silicon · Intel
For Apple silicon Macs.Intel Mac? Get the Intel build
Also for Windows: direct download · Microsoft Store
Send yourself the link and install TenuVault on your computer.
Windows: direct download · Microsoft Store
Mac: Apple silicon · Intel
For Apple silicon Macs.Intel Mac? Get the Intel build
Free to download. Every new tenant starts with 14 days of Pro, with no card and no email. Plans and features
1. Install and prepare tenant access
Download the stable Windows or macOS installer for your architecture. Review operating-system and network requirements, then have an authorized administrator run the setup script to create the single-tenant public client app registration and grant the documented delegated permissions.
Sign in with the admin account that will run the backups. Its Intune roles determine what configuration it can read. For Azure storage, grant the required storage access separately.
2. Choose storage and save the recovery key
Choose encrypted local storage on Community, Pro or MSP, and save the recovery key somewhere separate from the admin device before relying on it. Pro and MSP can use your Azure storage account instead; those backups are protected by Azure encryption at rest and the account's access control, not by the recovery key.
Record the storage location, the person responsible for the key and the retention policy. A backup on a lost computer is not a complete recovery strategy unless you can retrieve the files and key from another location.
3. Run and review a manual backup
Run a backup with the scope you intend to protect. Inspect its result, log, item types and counts. Investigate access-denied types and exclusions, and confirm that the policies you intend to recover are present.
Make a small unassigned test policy if your organization permits it and practice restoring it as a copy. Record the result rather than assuming that a completed export proves every recovery path.
4. Configure and observe the schedule
Community supports a weekly schedule. Pro and MSP also support daily schedules and custom retention. A schedule runs in one of two places: in the TenuVault app on an admin's computer, or on Pro and MSP as cloud backups in an Azure Automation runbook in your own subscription, so no computer has to be on or signed in.
For schedules on a computer, keep TenuVault running in the tray, arrange startup where appropriate and make sure the computer is awake at the scheduled time. Desktop backups need a usable sign-in session, so under a strict Conditional Access sign-in frequency use Backup Reader (Pro and MSP) or cloud backups. Observe an actual scheduled run and inspect its status, and test your procedure after a restart, a sign-in expiry and a missed scheduled slot.
5. Keep an operational record
Record the app version, backup timestamp, scope, result, storage location and restore-drill outcome in your change system. Assign someone to check failures and key availability.
Repeat the drill after meaningful app, tenant, storage or authentication changes. Choose backup frequency and retention from your recovery requirements, then verify that your operating procedure meets them.
6. Restore a saved policy and verify it
Open Backup History and select a recovery point that contains the policy you need. Restore an unassigned copy first and inspect its settings. Pro and MSP also offer replacement of supported existing items and recovery of saved assignments.
For a deleted policy, recreation produces a different object ID. For an unwanted edit, choose a backup from before the change and review the replacement before applying it. Check targeting and test the result on a small device group.
Read the technical guides
Product scope reviewed . Check your installed release and the current plan table before using a workflow.
