Manage Infrastructure on Azure Stack Hub
Operations and health
Infrastructure management covers health monitoring, updates, backup, capacity, and diagnostics. The administrator portal surfaces alerts, region health, and update status. Understand update packages (full vs express), the update runbook, and the requirement to check prerequisites and apply OEM firmware through the OEM tooling.
Know infrastructure backup: it backs up the stamp's control-plane data to an SMB share, requires an external certificate, and is separate from tenant data backup. Capacity views show storage, compute, and memory usage; monitor storage rebalancing and alert remediation.
Traps to watch
- Infrastructure backup does not back up tenant workloads.
- Updates require healthy alerts cleared and may need OEM firmware first.
- Diagnostics logs (support logs) are collected via the PEP or admin tools; they are not the same as backup.
- Region health vs service health distinctions.
- Time sync and certificate expiry are common causes of failures.
Rule of thumb
Before any update or restore, clear active alerts, verify backup is current, and confirm certificates and time sync are healthy. If a question mentions "restore," the answer is the infrastructure backup plus OEM recovery steps.
Worked example
An update fails prerequisites. Check active alerts, confirm OEM firmware is current, verify the infrastructure backup completed, and validate certificate and time sync health before retrying the update.