Backup & Restore and Demo Data

Permissions: backup.manage, demo.manage

Purpose

App routes: /admin/backup, /admin/demodata

Prerequisites and data sources

Tabs and actions

Freshness and scope behavior

Workflow overview

Backup & Restore

The backup screen enumerates available sections by tier, such as configuration, operational data, references, and credentials. Select explicitly, download the archive, and store it under organizational controls. The normal whole-tenant configuration export is designed to be secret-free/masked unless the UI explicitly offers a protected secret tier with clear warnings.

Backup export sections and secret-redaction guidance
Backup export sections and secret-redaction guidance. Review configuration, operational data, reference sets, and credential sections before exporting. The captured catalog marks secrets as redacted; no archive was downloaded or uploaded, and no restore preview or restore was run. Synthetic example data; names, identifiers and measurements do not describe a live tenant. View full-size screenshot.

For restore, upload the archive, validate/preview it, select sections, and choose the offered conflict mode: merge, overwrite, or skip. Restore does not prove external credentials remain valid; re-enter and test masked/excluded secrets. Verify tenant identity before import and take a current backup first.

Demo Data

Demo Data loads synthetic records for exploring features without touching Azure. The screen shows status and provides seed/reset or purge actions. Demo connectors are disabled and use non-functional placeholders. Purge removes demo-marked records and is irreversible; inspect the confirmation and avoid mixing demo output into real reports.

Loaded demo-data scope and removal guidance
Loaded demo-data scope and removal guidance. The status describes synthetic records already seeded in the isolated local instance, not live Azure discovery. Load and Remove were not clicked during capture; review the demo-only removal scope before any later cleanup. Synthetic example data; names, identifiers and measurements do not describe a live tenant. View full-size screenshot.

Interpretation of results

Exports, history, scheduling, and integrations

No dedicated export, history, scheduling, or integration controls are documented for this feature page.

Safety and limitations

Troubleshooting

Verification

After restore or demo changes, validate workload counts, references, automation targets, connector disabled/status state, access roles, and Audit Log. Do not assume imported schedules or external destinations are safe to enable in a new environment.

Back to top

Azure Support Agent is open source under the MIT License.

This site uses Just the Docs, a documentation theme for Jekyll.