Commercial and channel
Savings Plan
Azure savings plan
An Azure savings plan for compute is a commitment discount that works differently from a reservation. Instead of committing to a specific virtual machine size and region, the customer commits to a fixed amount of spend per hour for a one-year or three-year term.
Why Savings Plan matters in a Microsoft estate
Savings Plan matters because Microsoft estate decisions often have a commercial owner as well as a technical owner. Clear cost, licence, and partner language helps teams prove value, reclaim waste, and agree the next action before spend becomes harder to challenge.
How Savings Plan shows up in practice
Each hour, Azure automatically applies that benefit to whichever eligible compute usage carries the highest discount first, with anything above the hourly commitment billed at standard pay-as-you-go rates. The eligible service list is broad and applies automatically across regions and families, without the customer having to predict where a workload will run. It covers virtual machines, App Service, Container Instances, Container Apps, the Functions premium plan, dedicated hosts, and Azure Spring Apps for Enterprise. This flexibility is the direct trade-off against a reservation.
A savings plan gives up some of the deepest possible discount depth in exchange for a benefit that follows the spend, rather than waiting for one specific resource configuration to keep running. That makes it a better fit for workloads that shift between VM families, move across regions, or are still evolving in shape. Two mechanics matter when sizing a savings plan. The hourly benefit is use-it-or-lose-it: any hour where actual eligible usage runs below the committed amount leaves that portion of the commitment unrecovered, and it does not roll forward into a later hour. Committing too aggressively therefore wastes money just as surely as not committing at all.
A savings plan also cannot be cancelled, exchanged, or refunded once purchased, unlike a reservation, which makes accurate sizing more consequential. The recommended approach is to size the hourly commitment against a genuine look-back on real usage data, typically from Azure Advisor or Cost Management recommendations, rather than a forecast or a round number. In a mixed estate the two commitment types are usually combined rather than treated as an either-or choice. Reservations cover the stable core that will not move for the length of the term, and a savings plan absorbs the remaining variable layer that a reservation cannot commit to safely.