3.1 Factors That Affect Azure Costs

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.

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)

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.

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.

Reservations, Savings Plans, and Spot

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.