Microsoft Certified: Azure Fundamentals (AZ-900) is the only Azure certification that requires no hands-on experience or prior knowledge whatsoever. Without writing a single line of code, it checks whether you understand why an organization moves to the cloud and what role Azure plays in that move. A traveler who has just landed in an unfamiliar country doesn't need the back alleys mapped out first — they need the overall layout. AZ-900 plays exactly that role, and it gives you solid footing before moving on to hands-on certifications like AZ-104 or AZ-204.
Why This Exam Remains the First Stop for Everyone
A new hire's first move at a company is usually to study the org chart, because knowing who does what makes every later collaboration easier. AZ-900 draws that org chart for the world of Azure. Non-technical roles in sales, marketing, and project management can take it just as easily as developers or infrastructure engineers building a foundation before their next certification. There are no prerequisites, and true to its Fundamentals level, it never needs to be renewed once earned.
Exam Format: Short but Wide in Scope
Much like a routine physical runs through several systems quickly, AZ-900 spends about 85 minutes covering roughly 40 to 60 questions across the breadth of cloud computing. The passing score is 700 out of 1000, and the exam fee is 99 USD. Question formats mix single-choice, multiple-choice, drag-and-drop, and case-study items. Because the question count is relatively small, a single mistake carries more weight than on longer exams, so lock in the questions you know first and keep a running table of service names you tend to confuse.
Domain 1: Describe Cloud Concepts (25-30%)
Imagine a neighborhood bakery suddenly scaling into a nationwide chain — instead of buying a new oven for every location, it makes more sense to rent capacity as needed, and this domain covers exactly that shift. The essentials are moving from CapEx to OpEx, the distinction between IaaS, PaaS, and SaaS, cloud benefits like high availability, scalability, reliability, and predictability, and the shared responsibility model. The related posts Cloud Computing Concepts, Benefits of Cloud Services, and Cloud Service Types walk through concrete examples for each service model.
Domain 2: Describe Azure Architecture and Services (35-40%)
This is the highest-weighted domain, and like stacking LEGO bricks into a building, it's about layering compute, networking, and storage services on top of the basic structure of regions, availability zones, and resource groups. Frequently tested points include the difference between Virtual Machines, containers, and App Service, the roles of Virtual Network and VPN Gateway, and the distinction between Blob Storage and Azure Files. The related posts Core Azure Architecture, Compute and Networking, and Storage Services go deeper into how to choose between services.
Domain 3: Describe Azure Management and Governance (30-35%)
Just as a household keeps a budget ledger and installs window locks, this domain is about running an Azure environment safely and predictably. The core topics are authentication through Microsoft Entra ID, security features like multi-factor authentication and Conditional Access, governance through Azure Policy and management groups, tracking health with Azure Monitor, and controlling spend with budget alerts and the pricing calculator. The related posts — Identity, Access, and Security, Governance and Compliance, Cost Management Fundamentals, Monitoring and Service Health, and Resource Deployment and Management — cover this domain across five dedicated posts.
Where to Go After AZ-900
Just as a finished foundation supports floors built for different purposes, the path after AZ-900 splits depending on your goal. Infrastructure engineers who operate servers, networks, and storage typically move to the Associate-level AZ-104; developers who build and deploy applications move to AZ-204; and anyone aiming to design cloud architecture moves to AZ-305. Concepts learned in AZ-900 — regions, resource groups, the shared responsibility model — get assumed as prior knowledge in all three, so skipping this exam and jumping straight into an Associate-level one often means getting stuck on basic terminology.
A Study Order for Beginners, and Common Mistakes
Walking an unfamiliar city without a map means retracing the same streets twice. If you're new to the cloud, start with Domain 1 (cloud concepts) to lock down IaaS, PaaS, SaaS, and the shared responsibility model, then move into Domain 2 (architecture and services) and build a resource group in the Azure portal yourself to get a feel for it, and finish with Domain 3 (management and governance) by layering in Entra ID and Azure Policy. The most common mistake is memorizing service names without ever clicking through the portal — spending a few hours creating and deleting a resource group on a free trial account makes concepts stick far longer than reading alone. A second common mistake is memorizing IaaS, PaaS, and SaaS by service name rather than by scope of management; reorganizing them around the question "what do I have to manage myself here?" clears up most of the confusion.
Exam Key Takeaways
"Pay only for what you use, no upfront investment" -- OpEx, the core benefit of moving to the cloud "Rent infrastructure, manage everything above it yourself" -- IaaS "Platform provided, you only write application code" -- PaaS "Use finished software as-is" -- SaaS "Service keeps running even during a failure" -- high availability "Resources scale up or down with demand" -- scalability "Security responsibilities split between Microsoft and the customer" -- shared responsibility model "Verifies user identity and controls access" -- Microsoft Entra ID "Enforces rules consistently across an organization" -- Azure Policy "A logical container for organizing related resources" -- resource groups "Estimates cost before you actually spend anything" -- Azure pricing calculator "Tracks resource health in real time" -- Azure Monitor
AZ-900 tests concepts, not code, so instead of memorizing service names one by one, organize each one around the question "what does this service manage on my behalf?" — that single reframe untangles even the trickiest question on exam day.