SkarpChapter 12 of 20
Azure Pricing, Cost Management, and Service-Level Agreements
Trace how Azure resources generate cost, how SLAs are expressed, and which tools help you estimate and control spending for predictable cloud bills.
Azure Pricing Fundamentals: How Costs Are Generated
How Azure Costs Are Generated
In Azure, almost every resource can generate cost. For AZ-900, focus on what drives the bill: service type, region, usage/time, and data transfer.
Service Type and SKU
Each service has pricing tiers or SKUs. Bigger or more capable SKUs (more vCPUs, RAM, features, throughput) cost more. You pay per unit of capacity or operations.
Region Effects
Prices vary by region because underlying costs differ. The same VM can cost slightly more or less in different regions. Region choice affects both cost and service availability.
Usage and Time
Most services are pay-as-you-go: billed per second/hour, per GB-month stored, or per request. Stopping or deleting compute often stops compute charges, but storage may keep costing.
Data Transfer Costs
Data into Azure is usually free. Data out of Azure or across regions is often charged. Cross-region and internet egress can be major hidden costs and common exam traps.
CapEx vs OpEx
Azure shifts you from capital expense (buying servers) to operating expense (paying for usage). This gives flexibility and scalability but requires active cost management.
Key Factors Influencing Azure Costs
Cost Driver Checklist
For each workload, think: service type, size/performance, redundancy, OS/licensing, network/data transfer, and discounts like reservations or savings plans.
Size and Performance
Bigger VMs and higher performance tiers in PaaS (Premium, Business Critical) cost more. Scaling out with more instances and scaling up both increase spend.
Storage Redundancy and Tiers
LRS, ZRS, GRS, GZRS and hot/cool/archive tiers all have different prices. More durability and cross-region replication usually means higher cost.
Licensing and OS
Windows VMs include OS licensing in the price and usually cost more than Linux. Some services bundle SQL or allow bring-your-own-license via Azure Hybrid Benefit.
Network and Data Transfer
Outbound data, cross-region traffic, VPN, and ExpressRoute can add significant cost. Egress is a classic hidden cost in exam scenarios.
Reservations, Savings, and Free Tiers
1- or 3-year reservations and savings plans lower the rate but reduce flexibility. Free tiers help for learning, but production workloads usually exceed free limits.
Worked Example: Comparing Two Azure Architectures by Cost Drivers
Scenario A: Single Region
2 Windows VMs, 1 load balancer, 1 LRS storage account, 1 SQL DB in West Europe, 200 GB/month outbound. Main costs: compute, single-region storage, single DB, moderate egress.
Scenario B: Multi-Region HA
4 Windows VMs across 2 regions, global routing, GZRS storage in each region, 2 geo-replicated SQL DBs, 400 GB/month outbound. More resilience and complexity.
Comparing Cost Drivers
Scenario B has more VMs, higher redundancy (GZRS, geo-replication), and more outbound traffic. Expect significantly higher cost in exchange for better availability.
Exam Takeaway
On AZ-900, recognize that multi-region, geo-replication, and higher redundancy usually increase cost unless balanced by smaller sizes or long-term commitments.
Azure Pricing Calculator: Estimating Solution Costs
What the Pricing Calculator Is
The Azure Pricing Calculator is a web tool that lets you estimate monthly costs by configuring services, regions, SKUs, and usage before you deploy.
What It Lets You Do
You pick services, set region and instance size, choose redundancy and tiers, enter usage, and see per-service and total estimated monthly costs.
High-Level Steps
1) Add services, 2) choose region, 3) configure SKUs/options, 4) estimate usage, 5) review and adjust totals. It supports exporting/sharing estimates.
Exam-Relevant Purpose
Use the Pricing Calculator for planning and comparison, not for real-time spend tracking. Monitoring and control are handled by Azure Cost Management.
Thought Exercise: Using the Pricing Calculator for a Simple App
Imagine you are planning a small student project website hosted on Azure. You want to keep costs low but still be realistic.
Design:
- 1 small Linux web server VM
- 1 storage account for images (LRS, hot tier)
- 1 small Azure SQL Database
- Users are mostly in your home region
Your task (no need to actually open the calculator, just think through it):
- List the services you would add to the Pricing Calculator.
- For each service, decide:
- Which region you would choose and why.
- What size/tier you would start with (e.g., small VM, Basic SQL tier) to keep costs low.
- Any redundancy choices (e.g., LRS vs GRS) and why.
- Think about usage assumptions:
- VM: Will it run 24/7 or only during lab hours?
- Storage: How many GB of images do you expect?
- SQL: Do you expect heavy or light usage?
- Now imagine you double the number of users. Which parameters would you adjust in the calculator to see the new cost?
Write down your answers or say them out loud. This is exactly the kind of reasoning AZ-900 expects: not exact prices, but a clear understanding of which knobs affect cost.
Azure Cost Management and Billing: Monitoring and Controlling Spend
What Cost Management and Billing Is
Azure Cost Management and Billing is the built-in portal area to track, analyze, and optimize actual spending, and to manage invoices and payment details.
Cost Management Side
Cost Management handles usage and cost analysis, budgets, alerts, and recommendations. It helps you understand and control where money is going.
Cost Analysis and Budgets
Cost analysis shows charts by subscription, resource group, service, or tag. Budgets let you set spend limits and trigger alerts at chosen percentages.
Recommendations and Exports
Azure Advisor integrates to suggest savings like rightsizing VMs or removing idle resources. You can export cost data or use APIs for deeper analysis.
Billing Side
Billing views invoices, payment methods, and billing scopes (like Microsoft Customer Agreement or Enterprise Agreement) that group subscriptions.
Exam Contrast
Know the distinction: Pricing Calculator is for planning estimates; Cost Management and Billing is for monitoring and controlling real, ongoing spend.
Hands-On Mindset: Using Budgets, Tags, and Policies to Control Cost
Budgets and Alerts
Budgets in Cost Management let you set spend limits per subscription or resource group and trigger alerts at thresholds. They warn but do not auto-stop resources.
Tagging for Cost Allocation
Tags like Environment, Department, or Project can be attached to resources. Cost analysis can group by tags to see who or what is driving spend.
Azure Policy for Cost Governance
Azure Policy enforces rules so resources stay compliant with standards and SLAs. You can require tags, restrict regions, or block expensive SKUs.
Governance Toolkit
Combining budgets, tags, and Policy gives organizations a basic cost governance toolkit: detect overspend, attribute it, and prevent noncompliant deployments.
Service-Level Agreements (SLAs): Availability and Uptime
What an SLA Is
An Azure SLA states the expected availability (e.g., 99.9%) for a service and what service credits apply if Microsoft does not meet that target.
Availability Percentages
Common values are 99.9%, 99.95%, 99.99%. Higher percentages mean less allowed downtime per month, measured over a billing period.
Patterns in Azure SLAs
Single-instance services often have weaker or no financial SLA. Redundant instances across zones or sets typically qualify for higher SLAs.
Why SLAs Matter
SLAs drive architecture and cost. Higher uptime requirements usually require redundancy and premium tiers, which increase cost but improve resilience.
Combining SLAs for a Solution
Series Components and SLAs
When an app depends on multiple services in series, the overall SLA is roughly the product of each SLA (as decimals), so it is slightly lower than each individual one.
Worked SLA Combination
If App Service is 99.95% and SQL Database is 99.99%, combined SLA ≈ 0.9995 × 0.9999 ≈ 0.9994, or about 99.94% end-to-end availability.
Effect of Many Dependencies
The more services you chain, the more the overall SLA drops, even if each one has a high SLA. Every dependency is another potential point of failure.
Redundancy Helps
Parallel redundant components (e.g., multiple instances behind a load balancer) can increase effective availability, because all would have to fail together.
Exam Tip
On AZ-900, if multiple dependent services are mentioned, expect the solution SLA to be lower than any one service unless explicit redundancy is described.
Quiz: Pricing Calculator vs Cost Management
Check your understanding of Azure pricing tools.
Which statement best describes the difference between the Azure Pricing Calculator and Azure Cost Management and Billing?
- The Pricing Calculator estimates future costs before deployment, while Cost Management and Billing tracks and analyzes actual spending after deployment.
- The Pricing Calculator is used only by Microsoft employees, while Cost Management and Billing is for customers.
- The Pricing Calculator shows invoices, while Cost Management and Billing is used only to buy reservations.
- Both tools are used only for pay-as-you-go subscriptions and cannot be used with enterprise agreements.
Show Answer
Answer: A) The Pricing Calculator estimates future costs before deployment, while Cost Management and Billing tracks and analyzes actual spending after deployment.
The Azure Pricing Calculator is a planning tool for estimating future costs based on chosen services, regions, and usage. Azure Cost Management and Billing is used to monitor, analyze, and control actual and forecasted spending, and to manage invoices and payment methods.
Quiz: Cost Drivers and SLAs
Test your understanding of Azure cost drivers and SLAs.
A company wants to increase the SLA of its web application from 99.9% to 99.99%. Which design change is most aligned with how Azure SLAs work and what will it likely do to cost?
- Move the app to a larger VM size in the same region; this will always increase the SLA without changing cost.
- Deploy multiple instances of the app across Availability Zones and use a load balancer; this will likely increase both SLA and cost.
- Turn off redundancy and use only one instance of each service; this will increase SLA and lower cost.
- Move all resources to a cheaper region; this will always increase SLA while reducing cost.
Show Answer
Answer: B) Deploy multiple instances of the app across Availability Zones and use a load balancer; this will likely increase both SLA and cost.
Using multiple instances across Availability Zones with a load balancer increases resilience and qualifies for higher SLAs, but requires more resources, so cost usually rises. Larger VM sizes alone do not necessarily change the SLA, and reducing redundancy typically lowers availability.
Key Terms Review: Pricing, Cost Management, and SLAs
Flip the cards to reinforce key concepts from this module.
- Azure Pricing Calculator
- A web-based tool used to estimate future Azure costs by selecting services, regions, SKUs, and usage assumptions before deployment.
- Azure Cost Management
- The part of Azure Cost Management and Billing focused on analyzing, monitoring, and optimizing actual and forecasted Azure spending using cost analysis, budgets, alerts, and recommendations.
- Azure Billing
- The part of Azure Cost Management and Billing that manages invoices, payment methods, and billing scopes such as subscriptions under a Microsoft Customer Agreement or Enterprise Agreement.
- Cost Driver: Region
- The Azure region where a resource runs; different regions can have different prices for the same service due to varying infrastructure and energy costs.
- Cost Driver: Data Egress
- Charges that apply when data leaves Azure to the internet or between regions; inbound data is usually free, while outbound can significantly impact cost.
- Budget (in Cost Management)
- A configurable spending target for a subscription or resource group that can trigger alerts when actual or forecasted costs exceed defined thresholds.
- Tag (for cost allocation)
- A key-value pair attached to Azure resources (e.g., Department=Finance) that allows grouping and reporting of costs by business dimension.
- Azure Policy (cost-related use)
- Used to enforce rules like required tags, allowed regions, or allowed SKUs so that resource deployments stay compliant with cost and governance standards.
- Service-Level Agreement (SLA)
- Microsoft's formal commitment describing the expected availability of an Azure service and the service credits provided if that availability is not met.
- Combined SLA for a Solution
- The effective availability of an application that depends on multiple services; for series dependencies, it is approximately the product of individual SLAs and is lower than each one.
Wrap-Up Reflection: Connecting Costs, Governance, and SLAs
Take a minute to connect this module to what you already know from earlier in your path (storage and identity).
Reflect on these prompts:
- Storage choices and cost
- Think of at least two ways your choice of Azure Storage redundancy (LRS, ZRS, GRS, GZRS) can affect both cost and SLA/durability.
- Identity and cost governance
- How can Microsoft Entra ID roles and role-based access control help prevent uncontrolled spending (for example, who is allowed to create large VMs)?
- Design trade-offs
- Imagine an app that does not need 24/7 availability. How could you adjust its architecture or schedules to reduce cost (for example, auto-shutdown dev/test VMs at night) without violating realistic SLAs?
- Your next step in this course
- After this module, your Skarp diagnostic and upcoming mock exams will probe these ideas. As you answer questions, ask yourself: Which design choice is cheaper? Which one has a higher SLA? Which tool helps me estimate vs monitor?
Write short bullet answers for each prompt. This reflection will make the upcoming practice questions and spaced review items much easier.
Key Terms
- Tag
- A key-value pair attached to Azure resources that can be used to group and report costs by business dimensions such as department, project, or environment.
- Budget
- A configurable spending target in Azure Cost Management that can trigger alerts when actual or forecasted costs exceed defined thresholds.
- Redundancy
- The practice of storing or running multiple copies of data or services (for example, across zones or regions) to improve availability and durability, often at higher cost.
- Data Egress
- Data that leaves Azure, such as traffic from Azure to the public internet or between Azure regions, which often incurs additional charges.
- Reservation
- A pricing option where you commit to using certain Azure resources (such as virtual machines) for a 1- or 3-year term in exchange for a lower rate compared to pay-as-you-go.
- Availability
- The percentage of time a service is operational and accessible, typically measured over a month and expressed as 99.9%, 99.95%, 99.99%, and so on.
- Savings Plan
- A flexible discount model where you commit to a consistent amount of compute usage over 1 or 3 years, receiving lower prices across eligible compute services.
- Azure Pricing Calculator
- A web-based tool used to estimate future Azure costs by selecting services, regions, SKUs, and usage assumptions before deployment.
- Service-Level Agreement (SLA)
- Microsoft's formal commitment describing the expected availability of an Azure service and the service credits provided if that availability is not met.
- Azure Cost Management and Billing
- The combined Azure experience that covers both cost management (analyzing and optimizing usage and spend) and billing (invoices, payment methods, and billing scopes).