Azure VM Using Unmanaged Disks
Unmanaged disks are the retired storage model and lack the availability, encryption and backup behavior managed disks provide.
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: Migrate the VM to managed disks.
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
- URGENT. Unmanaged (page-blob) disks were retired on 2026-03-31; affected VMs can no longer be started. This migration is mandatory.
- Stop and deallocate the resource.
- VM → Disks → Migrate to managed disks → review the plan → Migrate.
- Start the VM and run application smoke tests.
- Once verified, delete the orphaned VHD blobs and the source storage account to stop residual storage cost.
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-1307- 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.