Study guide
3.1 Factors That Affect Azure Costs
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
3.1 Factors That Affect Azure Costs
Key Takeaways Explain This Topic AI
Azure costs depend on service, usage, region, data-transfer route, subscription/offer, and any Marketplace or license charges.
Inbound transfer is generally free; outbound and inter-region charges depend on the service, route, and current price sheet.
Azure Hybrid Benefit can reduce eligible licensing costs under current product terms; savings are not a fixed percentage.
Reservations and savings plans involve commitments; Spot VMs use reclaimable capacity with variable savings.
Right-size, deallocate unused compute, and inspect retained disks, IPs, and backups when optimizing costs.
Last updated: October 2026
Quick Answer: Azure bills on a consumption-based (pay-as-you-go) model. Your cost depends on which resource (resource type), how much you run it (usage), where you run it (region), how much data leaves Azure (outbound bandwidth), your subscription type, and any third-party Marketplace charges. The big savings levers are Reserved Instances, Savings Plans, Azure Hybrid Benefit, Spot VMs, and right-sizing.
The Six Primary Cost Factors
AZ-900 phrases these questions as "Which factor affects cost?" or "What can reduce cost?" Use the factors below to reason through costs. The official outline asks about factors affecting Azure costs, but it does not prescribe a six-item list.
1. Resource Type
Each service has its own meter and unit of measure. A meter is the thing Azure counts; the rate per meter is set per region.
- Resource What you pay for
- Virtual Machine (VM) Per-minute compute by size/series, plus OS license, plus attached managed disks
- Blob Storage Per GB stored + per 10,000 transactions + tier (Hot/Cool/Cold/Archive)
- Azure SQL Database Per vCore-hour or DTU-hour + provisioned storage
App Service Paid App Service plans bill for provisioned plan capacity even with zero traffic; a free tier also exists
Azure Functions (Flex Consumption; the Consumption plan is legacy) Per execution + execution time and memory used
- Bandwidth Usually outbound transfer by route and volume; check service-specific rates
- 2. Usage / Consumption
You pay for what you consume: VM compute is billed per full minute, storage per GB-month, transactions per operation, and egress per GB. Stopping (deallocating) a VM stops compute charges, but you still pay for the attached disks.
3. Region
The same VM SKU can have different prices in different regions. Use the Azure Pricing Calculator for a current comparison instead of assuming a particular region is always cheapest. Choosing a region is therefore both a latency/compliance decision and a cost decision.
4. Bandwidth (Data Transfer)
- Direction Cost
- Inbound (into Azure) Generally free, subject to the service and route
- Outbound (Azure → internet) Often charged by volume, with offer-specific allowances
- Between regions Often charged; check the source, destination, and service
- Within a region / zones Some routes or services charge; verify the architecture
Trap: Candidates assume "data transfer is free." Inbound is generally free, while egress and cross-region replication may carry charges — a key reason geo-redundant designs cost more.
5. Subscription Type
Pay-as-you-go — standard rates, no commitment.
Enterprise Agreement (EA) — negotiated volume pricing for large organizations.
Cloud Solution Provider (CSP) — a Microsoft partner manages and bills the subscription.
Free Account — 12 months of popular free services + a USD 200 credit usable for 30 days for eligible new customers + selected always-free services under current terms.
Visual Studio subscribers — eligible for discounted Dev/Test pricing (no Windows license charge on VMs).
6. Azure Marketplace
Third-party (non-Microsoft) software and managed services purchased through the Marketplace bill on top of your Azure usage and may have separate licensing terms. A firewall appliance or a managed database from a partner appears as a distinct line item and may not be covered by your Microsoft volume agreement, so it is easy to overlook when forecasting spend.
CapEx vs OpEx Framing
AZ-900 connects cost factors to the capital expenditure (CapEx) versus operational expenditure (OpEx) distinction. On-premises servers are CapEx: a large up-front purchase that depreciates. Azure consumption is OpEx: a variable, ongoing bill with no up-front asset. Reservations are a hybrid — you commit to OpEx in advance to capture a discount, but you do not buy hardware. Understanding which strategy shifts spend from CapEx to OpEx (and why finance teams favor OpEx for agility) is a core cost idea.
- Model Spend pattern Azure example
- CapEx Up-front, depreciated Buying physical servers
- OpEx Pay-as-you-go, variable Pay-as-you-go VMs and storage
- Committed OpEx Pre-committed for a discount Reservations and Savings Plans
- Cost-Optimization Strategies
- Azure Hybrid Benefit
Eligible existing Windows Server or SQL Server licenses can reduce Azure licensing cost under Azure Hybrid Benefit. Check the current product and Software Assurance/subscription eligibility rules before applying it.
- Eligible license Possible effect
- Windows Server May reduce eligible VM licensing charges
- SQL Server May reduce eligible SQL licensing charges
- Combined with a reservation Savings depend on eligibility, usage, and current prices
- Reservations, Savings Plans, and Spot
- Option Commitment Max discount Flexibility
- Reservations Usually 1 or 3 years Varies by offer Applies to eligible reserved scope
- Savings Plans 1 or 3 years Varies by offer Eligible compute usage up to committed spend
- Spot VMs None Variable; up to 90% advertised Can be evicted when capacity is needed
- Right-Sizing and Auto-Shutdown
A dev VM deallocated outside business hours can reduce its compute-hours, but disks and other retained resources still bill; the total saving depends on its cost mix. Auto-shutdown is built into the VM blade in the portal. Azure Advisor can surface underutilized resources and cost recommendations; verify each recommendation before deleting anything.
Choosing the Right Lever (Worked Scenario)
Suppose a team runs a steady production web tier 24/7 and a separate analytics cluster that only runs interruptible nightly jobs. The optimal mix is: a 3-year Reservation or Savings Plan for the always-on production tier (predictable demand, subject to commitment pricing), and Spot VMs for the analytics cluster (interruptible, with variable Spot savings). If those production VMs run Windows Server with Software Assurance, layer Azure Hybrid Benefit on top of the reservation to remove the OS license charge. Finally, set auto-shutdown on every developer's personal test VM.
This single design combines several optimization levers in one multi-part scenario.
Storage Tiering as a Cost Lever
Blob storage tiers also drive cost. Match access patterns to Hot , Cool , Cold , or Archive . Archive often has lower storage cost but rehydration delay, retrieval charges, and retention considerations; compare total costs before tiering. Tier changes require planning: an archived blob is offline until it is rehydrated, which can take time and incur charges. Do not use Archive when immediate access is required.
On the Exam: Distinguish the three commitment models: Reservations (best for fixed size/region), Savings Plans (flexible across families), Spot (deepest discount, evictable). Azure Hybrid Benefit requires eligible existing licensing under current product terms; it is not a generic discount switch.