AZ-900 Study Guide for Beginners: A Four-Week Plan

Microsoft's current study guide lists skills measured as of July 20, 2026. The exam has three domains: cloud concepts at 25–30%, Azure architecture and services at 35–40%, and Azure management and governance at 30–35%. Use those ranges to keep your plan balanced; the largest domain matters, but no domain is small enough to ignore.

Download or bookmark the official study guide and turn every objective into one of three states: not started, can explain, or can apply in a scenario. The bullets under each objective illustrate what Microsoft may assess, and related topics may also appear. Treat the official outline as the scope boundary and use courses, notes, and questions to learn that scope.

AZ-900 is a beginner certification, but Microsoft describes the intended candidate as a technology professional with experience in an IT area such as infrastructure, databases, or development. If Azure is your first technical topic, allow extra time for networking, identity, storage, and basic operating concepts rather than trying to memorize product names without context.

Begin with public, private, and hybrid cloud; consumption-based pricing; serverless computing; shared responsibility; and the benefits of availability, scalability, reliability, predictability, security, governance, and manageability. Then compare infrastructure, platform, and software as a service.

Use one workload to make the service models concrete. If a company runs its application on Azure virtual machines, the customer still manages the guest operating system and application. A managed application platform shifts more infrastructure work to the provider. With software as a service, the customer mainly manages users, access, configuration, and its data responsibilities.

End the week by explaining who manages the physical datacenter, host, operating system, application, identities, and data in several models. A good answer changes when the service model changes; a memorized slogan does not show that you can apply shared responsibility.

First learn the hierarchy: resources belong to resource groups, resource groups belong to subscriptions, and subscriptions can be organized with management groups. Keep that management hierarchy separate from physical geography such as datacenters, regions, region pairs, sovereign regions, and availability zones.

Then compare compute choices rather than learning them as isolated definitions. Virtual machines offer operating-system control; containers package applications consistently; functions support event-driven serverless execution; and web apps provide managed application hosting. Add scale sets, availability sets, and Azure Virtual Desktop only after you understand the decision each feature supports.

For networking, be able to describe virtual networks, subnets, peering, Azure DNS, VPN Gateway, ExpressRoute, and public versus private endpoints. Draw a simple application with a client, network boundary, compute service, and data store. Mark which traffic is public, which is private, and which connection would cross from an on-premises environment.

For storage, compare blobs, files, queues, tables, and managed disks by data shape and access need. Then add performance tiers, redundancy choices, storage account options, and movement tools such as AzCopy, Storage Explorer, File Sync, Azure Migrate, and Data Box. Ask whether the scenario needs object, file, message, key-value, or block storage before choosing a product.

For identity, distinguish Microsoft Entra ID from domain services, authentication from authorization, and single sign-on from multifactor or passwordless authentication. Learn what Conditional Access evaluates and how Azure role-based access control limits what an identity may do at a scope.

Connect Zero Trust, defense in depth, and Defender for Cloud to outcomes instead of treating them as interchangeable security labels. For each practice scenario, state whether the need is to verify explicitly, limit permissions, add protection across layers, assess security posture, or protect workloads.

Study cost factors, the pricing calculator, Cost Management, and tags as different tools. The calculator estimates a proposed design; Cost Management helps analyze and control actual cloud spending; tags attach useful metadata for organization and reporting. A question about future cost is not asking for the same tool as a question about last month's spend.

Keep RBAC, Azure Policy, and resource locks distinct. RBAC controls who can perform actions. Policy evaluates or enforces resource standards. A lock helps protect a resource from modification or deletion. Microsoft Purview addresses data governance and compliance rather than replacing those Azure resource controls.

Finally, compare the portal, Cloud Shell, Azure CLI, PowerShell, Azure Arc, infrastructure as code, Azure Resource Manager, and ARM templates by workflow. You do not need to memorize commands for a fundamentals exam, but you should recognize interactive management, command automation, hybrid management, and repeatable declarative deployment.

Azure Advisor recommends ways to improve resources. Azure Service Health communicates service issues and planned maintenance that can affect you. Azure Monitor collects and analyzes telemetry. Within the monitoring family, Log Analytics supports log queries, alerts react to conditions, and Application Insights focuses on application performance and behavior.

Build a six-row comparison sheet with one question for each tool. Which service recommends improvements? Which reports an Azure outage affecting your resources? Which collects platform metrics and logs? Which workspace supports log queries? Which mechanism notifies on a threshold? Which feature analyzes an application's requests and dependencies?

Revisit the sheet with scenarios instead of definitions. If a web application becomes slow, the evidence needed differs from a notice that an Azure region is experiencing a service incident. Choosing the tool starts with the operational question.

Take a mixed baseline without references and record confidence beside each answer. Review correct guesses as well as errors. For every miss, write the objective, the detail that should have controlled the decision, why your chosen option was weaker, and one follow-up task.

Use Microsoft's free Practice Assessment to experience official wording, and use the exam sandbox to become familiar with the interface. Supplement with independent questions that provide explanations and objective mapping. No short quiz proves readiness across the full blueprint, so compare your practice coverage with the official objective list.

Retest weak decisions after a delay with new wording. If you can only recognize the original answer, the concept is not stable yet. Finish the week with a timed mixed set, then spend the remaining study time on repeated reasoning errors rather than rereading every topic equally.

Before scheduling, confirm that you can explain every top-level objective and apply the major comparisons without prompts. Check that your practice has covered all three domains, that weak areas are improving on unfamiliar questions, and that you can complete mixed sets without rushing the final items.

Microsoft's certification page currently lists 45 minutes for the assessment and provides the supported languages, scheduling paths, accommodation information, retake policy, Practice Assessment, and exam sandbox. Recheck that page before booking because operational details can change independently of your study notes.

A passing score requires more than recognizing Azure names. Aim to explain why the selected service, governance control, cost tool, or monitoring feature fits the scenario and why the nearest alternative does not. That reasoning is also the part of AZ-900 preparation most likely to transfer into later Azure study.