Azure Stateless VM Could Use Ephemeral OS Disk
An ephemeral OS disk lives on the VM's own local storage instead of remote Azure Storage, so a stateless VM on a managed OS disk is paying to persist an OS state it never keeps.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Move the stateless VM to an ephemeral OS disk. Where the saving can be proven it is priced; where it cannot, the finding says so.
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
- Verify the workload is truly stateless: no app data on the OS disk, /etc is provisioned via cloud-init or images.
- Verify the VM SKU supports ephemeral OS disks (check size's Cache size / Temp storage column in the SKU table).
- Recreate the VM from the same image with ephemeral OS disk enabled (set diffDiskSettings.option=Local in ARM / CLI).
- Reattach data disks and reconfigure networking on the new VM.
- Delete the old VM and its managed OS disk.
These are the steps the finding carries in the product.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1309- Full reference
Related checks
See the oversized resources 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.