Skip to content
Community+Governance

Backup & Restore

Back up your Atlas configuration and restore just the parts you need.

Backup & Restore protects the configuration you have built in Atlas AVD. Choose what goes into a backup (tenants, settings, host pools, deployments, Fortify, optimizations, automations, audit logs, activity and alerts, and Vault metadata), protect it with a password if you like, and download it. Restore from your history or from a downloaded file, choosing only the parts you want back, and preview a dry-run plan first if you like. Platform administrators can also run backups automatically every 1 to 24 hours.

Atlas AVD screenshot. All names, metrics and values are demo data.

The problem Backup & Restore solves

Over months an Atlas deployment collects work that is slow to rebuild: host pool settings, autoscale and reimage schedules, alert thresholds, Group Policy baselines, integration settings and who holds which role in each tenant. One bad bulk edit or a deleted tenant can undo that work in a minute.

Azure backs up the Atlas database, but a point-in-time restore brings back the whole server, not the one tenant or the one area you need. Auditors ask for something else again: a verifiable copy of your configuration and audit history from a given day.

Key capabilities

Choose the modules each backup includes, from host pools and settings to audit logs and alerts
Optional password encryption with AES-256-GCM; Atlas cannot recover the password
Vault secrets stay in your Key Vault: backups carry only redacted Vault metadata
Checksum and integrity check for every backup, and a download you can keep
Selective restore: host pool configuration, ADMX templates, integrations, alerts, automations, or users and roles
An optional dry-run preview of what a restore will change
Automatic backups every 1 to 24 hours; stored copies are deleted after 24 hours, except the newest good backup, so download the ones you want to keep

How Backup & Restore works

  1. 1Open Administration → Platform → Backup & Restore
  2. 2Choose the modules to include and, optionally, a password
  3. 3Generate the backup and download it
  4. 4To restore, pick a backup from your history or upload a file, choose the parts to restore and, optionally, preview the plan

What goes into a backup

Backup & Restore is under Administration → Platform in the sidebar and is for administrators. Under Generate backup, keep Scope on Current tenant only (All tenants is for platform administrators) and tick the Included modules: Tenants, Settings, Host pools, Deployments, Fortify, Optimizations, Automations, Audit logs, Activity & alerts, and Vault (redacted). Turn on Encrypt with password to protect the file with AES-256-GCM. The password needs at least 8 characters, and Atlas cannot recover it.

Click Generate backup to follow a progress bar and live log, then Download backup to save the .atlasbackup file. The file records a SHA-256 checksum for every entry, and Copy checksum gives you a fingerprint to keep with it. Secrets stay in Key Vault: integration credentials and Vault entries are written as references, never as values.

Stored backups are deleted 24 hours after they are created, so download any you want to keep. The newest successful backup is the exception: Atlas keeps it until a newer one succeeds, so a run of failed scheduled backups never leaves you with nothing to restore. Platform administrators also get an Automatic backups card: turn on Run backups automatically and set Hours between backups, from 1 to 24. The cap matches the 24-hour retention, so a restorable backup is always on hand. A failed backup raises a Backup failed alert, which closes after the next successful one.

How a restore works

Under Restore from backup, pick a backup From history, or choose Upload file and drop in a .atlasbackup file with its password if it is encrypted. Leave every Restore scope box clear to restore everything, or tick only what you need: Host pool configuration, ADMX / Group Policy baselines, Integration credentials & settings, Alert thresholds & notifications, Automations & schedules, or User & RBAC assignments. Preview (dry-run) shows how many rows would be written and how many would overwrite existing data before you click Restore and confirm.

Atlas re-checks every file's checksum before it writes anything, and warns you if the backup failed its health check. Matching rows are overwritten and rows that are not in the backup are left alone, while audit and activity history is only ever added back, never rewritten. A backup restores into the tenant it was taken from. If that tenant has been deleted, Atlas adds it back first, from Recently deleted when it is still there. Vault entries are never restored.

How to set up Backup & Restore

  1. 1In the sidebar, open Administration → Platform → Backup & Restore.
  2. 2Under Generate backup, keep the modules you need and turn on Encrypt with password.
  3. 3Click Generate backup, then Download backup, and store the file and its checksum somewhere safe.
  4. 4If you are a platform administrator, turn on Run backups automatically and set Hours between backups.
  5. 5Pick a backup under Restore from backup and run Preview (dry-run) to see what a restore would change.

Backup & Restore: frequently asked questions

Does a restore bring back deleted VMs or host pools in Azure?

No. Backup & Restore covers the data Atlas keeps about your environment: settings, schedules, thresholds, roles and history. It does not create, change or delete Azure resources. Protect session host VMs with Azure Backup; a VM's page in Atlas shows its Azure Backup status.

Can I keep backups longer than 24 hours?

Not inside Atlas: stored backups are deleted 24 hours after they are created, except the newest successful backup, which stays until a newer one succeeds. That period is fixed. Download the .atlasbackup file and keep it in your own storage for as long as your policy requires, then restore it later with Upload file.

Are secrets included in a backup?

No. Integration credentials and Vault entries stay in your Azure Key Vault, and the backup holds only references to them. A restore keeps the secrets already in place, and a tenant added back from a backup needs its client secret entered again.

Can I restore one tenant's backup into a different tenant?

No. A backup always restores into the tenant it was taken from, so one customer's data can never overwrite another's. If that tenant has been deleted, the restore adds it back first, which needs permission to manage tenants and room on your licensed tenant count.

Can I undo a restore?

No. Rows in both the backup and the live tenant take the backup's values, and that cannot be reversed. Run Preview (dry-run) first, and take a fresh backup just before restoring so you have a way back.

How is this different from the Azure database backup?

Azure backs up the Atlas database in your subscription automatically, for 7 days by default and up to 35, and restores the whole server to a point in time from the Azure portal. Backup & Restore works per tenant and per module, with a file you keep.

Which plan includes Backup & Restore?

Every plan, including Community. It is an administrator tool, and only platform administrators can back up all tenants at once or set up automatic backups.

Available on

Community plan and above

Backup & Restore is included in every Community subscription.