Study guide

1.4 The Consumption-Based Model

Microsoft Azure Fundamentals AZ-900

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the Microsoft Azure Fundamentals (AZ-900) Exam Study Strategies and Exam Tips

2 Domain 1: Cloud Concepts (25-30%)

1.1 What Is Cloud Computing? 1.2 Cloud Service Models (IaaS, PaaS, SaaS) 1.3 Cloud Deployment Models (Public, Private, Hybrid) 1.4 The Consumption-Based Model

3 Domain 2A: Azure Architecture Components

2.1 Azure Regions and Availability Zones 2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups) 2.3 Azure Resource Manager (ARM) Overview

4 Domain 2B: Azure Compute Services

2.3 Azure Virtual Machines 2.4 Azure App Service, Containers, and Serverless 2.5 Azure Virtual Desktop

5 Domain 2C: Azure Networking Services

2.6 Azure Virtual Networks (VNet) 2.7 Azure VPN Gateway and ExpressRoute 2.8 Azure Load Balancing and Content Delivery

6 Domain 2D: Azure Storage Services

2.9 Azure Storage Accounts and Services 2.10 Azure Database Services 2.11 Azure Data Services and Analytics

7 Domain 2E: Azure Identity, Access, and Security

2.11 Microsoft Entra ID (Azure Active Directory) 2.12 Azure RBAC, Zero Trust, and Defense in Depth 2.13 Azure Security Services

8 Domain 3A: Azure Cost Management

3.1 Factors That Affect Azure Costs 3.2 Azure Pricing Calculator and Cost Management 3.3 Using Tags for Cost Management and Organization

9 Domain 3B: Azure Governance and Compliance

3.3 Azure Policy 3.4 Resource Locks and Tags 3.5 Azure Blueprints, ARM Templates, and Bicep 3.6 Azure Governance Features: Putting It All Together

10 Domain 3C: Azure Monitoring and Management Tools

3.6 Azure Monitor and Service Health 3.7 Azure Compliance, Privacy, and Trust 3.8 Azure Activity Log, Diagnostics, and Resource Health

11 Additional Azure Services and Exam Review

Azure AI and Machine Learning Services Azure IoT and DevOps Services AZ-900 Exam Review: Key Concepts Summary Common AZ-900 Exam Scenarios and Practice

12 Advanced Azure Topics and Service Deep Dives

Azure Migration Services and Tools High Availability and Disaster Recovery in Azure Azure Networking: Private Link, Service Endpoints, and Bastion Azure Management Tools: Portal, CLI, PowerShell, and Cloud Shell Azure SLAs, Service Lifecycle, and Support Plans

1.4 The Consumption-Based Model

Key Takeaways Explain This Topic AI

Consumption pricing meters each service’s actual usage; deallocating compute does not automatically stop storage, network, or backup charges.

Pay-as-you-go has no commitment; reservations and savings plans trade commitment for eligible discounts, while Spot uses reclaimable capacity.

A deallocated VM stops compute billing, but disks and other retained resources may continue to cost money.

Inbound transfer is generally free; outbound and inter-region rates depend on service, route, and offer.

For AZ-900, know the Pricing Calculator for prospective estimates and Cost Management for actual spend; Azure Migrate business cases are broader migration planning.

Last updated: October 2026

Quick Answer: The consumption-based (pay-as-you-go) model charges only for what you actually use — metered by the second or minute, by the GB, or per transaction. There is no mandatory hardware purchase; each meter depends on the resource, and charges may persist for storage or networking even after compute is deallocated. You can optionally commit to 1- or 3-year terms for large discounts.

Why It Matters

In traditional IT you buy hardware up front against a guess about future demand. Overestimate and you waste money on idle servers; underestimate and you cannot serve users. The consumption model lets you adjust provisioned capacity as demand changes, while billing follows each resource’s meters and configuration. For AZ-900, focus on choosing a pricing option and recognizing billing factors in a scenario.

Core principles

No upfront cost — no hardware purchase or mandatory contract (unless you choose a discount commitment).

Adjust capacity — scaling or deallocating can reduce some meters when demand falls, but attached resources may still cost money.

Pay for what you use — billing tracks real consumption.

Inspect each meter — deallocation stops VM compute charges; disks, public IPs, backups, or other retained resources may continue billing.

  • Azure Pricing Options
  • Pay-As-You-Go (PAYG)

The default: pay per second/hour/transaction with no commitment.

Best for: unpredictable or short-term workloads, dev/test, proofs of concept.

Flexibility: maximum — change or stop anytime.

Discount: No commitment discount; actual price may still reflect an offer or agreement.

Reserved Instances (RIs)

Commit to a specific resource (e.g., a VM size in a region) for 1 or 3 years .

Best for: steady-state, 24/7, predictable workloads.

Flexibility: lower — a reservation provides a billing discount for eligible usage within its scope, subject to current exchange and refund rules; it does not guarantee deployable capacity.

Discount: Varies by resource, region, term, and purchase option; compare current prices.

Azure Savings Plans (for compute)

Commit to a fixed hourly dollar amount of compute spend for 1 or 3 years ; the discount flexes automatically across VM families and regions.

