AZ-900 names all three of its skills domains with the word describe. The exam tests whether you can tell apart ideas that sound alike, so the study plan has to start from the pairs you mix up. Take the free assessment first and write down each pair that trips you. Then spend four weeks on the three domains, in weight order, at about 4 to 6 hours a week, with that list as the syllabus.
What the exam measures, as of July 20, 2026
Microsoft's official AZ-900 study guide lists three skills domains, with weights for the skills measured as of July 20, 2026:
- Describe cloud concepts: 25-30%
- Describe Azure architecture and services: 35-40%
- Describe Azure management and governance: 30-35%
The weights set the week counts, and architecture and services gets the most.
Format facts that shape the plan:
- A score of 700 or greater passes. Technical exam scores are reported on a scale of 1 to 1,000, and the 700 is a scaled score, so it may not equal 70% of the points (exam scoring and score reports).
- You get 45 minutes, and the exam is proctored. If you fail, you can retake it 24 hours after the first attempt. You book through Pearson Vue, or through Certiport if you are a student or an educator (Azure Fundamentals certification page, last updated July 20, 2026). At 45 minutes, timed practice matters.
- The study guide links a free Microsoft Practice Assessment for the style and wording of the questions, and a sandbox where you can explore the exam environment.
- The study guide change log marks the July 20, 2026 update as minor changes to the compute and networking services objectives, the management and deployment tools objectives, and the monitoring tools objectives. Notes written before July may list slightly different items.
Your first hour: take the free assessment and list the pairs you mix up
Take the free AZ-900 assessment without looking anything up. It is free and needs no card. It returns a Readiness Report that scores the attempt and lists your top gaps. Set the score aside for this hour. The job is to name the pairs.
For each miss, write down the pair you confused in your own words. "I picked scalability when the answer was high availability" is a study note you can act on. "Review cloud benefits" is not. Those pairs are where the four weeks should go.
Four weeks, with the heaviest domain in the middle
This plan assumes about 4 to 6 hours a week. Azure architecture and services carries the most weight (35-40%), so it gets two weeks. Cloud concepts (25-30%) comes first because every later domain uses its vocabulary. Management and governance (30-35%) comes last because its tool-matching questions build on the services you meet in weeks 2 and 3.
- Week 1: cloud concepts (25-30%). Cloud computing, the shared responsibility model, cloud models (public, private, hybrid), consumption-based pricing, IaaS, PaaS, SaaS, and the benefits of cloud services. Done when you can explain each model and each benefit in one sentence without notes.
- Week 2: architecture, part one (35-40%). Regions, availability zones, the resource hierarchy (resource groups, subscriptions, management groups), and compute and networking. Done when you can order the hierarchy from the bottom up and choose between VMs, containers, and functions for a described workload.
- Week 3: architecture, part two, then start management and governance. Storage services, tiers, and redundancy options, then identity (Microsoft Entra ID, Conditional Access, RBAC, Zero Trust), then cost management. Done when you can match a storage tier to how often the data is accessed, a redundancy option to where the copies must live, and describe what each identity tool does.
- Week 4: management and governance (30-35%), then mixed review. Governance (Microsoft Purview, Azure Policy, resource locks, tags), deployment and management tools (portal, Cloud Shell, CLI, PowerShell, Azure Arc, ARM templates), and monitoring (Azure Advisor, Azure Service Health, Azure Monitor). Done when you can match each tool to the problem it solves, and a mixed retest no longer trips you on the pairs from your list.
If you have only a week or two, keep the order and compress it. Do not drop the diagnostic or the final mixed retest. They are what tell you whether the compressed version worked.
Cloud concepts (25-30%): match the benefit to the problem in the stem
The stem of a benefit question names the problem it worries about, and you match the benefit to that worry. The pairs to fix first:
- High availability versus scalability. High availability "focuses on ensuring maximum availability, regardless of disruptions or events that may occur" (Microsoft's module). Scalability is the ability to adjust resources to meet demand, adding more for peak traffic and reducing when demand drops. A stem that names an outage or a failed component points to high availability. A stem that names growing or shrinking load points to scalability.
- IaaS, PaaS, SaaS. The outline asks you to identify the appropriate use case for each service type. The deciding split is who manages what. Azure runs the platform, and you keep the decisions above it: your identities, your data, your configuration.
- The shared responsibility model itself. When a question describes a task and asks who handles it, split the task into what Azure operates for you and what you still decide.
This domain is mostly definitions, so practice by explaining each model and each benefit in one sentence without notes, then checking yourself against the Describe cloud concepts learning path.
Architecture and services (35-40%): know what each scope is for
The heaviest domain rewards knowing where each thing sits in the hierarchy and why it exists. From the bottom up: resources live in resource groups, resource groups live in subscriptions, and management groups organize subscriptions. When a question describes a need, ask which level that need belongs to:
- A shared lifecycle and permissions for one app's parts point to a resource group. Microsoft's guidance is to add resources sharing the same lifecycle to the same resource group "so you can easily deploy, update, and delete them as a group" (manage resource groups).
- Billing and a higher-level access boundary point to a subscription.
- Rules across many subscriptions point to a management group. Management group is the tempting option because it is the bigger scope, but it holds subscriptions, not resources.
The outline also asks you to compare containers, virtual machines, and functions. The cues: a workload you manage down to the operating system is a virtual machine, a packaged app that should scale per request is a container, and a short task triggered by an event is a function. For networking, know the pair that separates the two Azure-to-on-premises options. VPN Gateway connects on-premises to Azure over an encrypted tunnel, and ExpressRoute is the dedicated private connection. Storage questions ask you to match a tier to how often the data is accessed and a redundancy option to where the copies must survive.
Three labs from Microsoft's course materials, each listed at 15 to 20 minutes, each needing an Azure subscription (anything you create can incur charges, so delete the resource group when you finish):
- Create a Microsoft Azure resource
- Create a virtual machine and configure it as a web host
- Create a storage blob
Learning path: Describe Azure architecture and services
Management and governance (30-35%): split the tools by the job they do
This domain has four families of tools, and the questions match a job to the tool that does it:
- Cost. The pricing calculator for estimates, Cost Management for what you are already spending, and tags to group and attribute the spend.
- Governance. Microsoft Purview for data governance, Azure Policy for rules about what can exist, and resource locks to stop deletion or change.
- Deployment and management. The portal, Cloud Shell, the CLI, PowerShell, Azure Arc, and ARM templates for repeated, identical deployments.
- Monitoring. Azure Advisor for recommendations, Azure Service Health for platform issues, and Azure Monitor for your own data.
The monitoring tools are where the confusable pairs cluster. Microsoft's docs draw the split this way. Azure Monitor Metrics stores numeric data in a time-series database, and Azure Monitor Logs is the other half of the data platform, where a Log Analytics workspace holds the detailed records you query with Kusto Query Language (KQL) (Azure Monitor logs). So read the job in the stem. A number over time is a metric. A detailed record you query is a log. A notification or action that fires when a condition is met is an alert.
Learning path: Describe Azure management and governance
How you know a weak pair is fixed
Rereading a module feels like progress, but the feeling comes from recognition, not from the ability to tell the pair apart when the question is worded differently. At the end of each week, take questions you have not seen on that domain and check whether the pairs on your list still trip you. The bar is that a pair stops showing up when the question wording changes.
The CramHQ AZ-900 path is built for that retest loop, and it is free with no card required. The path includes lessons, 500+ questions with explanations, flashcards, six practice tests, and a Final Timed Simulation, so the end-of-week retests come from the path. The free assessment's Readiness Report shows your top gaps, and a targeted Pass Plan repair works on one of them.
The readiness call: book or fix one domain
In the last few days, take one fresh mixed timed set from the path and the free Microsoft Practice Assessment that the study guide links. Count only questions you have not seen before, and note which domain the misses come from. If they spread thinly across all three domains, book the exam. If one domain holds most of them, spend a day on that domain and retest before you book.
The AZ-900 readiness check walks through reading those results in more detail.
If AZ-900 is a first step toward an administrator role, the next exam is AZ-104, the Microsoft Azure Administrator exam. After AZ-900, the path lists AZ-104 and AZ-305 as the next steps, and the advice is to start with fundamentals, then move into administrator skills or architecture design when you are ready.