Azure VM Cost: Compute, Disks, Licenses and Stopped VMs Azure doesn't publish one VM price. The bill stacks compute capacity, runtime, disks, OS or software licenses, networking, and supporting services. A VM that looks cheap at its hourly rate gets expensive fast when it runs around the clock, sits on premium disks, ships with Windows, or leaves billable resources behind after shutdown.

Flexera's 2025 report estimates 27% of cloud spend is wasted across IaaS and PaaS. This article covers representative pricing, the main cost drivers, a component-by-component breakdown, stopped versus deallocated billing, and a practical monthly estimate method.

Key Takeaways

  • Price depends on size, region, OS, purchasing model, running hours, disks, and add-ons.
  • Monthly cost = hourly rate × billable hours, plus disks, licenses, and networking.
  • Commitments and Spot cut compute rates, but only for the right workloads.
  • Deallocation stops compute billing; disks, IPs, and snapshots keep charging.

How Much Does an Azure VM Cost? (Pricing Overview)

There is no universal VM price. Every figure below is illustrative: East US, pay-as-you-go, retail USD, retrieved from Microsoft's Retail Prices API. Negotiated enterprise rates differ. Compute only, excluding disks and other services.

Representative SKU Typical use Linux / hour Windows / hour
Standard_B2s Dev/test, burstable $0.0416 $0.0496
Standard_D2s_v5 General-purpose production $0.096 $0.188
Standard_E2s_v5 Memory-heavy databases $0.126 $0.218
Standard_F2s_v2 CPU-heavy batch $0.0846 $0.177
Standard_NC4as_T4_v3 GPU workloads $0.526 $0.71

These are hourly rates, not monthly totals. Microsoft's calculator assumes 730 hours a month. At that convention, a D2s_v5 on Linux works out to roughly $70 a month in compute alone, and the Windows version to roughly $137. A B2s on Linux lands near $30.

The range widens at the high end because GPU and memory-optimized families carry specialized hardware. Compute-only pricing and an all-in monthly figure are different numbers, so keep them separate in any budget.

Azure VM pricing range from burstable to GPU workloads

Pricing varies by region

The same D2s_v5 Linux VM costs $0.096/hour in East US and $0.112/hour in West US. Quote the region every time.

