Backup
Create backups from selected source resources and validate completion with toast and status updates.
Go to Backup from the top navigation. Use 'Connect to Azure' if your account is not connected yet. Select the source subscription and source resource group. Review the discovered resources list and keep only resources you want included. Choose ARM or Bicep template format. Enter an optional friendly backup name for easier identification later. Select Backup and monitor live stage/progress updates. On success, confirm the green success toast and use quick actions to Restore or Download logs. Open Backups and confirm the new backup appears with expected source details. Restore
Run restores safely with prechecks, optional destructive cleanup, conflict handling, and rich status visibility.
Open Backups. For the backup you want, select Restore. On the Restore page, choose the target subscription and target resource group. Review Resources to restore and adjust parameter values where needed. If rename conflicts are detected, provide valid new names for affected resources. Select Apply name changes and validate. After successful validation, continue with restore and confirm mapping details. Track progress in Restore status, including human-readable stage badges, elapsed time, and per-resource rows. Review resource status badges and expand Error details to capture specific failure text. Use restore toasts for real-time success/error feedback while keeping inline banners visible. When complete, return to Backups to review the latest restore result. Backups (history, failure analysis, logs)
Review restore attempt history with stage, duration, and detailed event timelines per attempt.
Use the History action to expand restore attempts for a backup. For failed attempts, use Failure details to inspect the stage and error summary. Use Details to inspect the full event timeline and per-resource operation outcomes. Use the Log download action in the backup row to export backup logs. Use rename and remove actions to manage backup records safely. Settings
Configure defaults that drive backup naming, retention, restore behavior, retry handling, and conflict resolution.
Backup settings
Backup folder path: local path where backup artifacts are written in local/dev mode. Template format: default backup export format (ARM or Bicep). Default backup naming pattern: controls generated backup names using tokens like {env}, {rg}, {sub}, and {yyyyMMdd-HHmm}. Environment token value: value used for {env} in generated names (for example dev, test, prod). Retention - Keep last N backups: keeps only the newest N backups (0 disables this rule). Retention - Delete backups older than X days: deletes backups older than the configured age (0 disables this rule). Default backup subscription and resource group: pre-populates Backup target selectors. Restore settings
Restore defaults - Stop on failure: stops restore when the first operation fails. Restore environment/configuration/connection string settings: controls which app/runtime settings are replayed during restore. Restore RBAC role assignments: replays supported role assignments captured during backup. Default restore subscription and resource group: pre-populates Restore target selectors. Delete target resource before restore: destructive option that removes existing resources in the selected target resource group before restore. Retry attempts/base retry delay/max parallel operations: controls resilience and throughput of restore execution. Auto resolve naming conflicts, suffix, and random-number option: automatically generates unique names for globally-unique resource types before deployment. Save settings to apply defaults; success/failure feedback appears in toast notifications. Troubleshooting
Use these checks to diagnose and resolve common restore and backup issues.
Confirm you are signed into the correct Azure account and tenant. Verify the target subscription and resource group exist and are selected. Ensure renamed resources exist when replaying scoped RBAC roles. Check failure details and exported logs for failing scope and principal. If needed, contact support from Contact Us and include backup ID, attempt time, and failure text. 
