Azure Reservations and Savings Plans

Azure offers several ways to pay for services. The simplest is pay-as-you-go (PAYG), where you pay for what you use each month with no upfront commitment. However, for predictable workloads, PAYG can be expensive. To incentivize customers to commit to longer-term usage, Azure provides two discount programs: Azure Reservations (also called Reserved Instances for VMs) and Azure Savings Plans. Both offer significant discounts—up to 72% compared to PAYG—in exchange for a commitment of one or three years. The key difference is flexibility: Reservations lock you into a specific resource configuration (e.g., a specific VM size in a specific region), while Savings Plans allow you to change resources as long as you stay within a committed hourly spend.

Step 1: Choose your commitment. For Reservations, you pick a specific service (e.g., Virtual Machines, SQL Database, Azure Cosmos DB), a tier (e.g., VM size D2s v3), a region (e.g., East US), and a term (1 or 3 years). You also choose the billing frequency: upfront (full payment), monthly, or partial upfront (e.g., pay 50% upfront, rest monthly). For Savings Plans, you choose a compute scope (e.g., all compute services in a subscription or management group) and a term (1 or 3 years), and you commit to a specific hourly spend (e.g., $1.00 per hour). You can also choose to pay upfront or monthly.

Step 2: Azure calculates the discount. When you purchase a Reservation, Azure applies the discounted rate to any matching resources you run. For example, if you buy a 1-year reservation for a D2s v3 VM in East US, any D2s v3 VM you run in that region will automatically get the reserved price. The discount is applied at the meter level—each hour, Azure checks if you have running resources that match your reservation, and if so, it charges the reserved rate instead of the PAYG rate. If you run more than one matching VM, the discount is applied to the first VM that matches; additional VMs are charged at PAYG.

Step 3: Billing and usage. Reservations and Savings Plans are billed separately from your resource usage. The commitment amount appears as a line item on your invoice. For Reservations, you pay the committed amount (upfront or monthly) regardless of whether you use the resource. For Savings Plans, you are charged the committed hourly amount multiplied by the number of hours in the billing period (e.g., $1.00/hour * 730 hours in a month = $730). If your actual usage exceeds the commitment, you pay the PAYG rate for the excess. If you underuse, you still pay the full commitment—there is no refund for unused hours.

Reservation scopes: You can apply a reservation to a single subscription, a resource group, or a billing account (Enterprise Agreement or Microsoft Customer Agreement). The scope determines which resources get the discount. For example, if you scope a reservation to a subscription, only VMs in that subscription get the discount. If you scope it to the billing account, all subscriptions under that account can use the discount.

Reservation exchange and cancellation: You can exchange a reservation for another reservation of the same type (e.g., swap a VM reservation for a different VM size) without penalty. You can also cancel a reservation, but you may incur a penalty (up to 12% of the remaining commitment) and receive a prorated refund. Savings Plans allow exchanges but not cancellations—once you commit, you cannot cancel, though you can reduce the commitment by purchasing a new plan with a lower hourly amount and then letting the old one expire.

Discount percentages: The exact discount depends on the service, region, term, and payment option. Typically, 3-year reservations offer higher discounts than 1-year. Upfront payment gives a slightly higher discount than monthly. For example, a 3-year, upfront reservation for a D2s v3 VM in East US might save 60% vs PAYG, while a 1-year monthly reservation might save 40%.

In an on-premises data center, you purchase hardware (servers, storage) upfront—a capital expenditure (CapEx). You own the hardware and can use it as long as you want, but you bear the risk of over-provisioning or underutilization. Azure Reservations and Savings Plans are similar to a CapEx model in that you commit upfront, but they are operational expenditures (OpEx) because you pay monthly or upfront but never own the hardware. The key difference is flexibility: with on-premises hardware, you are locked into that specific equipment; with Azure, you can exchange reservations or change your Savings Plan commitment to adapt to changing needs (within limits).

You can purchase and manage Reservations and Savings Plans through the Azure portal under Cost Management + Billing > Reservations or Savings Plans. The portal shows your active commitments, usage, and savings. You can also use Azure CLI or PowerShell. For example, to list reservations:

az reservation list

To purchase a reservation for a VM:

az vm reservation create --reservation-order-id <id> --vm-size Standard_D2s_v3 --quantity 1 --term P1Y --scope Single --subscription <sub-id>

Savings Plans are purchased similarly using the az billing commands. The CLI is useful for automation and bulk operations.

Scenario 1: A company runs a production database 24/7. They know they need a specific VM size in a specific region for at least the next year. They buy a 1-year reservation for that VM, saving 40% vs PAYG.

Scenario 2: A startup has variable compute needs—sometimes they use more VMs, sometimes less, but they always have at least $500 worth of compute per month. They buy a Savings Plan with a $0.70/hour commitment (about $500/month). This gives them a discount on all their compute usage, and if they need more, they pay PAYG for the excess. If they need less, they still pay the $500 commitment but get the discount on whatever they use.

Scenario 3: A company runs multiple environments (dev, test, prod) across different subscriptions. They want to centralize cost savings. They purchase a Savings Plan at the management group scope, so all subscriptions under that group benefit. This simplifies billing and ensures no subscription misses out on discounts.

Scenario 1: E-commerce company with predictable production VMs. A mid-sized e-commerce company runs a cluster of 10 D4s v3 VMs in West US for its production web servers. These VMs run 24/7 year-round. The company's cloud architect reviews Azure Cost Management and sees that these VMs cost $5,000/month at PAYG. By purchasing a 1-year reservation for 10 D4s v3 VMs in West US with monthly payment, they reduce the cost to $3,000/month—a 40% savings. The team configures the reservation scope to the production subscription. The discount is automatically applied, and the finance team sees the savings in the monthly billing report. One common mistake: if the company later decides to migrate to a different VM size (e.g., D4s v4), they would need to exchange the reservation. If they don't, the new VMs would be charged at PAYG, and the old reservation would go unused, wasting money.

Scenario 2: SaaS startup with variable compute needs. A SaaS startup uses Azure Kubernetes Service (AKS) with a mix of spot VMs and regular VMs. Their compute spend fluctuates between $800 and $1,200 per month. They want to save money but need flexibility. They purchase a 1-year Savings Plan with a $1.00/hour commitment (about $730/month). This covers their baseline compute usage. Any additional usage beyond $1.00/hour is charged at PAYG. The Savings Plan automatically applies discounts to all eligible compute services (VMs, AKS, etc.) across all subscriptions in the management group. The startup saves about 30% on their baseline. A pitfall: if the startup's usage drops significantly (e.g., to $500/month), they still pay the $730 commitment, resulting in overspend. To avoid this, they could purchase a lower commitment or use a mix of reservations for predictable workloads.

Scenario 3: Large enterprise with multiple departments. A large enterprise has several business units, each with its own Azure subscription. The central IT team wants to negotiate enterprise-wide discounts. They purchase a 3-year Savings Plan at the billing account scope with a $10.00/hour commitment. All subscriptions under the enterprise agreement benefit from the discount. The IT team uses Azure Cost Management to allocate the Savings Plan cost back to each department based on their usage (via chargeback). This centralizes cost savings and simplifies budgeting. A common issue: if one department spikes usage, it consumes more of the Savings Plan, potentially leaving less for others. The IT team must monitor utilization and adjust commitments periodically.