Best for: consistent overall compute spend but changing VM mix.

Flexibility: medium — locked to a spend rate, not a specific SKU.

Discount: Varies by eligible compute usage and commitment; compare current prices.

Spot VMs

Buy unused Azure capacity at deep discounts; Azure can reclaim it whenever capacity is needed.

Best for: interruptible, fault-tolerant work — batch jobs, rendering, CI/CD, dev/test.

Flexibility: Capacity is not guaranteed; eviction can occur when Azure needs capacity, so build for interruption.

Discount: Potentially deep and variable; Microsoft advertises up to 90% for eligible Spot VMs.

Pricing Option Comparison

  • Option Commitment Max Discount Best For Key Risk
  • Pay-As-You-Go None No commitment discount Variable/short-term Unit price may be higher
  • Reservations Usually 1 or 3 years Varies Predictable eligible usage Commitment and scope rules
  • Savings Plans 1 or 3 years Varies Consistent eligible compute spend Hourly spend commitment
  • Spot VMs None Variable; up to 90% advertised Interruptible workloads Capacity can be reclaimed
  • How Azure Meters Usage
  • Resource Metered By Example
  • Virtual Machines Each full minute of compute A D2s_v3 running ~730 hours/month
  • Storage Per GB-month + transactions 100 GB of Hot-tier Blob storage
  • Networking Per GB of outbound transfer 50 GB egress to the internet
  • Databases Per vCore/DTU-hour + storage Azure SQL with 2 vCores, 730 hours

Functions (Flex Consumption plan; the older Consumption plan is legacy) Executions + resource consumption, subject to grants and current meters A function invoked repeatedly

Billing rules you must memorize

Inbound data (into Azure): generally free .

Outbound data (leaving Azure): often metered and billed; rates and allowances depend on route, service, and offer.

Deallocated (stopped) VM: compute charges stop , but disk storage charges continue .

Deleted VM: verify disks, public IPs, backups, snapshots, and other associated resources separately; deleting the VM alone does not prove all related charges ended.

On the Exam: The classic trap question is "a stopped VM stops all charges." False — deallocation halts compute only; the OS/data disks still cost money until deleted.

Factors That Affect Cost

  • Factor Effect on Cost
  • Resource type Each service and SKU has its own price and meter; compare the configured total
  • Resource size/SKU Larger VMs and more storage cost more
  • Region Prices vary by region (East US vs West Europe)
  • Bandwidth/egress Outbound transfer is metered
  • Reservations/Savings Plans Eligible commitments can reduce billed rates, subject to terms and scope
  • Azure Hybrid Benefit Reuse existing Windows Server / SQL Server licenses to save

Cost-management tooling (also in the outline): use the Azure Pricing Calculator to estimate before deploying, the Azure Migrate business case for a broader migration comparison (outside the current calculator objective), Azure Cost Management + Billing to track and analyze actual spend, and budgets/alerts plus resource tags to govern and attribute costs.

Study focus: Match a workload to an eligible pricing option (steady usage ⇒ consider a reservation; interruptible batch ⇒ Spot; unpredictable or short use ⇒ pay-as-you-go) and check which meters continue after a resource is stopped.

Worked Scenario: Picking the Right Commitment

An analytics company runs three distinct workloads. Its production database servers run 24 hours a day, every day, with steady load — these are textbook Reserved Instance candidates, locking in potential savings for a 1- or 3-year term because the demand is fully predictable. Its data-science team runs large, restartable model-training jobs overnight that tolerate interruption — perfect for Spot VMs at variable discounts, since an eviction merely reschedules the job.

Its developers spin up short-lived test environments a few hours at a time on an unpredictable schedule — best left on Pay-As-You-Go , because committing would waste the discount on capacity they do not consistently use. If the company has consistent total compute spend but keeps changing VM families, a Savings Plan captures a discount across eligible usage without locking a specific SKU.

Azure Hybrid Benefit and Other Savings Levers

Beyond the four pricing options, AZ-900 expects you to recognize Azure Hybrid Benefit : organizations that already own Windows Server or SQL Server licenses may be able to apply eligible licenses to Azure under the current benefit terms, reducing eligible license-related charges. Combined with reservations, Hybrid Benefit can stack for substantial savings. Other levers that affect the bill include choosing a cheaper region , right-sizing the VM SKU , and reducing egress by keeping traffic within a region.

Cost-Management Tooling Summary

  • Tool Purpose Before or After Deploy
  • Pricing Calculator Estimate the cost of a planned configuration Before

Azure Migrate business case Compare migration scenarios and modeled on-premises/Azure costs; beyond current AZ-900 cost-tool objective Before migration

  • Cost Management + Billing Track, analyze, and report actual spend After
  • Budgets & Alerts Notify or trigger actions when spend nears a threshold After
  • Azure Advisor (Cost) Recommend right-sizing and reservation purchases After

Common Trap: The Pricing Calculator estimates a proposed deployment, while Cost Management analyzes existing spend, and Azure Migrate can model a migration business case; the current AZ-900 cost objective names the Pricing Calculator, not a standalone TCO calculator. Match the tool to whether the scenario is planning, comparing, or monitoring — exam stems hinge on that distinction.