Azure Managed Disk Without Backup
There is no restore point, so a deletion or a corruption of this disk is permanent.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable backup on the managed disk.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Managed Disks on Azure
- The fix, by hand
- Open Business Continuity Center (formerly Backup center, removed from portal global search in Sep 2024) → +Configure backup.
- Datasource type = Azure Disks; vault = a Backup vault (not Recovery Services vault) in the same region.
- Attach a backup policy with a daily snapshot frequency and retention matching your RPO (e.g. 7 daily / 4 weekly).
- Select the resource as the disk to protect; submit.
- Validate initial snapshot succeeds via the vault's Backup items blade.
- Optionally, layer Azure Automation runbooks for ad-hoc snapshot capture before risky maintenance windows.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1327- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.