AZ-900 Study Plan

Start with the active skills outline

Use Microsoft's AZ-900 study guide measured as of July 20, 2026. It has three domains: Cloud concepts, Azure architecture and services, and Azure management and governance. The percentages are ranges, not a promise of the question count on your exam. Use them to plan attention while adjusting for your own weak areas.

Print or copy the task bullets into a tracker. Mark each item as known, partly known, or unfamiliar. ‘Known’ means you can explain the concept without looking at a definition and choose it in an example. Recognizing a product name from work or a video is not enough. A fundamentals exam often tests whether you can distinguish similar services and match one to a need.

Take Microsoft's Practice Assessment after you have reviewed the outline once. It can reveal where additional study is needed. Microsoft says practice questions are not the same as live exam questions and do not represent the exam's length or complexity. Treat the result as a diagnostic, not a guarantee or required pass percentage.

Choose a realistic study window

Microsoft does not prescribe a fixed AZ-900 study-hour requirement. A candidate who already works with infrastructure or Azure may need a short review; someone new to IT may need time to learn basic terms and relationships. Use your diagnostic to estimate the scope, then choose a calendar that leaves room to review and practice.

A four-week schedule can suit a candidate with a technology background and a few defined gaps. Week one reviews cloud concepts and shared responsibility. Week two covers Azure architecture, geography, and resource hierarchy. Week three studies compute, networking, storage, identity, and security. Week four covers management and governance, then uses mixed practice and a timed session. This schedule is illustrative, not a promise that four weeks works for everyone.

An eight-week schedule offers more spaced repetition. Use weeks one and two for cloud concepts; weeks three and four for Azure architecture and services; weeks five and six for management, governance, and monitoring; week seven for mixed scenarios and comparison questions; and week eight for review, practice assessment, and time management. Spend more study blocks on topics marked new or partly known.

A longer plan may suit a candidate without technical experience or with limited weekly time. Add foundational sessions on what compute, networks, storage, identity, and applications do before learning Azure product names. Then move through the official domains. The calendar can be longer without more total hours if sessions are small, or more intensive if study time is available. Do not mistake the example schedule for an official Microsoft recommendation.

Study Cloud concepts

Learn public, private, and hybrid cloud models by identifying the kind of workload or constraint each may fit. Compare IaaS, PaaS, and SaaS by what the provider manages and what the customer retains. Use the shared responsibility model to explain why moving a server to Azure does not remove customer duties for identity, data, configuration, and appropriate access.

For each cloud benefit, create a concrete example. Scalability can help adapt capacity to changing demand. High availability concerns continued service access. Reliability and predictability relate to consistent operation, but they are not automatic results of buying cloud services. A design must use the relevant service features and be operated properly.

Compare consumption-based pricing with upfront purchases. Ask what changes when usage rises or falls and how an organization can monitor costs. A short scenario might describe a development environment used only during working hours. The cost conversation includes resource size and run time; a cloud move is not automatically cheaper if unused resources stay active.

Study Azure architecture and services

This is the largest published domain range. Organize it into geography and resource hierarchy, compute and networking, storage and migration, and identity and security. For each Azure service, learn the need it addresses and one close alternative. Contrast regions and availability zones, subscriptions and resource groups, virtual machines and containers, and VPN Gateway and ExpressRoute.

Draw a simple Azure environment with a management group, subscription, resource group, and resources. Add a virtual network and a compute service. Use the drawing to answer where access, billing, or organization applies. The visual structure can clarify why a subscription is not just a resource group with a different name.

Study storage by comparing the service and access pattern: object or blob storage, files, queues, and disks serve different needs. Review tiers and redundancy, then learn which tools support data transfer or migration. A candidate should know the purpose of AzCopy, Storage Explorer, File Sync, Azure Migrate, and Data Box without memorizing detailed command syntax.

For identity, separate authentication from authorization. Learn Microsoft Entra ID, multifactor authentication, single sign-on, passwordless methods, external identities, and Conditional Access. Compare RBAC's resource permissions with broader security ideas such as Zero Trust and defense in depth. Defender for Cloud supports security posture and threat-protection capabilities; it does not replace every identity or governance control.

Study Management and governance

Learn how a candidate can estimate and monitor cost. The pricing calculator estimates usage, cost management capabilities help analyze spend, and tags add metadata for organization and reporting. A tag does not enforce a budget or grant permission. Practice selecting the right tool for a cost question.

Compare governance controls: Azure Policy audits or enforces configuration standards; resource locks help prevent certain changes or deletion; RBAC determines who has permission to act. Microsoft Purview has data governance and compliance capabilities. These controls can work together, but they solve different problems. A question about preventing deletion is not necessarily asking for a role assignment.

Know the main management and deployment options: portal, Cloud Shell, CLI, PowerShell, Azure Arc, infrastructure as code, Azure Resource Manager, and ARM templates. The goal is to describe their purpose and when a team might use them, not perform every command. Monitoring distinctions also matter: Advisor recommendations, Service Health notifications, and Azure Monitor data are not interchangeable.

A weekly study-session pattern

A useful session has three parts: learn a small set of concepts, retrieve them without notes, and apply them to a new example. For instance, study Azure Policy, RBAC, and resource locks, close the guide, explain each from memory, and then decide what a company should use to enforce a configuration, limit who can change it, or prevent deletion.

Keep an error log with the topic, your selected answer, why it seemed plausible, and the distinction you missed. Review guessed correct answers as well as wrong ones. If you confused Service Health and Azure Monitor, write what each reports and use a fresh example. If you picked an answer because its name sounded familiar, study the service's role rather than its label.

Space review over several days. Return to a topic after you have forgotten some of the wording. Mixed practice helps because the question will not announce its domain. Once you know each concept separately, practice choosing between neighboring services under a time limit.

Use official practice resources well

Microsoft's Practice Assessment is free when available for the exam. It is meant to show the style and help identify knowledge gaps, not to reproduce the complete length or complexity of the live exam. Read explanations, return to the study guide, and then test the concept with another example.

Use the Microsoft exam sandbox to learn how the interface works. It demonstrates examples of Microsoft question types, navigation, the review marker, and the timer. It does not guarantee those exact types will appear on AZ-900. The sandbox can reduce interface surprises without replacing content study.

Microsoft Learn access is unavailable during fundamentals exams. Do not plan to search for a definition during AZ-900. Practice recalling what each service does before the exam. You may use the official Microsoft Learn documentation while studying, but you need to understand the ideas rather than search quickly under a clock.

Final review and readiness

Near the exam, complete a fresh mixed session within the 45-minute testing time. Review errors afterward and check whether you can finish without rushing every question. The full appointment is 65 minutes, which includes instructions and other steps. Practice timing is about maintaining attention and decision quality, not recreating the exact exam interface.

You are better prepared when you can explain every domain in plain words, distinguish closely related services, and apply the concepts to new examples. A strong readiness signal is consistent reasoning on unfamiliar questions and fewer repeated errors. No practice assessment score guarantees the scaled passing score of 700.

If a major domain remains unfamiliar, revise the appointment date under the provider's terms or move study time to that gap. If your weaknesses are narrow, review them and keep all domains in rotation. A practical plan responds to what you can demonstrate, not the number of pages you have completed.

The AZ-900 exam has a broad but foundational scope. The most effective preparation is a current outline, accurate service comparisons, active recall, and examples tied to real requirements. Learn why a service fits and what responsibility remains with the customer; that understanding transfers better than memorizing an answer key.