Azure vm cost: compute pricing and idle resources
Azure VM cost depends on the selected size, operating system, Region and billing arrangement. Review compute alongside the disks and networking that remain around the virtual machine, particularly when planning shutdown schedules.
Request a quote
Check the monitoring costs generated by the VM estate with the Log Analytics workspace cost review.
Azure VM cost: compute and retained resources
Microsoft documents VM states and their billing behavior. Stopped (allocated) VMs are still billed for compute. Deallocated VMs are not billed for compute, but disks and some networking resources can remain charged. A shutdown plan should verify the state reported by Azure rather than relying on what the guest operating system displays. Deallocation does not cancel an existing reservation or savings plan obligation; compare the remaining total cost, not only the VM usage meter.
| Cost dimension | Evidence | Decision |
|---|---|---|
| Compute | Size, Region, operating system and billed time | What capacity and schedule does the application require? |
| Licensing | Entitlement and agreement terms | Is the assumed licence treatment valid? |
| Disks | Provisioned storage and performance | What data must remain retained? |
| Networking | Addresses, traffic and related services | Which charges continue when compute stops? |
The Azure cost optimization review starts from the billing agreement and scopes. Use that boundary before estimating Azure VM cost per month. Include the actual rate and planned operating hours in the calculation. A continuously running configuration and a scheduled test environment should not be compared using the same assumed runtime.
Calculate a monthly scenario with the correct assumptions
Use the official Azure pricing calculator for a configuration estimate. Select the Region, instance configuration, operating system and purchase assumptions that match the intended service. Keep the saved estimate and rate date with the analysis, then reconcile it with your agreement terms rather than treating a public calculator as your invoice.
- Record the VM inventory with owner, environment and availability requirement.
- Confirm the scheduled operating hours and restart procedure.
- Separate licence assumptions from compute and storage inputs.
- Model the resources that remain after deallocation.
Azure VM cost when stopped depends on allocation state. Ask the operating team to verify deallocation in the approved process. For an environment that must restart on demand, include the restart and validation steps in the plan. Finance should assess the total recurring cost that remains, rather than reporting the removed compute line as the entire saving.
Review size before commitment
For Azure VM cost optimization, review utilization over a representative application cycle and ask engineering to approve the target configuration. Check memory, response behavior and storage demand beside CPU. Keep the maintenance and rollback requirements in the proposal. A smaller VM is useful only if it still runs the workload within its agreed service limits.
- Reconcile current charges with the VM and its attached resources.
- Test a size or schedule change against workload requirements.
- Measure remaining demand after the approved change.
- Compare commitment options against that remaining baseline.
Read the existing Azure reservations and savings plan comparison before considering a purchase. For a business comparison across clouds, use the cloud TCO calculator and include implementation and operational inputs. If the same application uses another cloud, the EC2 review offers a separate workload checklist rather than a claim that the two services have identical costs.
Prepare a VM and disk inventory, billed usage, performance evidence and relevant licence conditions for a quote. Specify the subscriptions included and the permissions available to the reviewer. Ask for calculations your team can edit, a recommendation register by resource and a clear distinction between analysis and implementation responsibility.

Questions before a cost review
Does Azure charge for a stopped VM?
Stopped (allocated) VMs still incur compute charges. Deallocated VMs do not incur compute charges, while retained disks and some networking resources can remain charged. Verify the state and each resource on the bill.