Purchasing models compared

  • Pay-as-you-go: no commitment, billed by the second. Best for temporary or unpredictable workloads.
  • Reserved VM Instances: 1- or 3-year terms for stable, predictable configurations. Microsoft advertises up to 72% off, based on a specific 3-year M64ls example. Reservations cover compute only, not Windows software charges or other resources.
  • Savings Plan for Compute: an hourly spend commitment (up to 65% off in Microsoft's example) that stays flexible across sizes and OS. It bills every hour whether you use it or not and can't be cancelled.
  • Spot VMs: up to 90% off unused capacity, but Azure can evict the VM. Use for restartable jobs only.
  • Azure Hybrid Benefit: lets organizations with eligible Windows Server licenses (active Software Assurance, at least 8 core licenses per VM) drop the Windows license charge. Savings vary, so confirm eligibility before budgeting.

Low-cost versus high-cost builds

Lower-cost setups use small or burstable VMs, Linux, standard disks, scheduled runtime, and suitable commitments. Higher-cost setups combine large CPU or memory footprints, GPUs, Windows or marketplace images, premium storage, 24/7 operation, and heavy data transfer.

A low hourly rate still loses if the VM is undersized, throttled, or paired with inefficient storage.

Low-cost versus high-cost Azure VM configuration comparison

Key Factors That Affect Azure VM Cost

Price comes from technical, operational, and licensing decisions together, not size alone.

VM type, size, and workload profile

Hourly rates scale with vCPU, memory, and specialized hardware. Match the family to the job:

  • B-series: burstable, for dev/test, small databases, and proofs of concept. Credits build below baseline; once exhausted, performance drops to baseline.
  • D-series: balanced general purpose for web and application servers.
  • E-series: memory optimized for large databases and analytics.
  • F-series: compute optimized for batch processing and CPU-bound work.
  • N-series: GPU families for AI/ML training, inference, and graphics.

Choose size from measured CPU, memory, and disk I/O data. Azure Advisor's default view looks at the last 7 days, and its user-facing targets are P95 CPU at or below 40% and P99 memory at or below 60%.

Region and availability

Rates differ by region. Compare only regions that satisfy latency, data residency, availability, and regulatory needs, then name the US region in your estimate.

Operating system and software licensing

Windows Server runs noticeably higher than Linux for the same size, as the table above shows (D2s_v5 nearly doubles). Some Linux marketplace images add publisher support fees, and premium marketplace software can bill on its own meters. Check the exact image plan in the calculator.

Storage, disks, and performance

Disk cost follows type, provisioned capacity, performance tier, redundancy, and snapshots.

  • Standard HDD: latency-tolerant, light workloads
  • Standard SSD: lower-IOPS and non-production use
  • Premium SSD: low-latency production
  • Premium SSD v2: tunable capacity, IOPS, and throughput
  • Ultra Disk: top performance; charges for capacity, IOPS, and throughput

Microsoft's East US Premium SSD v2 examples run from $5.14/month (64 GiB) to $186.71/month (1,024 GiB, 15,000 IOPS). A small VM on oversized premium storage can cost more than the compute.

Runtime, power state, and utilization

Continuous operation, business-hours schedules, autoscaling, and idle dev environments all change billable hours. A VM running 10 hours on weekdays uses roughly a third of the hours in a 730-hour month. Power state matters too, covered below.

Networking and related services

Add these to any estimate:

  • Internet egress: first 100 GB/month free, then about $0.087/GB in North America
  • Static public IPv4: $0.005/hour
  • Standard Load Balancer: $0.025/hour for the first 5 rules, plus $0.005/GB processed
  • VNet peering, VPN or ExpressRoute links
  • Azure Monitor log ingestion, billed per GB
  • Backup and snapshots

Model data movement and supporting resources, not just the VM.

Azure VM supporting services and networking cost components

Azure VM Cost Breakdown: Compute, Disks, Licenses, and Stopped VMs

Compute is one line on the bill. Here is each component.

Compute charges (recurring)

Hourly compute rate × billable running hours. SKU, region, OS, and purchasing model set the rate. Always state the hours assumed. A D2s_v5 Linux VM running 730 hours at $0.096 costs about $70; at 220 business hours, about $21.

Managed disks and snapshots (recurring)

OS disks, data disks, provisioned capacity, performance tier, redundancy, and snapshots all bill separately. Snapshots are listed at $0.05/GB-month on used data. These charges continue when compute is deallocated, and deleting a VM does not delete its disks by default.

Operating system and software licenses (recurring)

Windows Server and marketplace images add license cost, either folded into the hourly rate or billed separately. In the East US table, Windows adds roughly $0.09/hour to a D2s_v5.

With eligible Azure Hybrid Benefit, you pay the base compute rate instead. Don't assume eligibility in a budget until licensing confirms it.

Networking, monitoring, backup, and ancillary services (recurring or usage-based)

Separate required services from optional ones. Egress, public IPs, and load balancing usually come with the architecture. Log ingestion, backup, and security services are often optional but easy to forget.

Azure Backup charges a protected-instance fee ($5/month up to 50 GB, $10/month up to 500 GB) plus storage, which starts at $0.0224/GB-month for LRS.

Stopped, stopped-allocated, and deallocated VMs

Power state decides whether compute billing stops:

State Compute billed? Other resources
Running Yes Billed
Stopped (Allocated) Yes Billed
Stopped (Deallocated) No Disks, networking may still bill

Shutting down inside the guest OS usually leaves the VM allocated, so charges continue. Deallocate from the portal, CLI, or automation to release the host.

Even then, disks, snapshots, static IPs, backup data, and monitoring keep billing. A Savings Plan commitment is billed regardless, and a Reservation stays purchased though deallocation stops matching usage.

Azure VM power states and resources that continue billing

Audit tip: in Azure Cost Management, group by ResourceId, meter category, subcategory, and meter. That shows whether an unexpected charge comes from compute, disk, license, network, or a supporting service.

When disk sprawl, not compute, drives the waste, Lucidity's Lumen supports Azure with visibility into every disk and flags four idle categories: unattached, reserved, unmounted, and zero-I/O. These can represent up to 70% of unused block-storage spend.

How to Estimate and Reduce the Right Azure VM Budget

The right budget balances performance, availability, licensing, and operations. The lowest hourly rate is rarely the right answer.

Build an all-in monthly estimate

  1. Define the workload: family, size, region, OS, image, schedule, peak demand, availability needs.
  2. Calculate compute: verified hourly rate × expected billable hours.
  3. Add everything else: disks, snapshots, licenses, networking, monitoring, backup.
  4. Model scenarios: 24/7, business hours, seasonal scaling, and deallocated.

Four-step Azure VM monthly cost estimation workflow

Validate with the Pricing Calculator and Cost Management

The Azure Pricing Calculator pulls from the Retail Prices API. Match the region, OS, size, disks, purchasing model, and hours.

After deployment, compare against Cost Management data for power states, disk utilization, data transfer, and commitment coverage. Record the pricing date and source, since rates and terms change.

Reduce waste without hurting reliability

  • Right-size VMs and disks using telemetry.
  • Auto-shutdown dev/test and confirm VMs end up deallocated. Start/Stop VMs v2 has its own automation charges.
  • Delete unattached disks, unused public IPs, and old snapshots.
  • Buy Reservations or Savings Plans only for proven, stable usage; keep Spot for interruptible work.
  • Don't buy premium disks to cover uncertain demand. Check utilization first.

What most people miss

  • The hourly rate hides disk, license, network, monitoring, and backup charges.
  • "Stopped" does not mean free.
  • Discounts and Hybrid Benefit can produce misleading savings without checking utilization, eligibility, and term restrictions.

Conclusion

Azure VM cost reflects size, region, OS, purchasing model, runtime, disks, licenses, networking, and supporting services. A reliable estimate starts with current Microsoft pricing and an all-in calculation, then improves through right-sizing, deallocation, storage cleanup, and sensible commitments.

The right VM cost is the one that meets performance and availability needs while minimizing unused compute, storage, and licensing spend.

Frequently Asked Questions

How much does a VM cost on Azure?

It depends on size, region, OS, pricing model, and running hours. East US Linux examples run from about $0.04/hour (B2s) to $0.53/hour (GPU). Use the Azure Pricing Calculator for a current estimate including disks.

How to calculate Azure VM cost?

Multiply the hourly compute rate by billable hours (730 for a full month). Then add managed disks, licenses, networking, monitoring, backup, and other charges.

Does Azure charge for stopped VMs?

It depends on the state. Stopped (Allocated) VMs are still billed for compute. Stopped (Deallocated) VMs aren't, but disks and other retained resources may continue to charge.

What is the difference between stopped and deallocated Azure VMs?

A stopped VM stays allocated to a host and keeps billing. Deallocation releases the host and ends ordinary compute billing. Confirm the power state in the portal.

Are Azure managed disks still charged when a VM is stopped?

Yes. Managed disks are separate billable resources, charged on provisioned configuration even when compute is deallocated.

Is Windows more expensive than Linux on Azure?

Usually. Windows Server adds licensing cost; a D2s_v5 is $0.188/hour versus $0.096 on Linux in East US. Eligible organizations may reduce it with Azure Hybrid Benefit.