Azure VM Backup Not Enabled
There is nothing to restore from, so a deletion, a ransomware event or a corrupted disk is unrecoverable.
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 VM.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Virtual Machines on Azure
- The fix, by hand
- VM → Operations → Backup.
- Select or create a Recovery Services vault in the same region.
- Pick a backup policy. Daily at off-peak hours is the default; tune retention (e.g. 30 days operational, 12 monthly, 5 yearly) per compliance.
- Click Enable backup; trigger an initial backup via Backup now and wait for it to complete (first backup is a full copy and can take hours).
- Validate restore by mounting a recovery point via File Recovery once, end-to-end.
- Set a Monitor alert on backup job failures so silent regressions are caught.
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-267- 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.