Consumption-Based Model
😟 THE PROBLEM
You paid for a huge server all year, but used it fully only one month.
😊 THE SOLUTION
Use consumption-based pricing: pay for what you actually use.
- Big up-front purchase✓ No up-front cost
- Paying for idle capacity✓ Delete or switch off and stop paying
- Surprise bills✓ Budgets and alerts in Cost Management
Quick answer
The consumption-based model means you pay only for the cloud resources you use, measured by time, quantity or transactions, instead of buying capacity up front. There is no up-front cost, nothing to pay for unused capacity, and you can stop paying by removing resources. It is the pricing foundation of cloud computing and turns IT spending into operating expenditure (OpEx).
Exam objective: 1.1.5 Describe the consumption-based model. (Skills measured as of July 20, 2026)
Start with a question
Would you pay for a full year of gym membership if you only plan to go for three weeks?
Traditional IT is like buying the annual membership. You pay for servers sized for your busiest day, all year, even when they sit idle.
The cloud is like a pay-per-visit gym pass: each visit is recorded and you pay for what you used. That is the consumption-based model.
Explain it like I’m 10
The technical explanation
In the consumption-based model, cloud resources are metered and billed according to actual usage. Microsoft’s AZ-900 material lists three benefits:
- No up-front costs: nothing to buy before you start.
- No need to purchase and manage costly infrastructure that you might not fully use.
- Pay for additional resources only when you need them, and stop paying when you no longer need them.
How Azure meters common services
| Service | Typical meter |
|---|---|
| Virtual Machines | Per second of running time, by VM size (and OS licence if included) |
| Managed Disks | Per disk size tier per month (billed even if the VM is stopped) |
| Blob Storage | GB stored per month + read/write operations + data retrieval for some tiers |
| Azure Functions (consumption plans) | Executions + memory used over time (GB-seconds) |
| Bandwidth | GB of data transferred out (egress); inbound data is generally free |
| Azure SQL Database | Provisioned compute (vCores) per hour, or serverless compute used per second |
Bought once for an "average busy day". Idle at night, overwhelmed at the 3 pm exam rush.
37%capacity idle
5%demand unmet
Capacity follows demand automatically with a small safety buffer. Very little waste, nobody turned away.
15%capacity idle
0%demand unmet
Architect level FinOps: making consumption pricing work for you
The consumption model gives engineers the power to spend money with an API call. Mature organisations treat that as a shared responsibility called FinOps:
- Visibility: tag every resource (owner, cost centre, environment) and report by tag in Cost Management.
- Accountability: budgets per team with alert thresholds (for example 50%, 80%, 100%), plus anomaly alerts.
- Optimisation: right-size with Azure Advisor, auto-shutdown for non-production, delete orphaned disks and IPs, choose storage tiers deliberately, and buy reservations or savings plans for the steady baseline (see Cloud Pricing Models).
- Architecture: prefer services that scale to zero for spiky workloads; cache to cut egress; keep chatty services in the same region.
Real-world business scenario
A university's research group
- The problem
- Simulations needed 500 CPU cores for two weeks each semester, then almost nothing. Buying a cluster would mean idle hardware 90% of the year.
- What they used
- Azure Batch with VM pools created for each run and deleted afterwards, plus Blob Storage for results.
- Why that choice
- The consumption model meant paying only during the simulation weeks, with no capital purchase.
- The result
- Research ran on schedule at a fraction of the cost of owning a cluster, and budget alerts kept the grant spend on track.
When to use it and when not to
✓ Use it when…
- Variable, seasonal or unpredictable workloads.
- Experiments, prototypes and short-term projects.
- Start-ups and teams without capital budget.
- Any workload where you can scale down or switch off when idle.
✕ Think twice when…
- Steady 24/7 workloads billed purely pay-as-you-go. Commitment discounts (reservations, savings plans) are usually much cheaper.
- Environments with no cost ownership. Consumption without budgets leads to surprises.
↔ Alternatives to consider
- **Azure Reservations** or **Azure savings plan for compute** for predictable usage.
- **Spot VMs** for interruptible batch work at deep discounts.
Interview preparation
Say your answer out loud first, then open the model answer. Interviewers care more about your reasoning than the exact words.
Beginner What is the consumption-based model?
Model answer
It means paying for cloud resources based on how much you actually use, like an electricity bill. If I run a VM for ten hours, I pay for ten hours. If I delete it, I stop paying for it.
Interviewer follows up
What benefits does that give a business?
You
No up-front costs, no paying for idle capacity, the ability to experiment cheaply, and costs that grow and shrink with the business.
Intermediate How does Azure measure consumption for different services? Give examples.
Model answer
Each service has meters. VMs are billed per second of running time by size, storage per GB per month plus operations, Azure Functions on consumption plans per execution and GB-seconds of memory, bandwidth per GB of egress, and databases by provisioned compute units or by serverless usage.
Experienced developer The consumption model is flexible, but bills can surprise teams. What controls do you put in place?
Model answer
Budgets with alerts in Microsoft Cost Management at subscription and resource-group level, tagging policies so every cost has an owner, auto-shutdown for dev/test, Azure Advisor cost recommendations, anomaly alerts, and regular reviews of the biggest meters. Watch hidden meters like egress, log ingestion, premium storage transactions and orphaned disks or public IPs after VMs are deleted.
Scenario A student creates a powerful GPU VM for a weekend project and forgets about it for a month. What happens?
Model answer
Under the consumption model they are billed for every hour it was running, which can be very expensive for GPU sizes. The fix is to stop (deallocate) or delete it, set a budget alert, and use auto-shutdown schedules.
Test yourself with exercises
4 original practice questions in the AZ-900 style. Pick your answers, then check them. You will see why each option is right or wrong. Score 75% or more and this topic is marked complete.
Quick revision
Key points
- Pay only for what you use. No up-front cost, no charge for capacity you do not consume.
- Resources are metered by time, quantity or transactions.
- Delete or deallocate resources to stop most charges. Storage still costs while it exists.
- Turns IT spending into OpEx.
- Needs active cost management (budgets, tags, alerts).
Important terminology
- Consumption-based model
- Paying for actual usage of resources rather than for fixed capacity bought in advance.
- Pay-as-you-go
- The default Azure pricing option, billed for usage with no commitment.
- Meter
- The unit Azure uses to measure a resource's usage, such as VM hours, GB stored per month or millions of executions.
- Egress
- Data transferred out of an Azure region or out to the internet, which is usually charged. Inbound data (ingress) is generally free.
Common mistakes
- Assuming a stopped (but not deallocated) VM is free.
- Forgetting that disks, public IPs and backups keep billing after a VM is deleted unless removed too.
Exam tips
- "No up-front costs" + "pay for what you use" + "stop paying when you stop using" = consumption-based model.
- Inbound data transfer to Azure is generally free; outbound data transfer is generally charged.
Five quick revision questions
-
1.What do you pay for in a consumption-based model?Show
Only the resources you actually use.
-
2.Is there an up-front cost in the consumption model?Show
No.
-
3.Which expenditure type does the consumption model represent?Show
OpEx (operational expenditure).
-
4.Is inbound data transfer into Azure usually charged?Show
No, ingress is generally free. Egress is charged.
-
5.Name one tool to avoid surprise bills.Show
Budgets and alerts in Microsoft Cost Management.
Official references
Finished this lesson? Tick it off. Your progress is saved in this browser.
Next up: Cloud Pricing Models