Home/ cloud-computing/ Microsoft Certified: Azure Fundamentals/ Cheat Sheet
Microsoft Certified: Azure Fundamentals

Microsoft Certified: Azure Fundamentals Cheat Sheet

AZ-900 Tests Azure Service Understanding and Cloud Concepts — Not Configuration

This is a foundational exam. The traps are in shared responsibility, service model selection, and cost management concepts — not technical depth.

Check Your Readiness →
Among the harder certs
Avg: Approximately 68–73%
Pass: 750 / 1000
Most candidates understand Microsoft Certified: Azure Fundamentals concepts — and still fail. This exam tests how you apply knowledge under pressure.

AZ-900 Domain Areas

AZ-900 is a breadth exam across six domain areas. Most questions are conceptual — know what each Azure service category does, when to use each cloud model, and how Azure's management hierarchy works.

  1. 01
    Cloud Concepts — Benefits of cloud, cloud models (public/private/hybrid), consumption-based model
  2. 02
    Azure Architecture — Regions, availability zones, resource groups, management hierarchy
  3. 03
    Azure Services — Compute, networking, storage, databases, AI, DevOps
  4. 04
    Azure Management — Portal, CLI, PowerShell, ARM templates, Azure Arc
  5. 05
    Cost Management — Pricing calculator, Cost Management + Billing, TCO calculator
  6. 06
    Governance & Compliance — Azure Policy, Blueprints, RBAC, Trust Center

Wrong instinct vs correct approach

A company wants to ensure all Azure VMs have a specific tag applied
✕ Wrong instinct

Train administrators to apply tags consistently

✓ Correct approach

Use Azure Policy with a deny or append effect to enforce tag requirements — relying on manual compliance is unreliable at scale

A startup wants to estimate the cost of moving to Azure
✕ Wrong instinct

Create a trial subscription and estimate from the portal

✓ Correct approach

Use the Azure TCO Calculator to compare current on-premises costs with estimated Azure costs; use the Pricing Calculator to estimate specific service costs before committing

An organization needs to ensure compliance with industry regulations across all subscriptions
✕ Wrong instinct

Apply Azure Policy at each subscription individually

✓ Correct approach

Apply Azure Policy at the Management Group level — policies cascade to all child subscriptions, ensuring consistent enforcement without per-subscription configuration

Know these cold

  • Regions = geographic areas; Availability Zones = separate datacenters within a region
  • Shared responsibility shifts — aaS (more customer) → PaaS → SaaS (more Microsoft)
  • Azure Policy = enforce resource standards; RBAC = control who can act on resources
  • Management Groups → Subscriptions → Resource Groups → Resources (hierarchy order)
  • Reservations for predictable compute; Spot for interruptible; Hybrid Benefit for existing licenses
  • TCO Calculator for on-premises vs. Azure comparison; Pricing Calculator for Azure cost estimation
  • Azure Arc extends Azure management to on-premises and multi-cloud environments

Can you answer these without checking your notes?

In this scenario: "A company wants to ensure all Azure VMs have a specific tag applied" — what should you do first?
Use Azure Policy with a deny or append effect to enforce tag requirements — relying on manual compliance is unreliable at scale
In this scenario: "A startup wants to estimate the cost of moving to Azure" — what should you do first?
Use the Azure TCO Calculator to compare current on-premises costs with estimated Azure costs; use the Pricing Calculator to estimate specific service costs before committing
In this scenario: "An organization needs to ensure compliance with industry regulations across all subscriptions" — what should you do first?
Apply Azure Policy at the Management Group level — policies cascade to all child subscriptions, ensuring consistent enforcement without per-subscription configuration

Common Exam Mistakes — What candidates get wrong

Confusing Azure regions with availability zones

A region is a geographic area (e.g., East US). An availability zone is a physically separate datacenter within a region. Services deployed across AZs achieve higher availability than single-datacenter deployments — candidates mix these up in HA design questions.

Misidentifying the shared responsibility model boundaries

Microsoft manages the physical infrastructure, hypervisor, and platform services. Customers manage identity, data, devices, and application-level security. This boundary shifts based on IaaS/PaaS/SaaS model — candidates often place too much responsibility on Microsoft.

Confusing Azure Policy with RBAC

Azure Policy enforces resource configuration standards (e.g., only allow certain VM sizes, require tags). RBAC controls who can do what with resources. They work together but serve different governance purposes.

Treating all Azure cost savings tools as equivalent

Azure Reservations for committed compute (1-3 years); Azure Hybrid Benefit for Windows Server/SQL license reuse; Spot VMs for interruptible workloads; Dev/Test pricing for non-production. Selecting the wrong savings mechanism for the scenario is a common error.

Not understanding the Azure management hierarchy

Management Groups → Subscriptions → Resource Groups → Resources. Policies and RBAC applied at higher levels cascade down. Candidates who don't understand this hierarchy miss governance and cost management questions.

AZ-900 covers more governance and cost management than most candidates expect. Test your Azure fundamentals now.