Consumption Based Services: The Bill That Only Shows Up After You Spend It
TL;DR:
Consumption based services charge you for what you actually used, rather than a fixed number of seats or servers you bought in advance.
Think of it like the difference between a monthly gym membership and paying per class. If you go twice a year, per class is obviously cheaper. If half the office starts going daily and nobody is counting, the per-class bill arrives at the end of the month and it is a number nobody predicted.
On a good day this is the fairest pricing there is, because a quiet month costs you a quiet month. On a bad day somebody leaves something running over a long weekend and you find out on the invoice.
Beyond the Basics:
Here's the shift: the meter moved from what you own to what you use, and the budgeting habits mostly did not follow.
Traditional licensing is a capacity decision made once a year. You buy seats or servers, you own that number whether it is right or not, and the finance side is predictable. Consumption billing inverts it: the resource is allocated the moment somebody asks for it, and the cost lands afterwards.
- Usage is metered continuously. Compute hours, storage volume, transactions, messages, whatever the unit is for that service.
- You are charged in arrears. The invoice reports a decision that was already made, which is the structural difference from a subscription.
- The rate usually varies. Reserved or committed pricing trades flexibility for a lower unit cost, so steady workloads and spiky ones should not be bought the same way.
- Scaling down is where the savings live. The model only pays off if something actually turns off. Provisioned and forgotten costs exactly as much as provisioned and used.
That fourth point is where most disappointment comes from. Businesses move to consumption pricing expecting savings, keep everything running around the clock out of habit, and end up paying more than the flat rate they left.
Azure is the obvious example, and the same shape appears in Microsoft 365 add-ons that meter per transaction, and in security tooling billed by data ingested. Most Microsoft consumption sits under a CSP agreement, so the partner invoice is often where the detail actually surfaces.
Here's the catch: nobody in the building notices a slow increase. Consumption pricing needs a budget alert, an owner for the number, and someone reviewing it monthly, or the first real signal is a quarterly invoice nobody can explain. Set the alerts on day one, not after the surprise.