Here is something we see in almost every Azure environment we assess: teams who know roughly what their VMs cost per month, but drastically underestimate the true figure.
They look at the VM SKU price, multiply it by the number of machines, and arrive at a number that feels about right. The actual cost is often double. Because the compute charge is only part of the story.
The Visible Cost
The compute hour rate is the number everyone knows. It scales linearly with time and it is the figure on the pricing calculator. Simple enough.
But that is where the simplicity ends.
What Everyone Forgets
Managed disks. Every VM has at least an OS disk, and many have data disks. Managed disks bill 24/7 regardless of whether the VM is running. Deallocate a VM to stop compute charges and the disks keep billing. You would need to delete them entirely to stop paying.
Licensing. If you are running Windows Server VMs without Azure Hybrid Benefit, the licence cost is baked into your compute price — and it is significant. A Windows VM can cost nearly double the equivalent Linux VM. SQL Server licensing adds even more. If you already own licences through Software Assurance, Hybrid Benefit eliminates this cost. We regularly find organisations that have not activated it.
Backup. Enabling backup adds a per-instance fee that charges regardless of whether the VM is powered on. The cost scales with the amount of protected data.
Security tooling. Per-VM security charges apply whether the machine is running or not. These often do not appear on the VM's cost breakdown — they show up under a separate line item, making them easy to miss.
Monitoring and logging. If your VMs are shipping logs and performance data to a central workspace, you pay per GB ingested. A single VM might push several GB per month depending on collection rules, and it is rarely attributed back to the VM in anyone's mental accounting.
Network egress. Data leaving Azure costs money. VMs that serve content, replicate data, or send backups offsite can generate meaningful egress charges.
What a VM Actually Costs
When you add compute, disks, licensing, backup, security, logging, and egress together, the true monthly cost of a VM is typically two to three times the headline compute price. That is not a rounding error.
The Utilisation Problem
We regularly see VMs averaging five to fifteen percent CPU utilisation. You are paying for the full capacity of the machine — compute, disks, licensing, the lot — and using a fraction of it.
A VM sitting at ten percent CPU is not "mostly idle." It is a resource where you are paying for one hundred percent of capacity and getting ten percent of value.
When 24/7 Is Not Justified
The waste shows up in workloads that do not need continuous uptime but get it by default:
- Dev/test environments running nights and weekends when nobody is working
- Batch processing that runs for two hours on a VM provisioned for twenty-four
- Staging environments that mirror production but rarely see traffic
- Scheduled tasks that run once overnight
These workloads do not need a VM running 24/7. They need capacity that exists when work needs doing and does not exist when it does not.
The Cost of Doing Nothing
If you have fifty VMs and twenty of them could be right-sized, shut down outside hours, or replaced with a more efficient service, that is potentially thousands per month in savings — for changes that take days to implement, not months.
Every month that passes without a review is another month of waste locked in.
Want to see the true cost of your Azure VMs? Get a free FinOps assessment — we break down your VM spend including all the costs most teams miss.