Admin: Tenant Backup / Restore
Tenant Backup provides export and restore capabilities for core tenant configuration so administrators can protect configuration state, validate changes safely, and recover from operator mistakes.
What Is Included In Backup Payload
Backups are focused on tenant configuration and governance data used by platform features.
• Applications (including metadata, configuration, owners, and group memberships)
• Automation Tasks (task definitions, steps, parameter links, and runtime settings)
• Groups (members, application memberships, and integration memberships)
• Integrations (including AWS/Vercel metadata where configured)
• Site Settings (access checks, licensing, notification and governance settings)
Backup Configuration
Configure a storage account + container before scheduling recurring backups. Backup location is saved as tenant settings and reused by scheduled jobs.
1. Select a storage account from discovered tenant storage resources
2. Select a blob container used for backup files
3. Save backup configuration to persist account/container binding
4. Verify latest backup listing resolves from selected location
Scheduling Backups
Scheduled backups are configured by linking backup settings to an existing schedule. Once linked, scheduler services execute backup creation automatically on schedule runs.
1. Save backup location first
2. Select target schedule from available schedule list
3. Save backup schedule link
4. Remove link when schedule should no longer create backups
Restore Options And Safety Workflow
• Restore source: blob storage selection or local JSON file upload
• Dry-run restore: validate payload compatibility and surface warnings before commit
• Confirmed restore: apply backup payload into tenant configuration state
• Warning review: resolve surfaced warnings before production restore where possible
If you encounter any issues or need further assistance, please contact us at
info@azexecute.com. Our support team is here to help you.