How Azure pricing works: meters, reservations and the savings plan
Azure has four ways to pay for the same virtual machine. Picking the right one is worth more than picking the right size.
Two teams can run identical Azure infrastructure and see invoices that differ by half. The difference is rarely architecture. Azure pricing turns on which of the four purchasing mechanisms they used, and whether anyone looked at the meters.
Meters build the invoice
Azure does not bill resources, it bills meters. A single Linux virtual machine typically emits at least four: compute hours for the VM size, capacity for its managed disk, transactions against that disk, and outbound bandwidth. Add a public IP address and a load balancer and the count rises.
This is why deleting a VM does not always stop the charges. The managed disk, the public IP reservation and any snapshots are separate meters with separate lifecycles. Cost Management groups them by resource, which is the fastest way to find the ones nobody meant to keep.
The four ways to pay for compute
Pay as you go. The list rate, billed per second in most services with a per minute minimum. No commitment. Correct for anything unpredictable or short lived.
Reservations. A one or three year commitment to a specific VM series in a specific region, in exchange for a substantial discount. The reservation is applied automatically to any matching running instance in the scope you choose, so you do not have to attach it to a particular machine. Best for steady, known workloads such as a database tier that will not move.
Savings plan for compute. A one or three year commitment to an hourly spend figure rather than a specific machine. The discount is smaller than a reservation but it applies flexibly across eligible compute services, series and regions. Best when you know roughly what you will spend but not exactly what you will run.
Spot virtual machines. Spare capacity at a steep discount, reclaimed with short notice when Azure needs it back. Suitable for batch jobs, CI runners, rendering and anything that checkpoints. Not suitable for a database.
Azure Hybrid Benefit
Windows and SQL Server virtual machine rates include a licence component. If your organisation already holds eligible licences with Software Assurance, Hybrid Benefit removes that component from the rate. On a Windows fleet this is frequently the single largest available reduction, and it stacks with reservations.
It is a checkbox at deployment time and an easy one to forget on machines created quickly. Auditing existing VMs for it is usually worth an afternoon.
The Azure pricing line items that surprise people
- Managed disks are billed on provisioned size, not used size. A 1 TB premium disk holding 40 GB costs the same as a full one. Premium SSD tiers also jump in fixed increments, so a disk one gigabyte over a boundary costs a full tier more.
- Public IP addresses. Standard SKU addresses bill hourly whether or not anything is attached.
- Bandwidth out. Inbound is free, outbound is metered beyond a monthly allowance, and traffic between availability zones and regions has its own rates. This is covered across providers in data transfer costs.
- Snapshots and backups. Cheap individually, persistent forever, and frequently orphaned.
- Log Analytics ingestion. Diagnostic settings that send everything to a workspace can quietly become one of the largest meters on the invoice.
- Idle App Service plans. The plan bills, not the apps on it. An empty plan still costs.
A workable cost routine
- Tag every resource with an owner and an environment on creation. Enforce it with Azure Policy if more than two people have access.
- Set a budget with alerts at 50, 80 and 100 percent of the expected monthly figure.
- Review Azure Advisor cost recommendations monthly. It is not perfect, but it reliably finds idle resources and oversized VMs.
- Once you have three months of stable usage, buy a reservation or savings plan covering the baseline.
- Move anything interruptible to spot.
How this compares
The structure is close to what AWS does with savings plans and reserved instances, and Google Cloud takes a noticeably different approach by applying sustained use discounts automatically without any commitment. Those differences are set out in cloud pricing models compared and, provider to provider, in Azure vs Google Cloud.
If you are still working out which subscription type you are on, start with Azure account types explained.
Common questions
What is the difference between an Azure reservation and a savings plan?
A reservation commits to a specific VM series in a specific region for a bigger discount. A savings plan commits to an hourly spend amount and applies flexibly across eligible compute, for a smaller discount.
Do reservations lock me into one machine?
Not exactly. Reservations apply to matching usage automatically, and many can be exchanged or cancelled subject to the current policy. They are a billing construct, not a reserved physical server.
Is Azure Hybrid Benefit worth using?
If you already hold eligible Windows Server or SQL Server licences with Software Assurance, it removes the licence component from the VM rate, which is often the largest single saving available on Windows workloads.
AccountMarket Editorial
Written and maintained by the team behind accountmarket.org. We publish practical notes on the cloud platforms we work with every day, and we update articles when the platforms or our catalogue change.
Accounts covered in this article
Live options and pricing from the catalogue.
Buy Microsoft Azure Account
Azure subscriptions with credits and full portal access, covering tenants, resource groups and the quotas that matter before you deploy.
From $25.00
Keep reading
Cloud Pricing
How cloud credits work, and what expires first
Credits are simpler than they look and have more edges than people expect. Four rules cover almost every question about them.
Cloud Comparisons
AWS vs Azure: how to actually choose between them
For most organisations this is not a technical decision. Here is what genuinely differs, what does not, and the three questions that usually settle it.
Microsoft Azure
Azure account types explained: tenants, subscriptions and where the credit sits
Azure splits identity, billing and resources across three layers. Knowing which layer holds the credit, the quota and the permissions explains most Azure confusion.