RoleMath Study Track · free study companion
A free study companion keyed to the officially published exam domains of Microsoft Azure Fundamentals (AZ-900): what each domain covers in plain language, clearly labeled free resources, a guided lab outline for every domain, and interactive self-checks from our own question bank. Microsoft Azure Fundamentals (AZ-900) study guide
A free, source-cited study companion built on Microsoft's published AZ-900 study guide — not official training, not a pass guarantee. AZ-900 is an entry-level, no-prerequisite Fundamentals exam, and every lab runs in the learner's own free Azure account with a budget alert set first. Verify the current objectives on the official page before your exam.
Not sure which domain to start with? Take the readiness check on the cert page →
Program blueprint under review
A complete free AZ-900 program pinned to the currently reviewed Microsoft study guide (skills measured as of July 20, 2026), using free Microsoft Learn paths and executable, budget-safe labs in the learner's own free Azure account to turn cloud concepts, Azure services, and governance into decision evidence. The 2026-07-20 update is a minor sub-skills refresh with the same three domains and weights; the program still requires a guide re-diff on or after that date before exam scheduling. Total planning estimate ~15-30 hours depending on prior IT exposure.
This draft exposes RoleMath’s authored sequence and evidence plan. The current labs are guided outlines, not yet a fully fixture-backed course, and objective-leaf coverage has not passed the gold-standard gate. Completion does not predict an exam result.
Choose an outcome
Choose provisionally. Change routes when the work tells you something new about fit, time, or readiness.
Learners who have selected AZ-900 and need one current sequence across all three domains, with an explicit recheck before or after Microsoft's announced guide/exam update.
Completion emphasis: Complete every module and no-subscription or controlled lab route, Microsoft Learn paths, the official practice assessment, the Azure governance capstone, and a final guide-diff gap review.
Career changers and technical collaborators who want reviewable evidence that they can map requirements to Azure hierarchy, services, identity, controls, costs, monitoring, and support.
Completion emphasis: Retain a hierarchy/architecture map, service choices, responsibility and RBAC matrices, governance policy set, cost scenarios, monitoring/support plan, tabletop findings, cleanup record, and decision memo.
Learners deciding whether Azure service, identity, governance, cost, and management concepts are worth deeper administrator, architect, data, security, or developer exploration.
Completion emphasis: Complete the diagnostic, no-account pricing comparison, hierarchy/service map, RBAC/shared-responsibility matrix, and governance tabletop; choose a next Azure role experiment rather than infer job readiness from AZ-900.
Start safely
Choose a current-guide, no-subscription or controlled-account route before Azure practice; this diagnostic is not a Microsoft prerequisite, cost promise, or exam prediction.
Ready when: Yes, with the current guide date recorded and any changes diffed before exam scheduling or publication.
If not yet: Continue learning broad concepts but keep exam logistics and program review blocked until the post-update guide is checked.
Ready when: Either route is valid; an Azure subscription and payment method are not required for full program completion.
If not yet: Use Microsoft Learn, documentation, Pricing Calculator, diagrams, expected-state tables, and governance tabletops without opening a subscription.
Ready when: Yes, with only empty-resource-group/budget/read-only exploration and no billable deployment required.
If not yet: Stay on the no-subscription route and do not enter billing details or deploy resources for the program.
Ready when: Yes, or you will complete the cloud-concepts module before memorizing Azure product names.
If not yet: Begin with vendor-neutral cloud value, service models, shared responsibility, and pricing concepts.
Ready when: Yes, or you will build the hierarchy map before access, policy, cost, or management decisions.
If not yet: Use a fictional hierarchy diagram and scope-propagation exercise before the governance module.
Ready when: Yes, with region, usage, scope, exclusions, source/date, and uncertainty recorded.
If not yet: Use an assumption/evidence log before presenting any calculator value, service target, or support expectation.
Plan, then adapt
6 weeks 5-7 hours/week
A planning estimate for first-time Azure learners: separate concepts, architecture/services, management/governance, capstone, and the required Microsoft guide recheck.
4 weeks 8-10 hours/week
A planning estimate that pairs Microsoft Learn with one artifact per domain and preserves a final capstone, practice-assessment, and guide-diff block.
2 weeks 12-16 hours/week
For learners with prior Azure, Microsoft 365, IT, cloud, governance, or finance exposure; do not compress the announced-update recheck or unfamiliar hierarchy/responsibility concepts.
Evidence-gated sequence
Pin the currently reviewed AZ-900 guide, record the announced update, choose a no-subscription or controlled route, and establish evidence, cost, hierarchy, and cleanup records.
Explain cloud value and limits, service/deployment models, shared responsibility, consumption pricing, scalability, elasticity, reliability, predictability, governance, and manageability before selecting Azure services.
Modules: Describe cloud concepts
Map requirements to Azure regions/zones, resource hierarchy, compute, networking, storage, identity, access, security, migration, and management categories while recognizing scope and tradeoffs.
Modules: Describe Azure architecture and services
Control Azure scope, access, location, configuration, cost, deployment, monitoring, health, recommendations, and support through explicit owners and evidence.
Modules: Describe Azure management and governance
Integrate cloud concepts, Azure architecture/services, identity/security, management, governance, cost, monitoring, support, cleanup, and decision communication in one fictional department onboarding packet.
Modules: Describe cloud concepts, Describe Azure architecture and services, Describe Azure management and governance
Before a lab
Show your work
Completing this policy demonstrates current-guide AZ-900 coverage and no-subscription Azure decision practice inside RoleMath; it does not predict a score, confer tenant authority, guarantee savings, or establish professional Azure experience.
Integrated practice
Onboard a fictional department into an Azure environment by mapping requirements to hierarchy, services, identities, security, governance, cost, monitoring, support, and cleanup decisions across all three AZ-900 domains without requiring a subscription.
Safety boundary: The complete capstone has a no-subscription route. Optional live evidence is limited to an empty resource group and free budget alert in a personally controlled secured account, with no deployed service, data, identity/RBAC/Policy/lock change, or production scope. Delete/verify the empty group, review costs, retain the alert, and never expose tenant/subscription, billing, credential, or portal details.
Finish honestly
Present the packet as self-directed AZ-900 Azure literacy/governance lab work. Do not call it tenant administration, a production landing zone, Microsoft approval, guaranteed cost/availability, professional Azure experience, or a RoleMath credential.
Objective source checked 2026-07-11. Recheck objectives every 10 days and resources every 60 days.
The official objective domains and their exam weight — titles & weights only, straight from the vendor’s exam objectives. Microsoft Azure Fundamentals (AZ-900) study guide
Our default advice is to study the heaviest-weighted domain first, because the published weights tell you where the exam spends its questions. Azure Fundamentals gets one honest exception. Microsoft weights 'Describe Azure architecture and services' at 35-40% — the heaviest domain — and 'Describe Azure management and governance' at 30-35%, while 'Describe cloud concepts' carries the lightest range at 25-30%. But Cloud concepts is the vocabulary foundation the other two are written on: what the cloud is, why organizations move to it, and the value language (elasticity, pay-as-you-go, economies of scale, the shared responsibility model) that the architecture and governance questions quietly assume you already speak. Studying services or governance before you can say what the cloud is for makes both harder to reason about. So a defensible path is: skim Cloud concepts first to build the vocabulary, then spend your largest study block on Azure architecture and services (35-40%), then Azure management and governance (30-35%), and finally return to close any gaps in Cloud concepts (25-30%). Our recommended_order below lists the two heaviest domains first because that is where the questions concentrate; treat Cloud concepts as the foundation you touch first and last. This is sequencing advice based on the published weight ranges and how the topics depend on each other, not a claim about the science of learning — if a different order fits how you think, use it.
Module 1 of 3 · domain 2 · 35-40% of the exam
The heaviest domain on the exam — Microsoft weights it at 35-40%. Once the Domain 1 vocabulary is in place, spend your largest block of study time here; by weight, it is where the exam spends the most questions.
Plain-language explanation in our own words — paraphrased from, and checked against, the official objectives. Microsoft Azure Fundamentals (AZ-900) study guide
This is the biggest domain on the exam — Microsoft weights it at 35-40% — and it is the 'what can Azure actually do, and how is it laid out' domain. Where the cloud-concepts domain explains why the cloud exists, this domain populates it with the concrete building blocks — compute, storage, networking, databases — and with the way Azure organizes the world its services run in. Nobody expects an Azure Fundamentals holder to be an engineer, but the exam does expect you to recognize the main categories of service and pick the right kind of tool for a described job. Because the service names are many, the winning strategy is to learn categories first and a few flagship examples per category, not to memorize a catalog.
Start with Azure's global infrastructure, because later topics reuse it. Azure divides the world into regions — separate geographic areas you choose among, often for legal, data-residency, or latency reasons. Many regions are grouped into region pairs for resilience, and Azure also offers availability zones — physically separate locations within a region — so that spreading a workload across zones lets it survive one facility failing. The recurring exam skill is matching a goal to the right layer: 'keep running if one data center fails' points to availability zones, while 'meet a data-residency requirement' points to choosing the right region.
Next comes the way Azure organizes what you deploy, which is distinctive enough that the exam leans on it. Resources (the individual services you create) live inside resource groups — logical containers that let you manage related resources together. Resource groups belong to subscriptions, which are the unit of billing and access boundaries, and subscriptions can be organized under management groups for governance across many of them at once. Azure Resource Manager is the underlying deployment and management layer that all of this flows through. You are not being asked to administer this hierarchy — you are being asked to recognize it: what a resource group is for, what a subscription represents, and why an organization would use management groups.
The largest share of the domain is the Azure service categories themselves, learned by purpose. Compute is the ability to run programs: virtual machines you size and manage yourself (infrastructure as a service), a platform for hosting web applications without minding the servers (Azure App Service), container options such as Azure Container Instances and Azure Kubernetes Service, and a serverless option that runs your code only when an event fires (Azure Functions). Networking is the plumbing that connects it all — virtual networks that isolate your resources, load balancers that spread traffic, VPN and ExpressRoute connections that link Azure to your own network, and a global content-delivery capability. Storage comes in shapes for different jobs: blob storage for unstructured files, backups, and media; file, queue, and table storage for other patterns; and cooler, cheaper tiers for archives you rarely touch. Databases split into managed relational databases such as Azure SQL Database and a family of non-relational options built for scale and flexible data shapes such as Azure Cosmos DB. You are matching needs to categories, not reciting specifications.
A theme that ties the domain together is the trade-off between control and convenience — the same spectrum the cloud-concepts service models named, now made concrete in Azure's products. Running your own virtual machine gives you full control and full responsibility for patching and scaling it; a managed platform such as App Service or a serverless option such as Functions removes much of that burden but constrains how much you can customize. Recognizing where a described scenario sits on that spectrum — 'the team wants to stop managing servers entirely' versus 'the team needs a specific operating-system configuration' — is exactly the judgment the exam is checking, and it maps directly back to the IaaS/PaaS/SaaS models from Domain 1.
Study this domain by building a mental menu: for each category — compute, networking, storage, databases — name one or two flagship Azure services and the one sentence that says what each is for. Then practice the reverse: read a described need and say which category and service fit. The hands-on lab below has you explore Azure's core service categories and the resource hierarchy without deploying anything paid, so the service model stops being abstract. And read the official AZ-900 study guide for the authoritative topic list; our explanation paraphrases its scope in our own words rather than reproducing it.
Create a resource group and a Standard LRS storage account with a private blob container in a free Azure trial you own, then delete the resource group so it cascades Observe storage redundancy options, access tiers, access keys, and a private blob endpoint firsthand and record them on a steps script
Confirm the steps script records creating a resource group and a Standard LRS storage account, observing redundancy options, access tiers, access keys, and a private blob endpoint, and then deleting the resource group with cleanup verified and no keys or IDs pasted.
Practice evidence maps to exam_domain_microsoft_az_900_az_900_02
Stay safe & legal: Create resources ONLY in a free Azure trial you own — never a work, school, employer, or client tenant — and set a $1 budget / spending alert FIRST. Create only a resource group and a Standard LRS storage account with one tiny non-sensitive blob, all of which stay effectively $0, and DELETE the resource group at the end so it cascades. A budget alert warns you but is not a hard cap, so the delete step is what protects you. Account required: yes; payment required: no; maximum designed cost: $0.
4RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 2 of 3 · domain 3 · 30-35% of the exam
The second-heaviest domain — Microsoft weights it at 30-35%. Study it after the architecture and services domain: management and governance in Azure is mostly about controlling, costing, and securing the services you now recognize, so it reads more clearly once those services have names.
Plain-language explanation in our own words — paraphrased from, and checked against, the official objectives. Microsoft Azure Fundamentals (AZ-900) study guide
This is the 'who controls it, what does it cost, and how do you keep it in line' domain, and Microsoft weights it at 30-35% — the second-heaviest slice of the exam. It answers three connected questions: how do you understand and manage what Azure charges you, how do you enforce rules and access across an organization, and what tools does Azure give you to monitor and protect what you have deployed. For career changers coming from finance, operations, or account-management backgrounds, this is friendly terrain: much of the underlying skill is reading a bill, setting a policy, and choosing who can do what — not configuring technology by hand.
Start with cost management, because it is the most concrete and clickable part of the exam. Several factors drive what you pay — the resource type, how much you use it, which region it runs in, and which pricing option you chose. Azure offers ways to reduce cost for predictable workloads, such as reservations (committing to one or three years of usage for a discount) and, for eligible workloads, bringing your own existing licenses. The core tools are worth recognizing by purpose: Microsoft Cost Management lets you analyze and forecast spending and slice it by service or tag; the Total Cost of Ownership and Pricing calculators help you estimate before you commit; and budgets let you set a threshold and get alerted before spending crosses a line you chose. The exam tests whether you can match a described need — 'alert me before I overspend', 'estimate this project before we build it', 'show me which service costs the most' — to the right tool.
Next is governance and compliance — the discipline of keeping a cloud environment inside the rules an organization sets. Azure Policy lets you define and enforce rules across resources, for example requiring that every resource carry certain tags or that resources deploy only in approved regions. Resource locks protect critical resources from accidental deletion or change. Tags attach metadata (like a cost center or environment name) that makes resources searchable and billable by group. And Microsoft Purview and the Service Trust Portal support compliance and trust at a broader level. The concept the exam wants is that governance is how you scale control: rather than trusting every person to follow the rules by hand, you encode the rules so the platform enforces them.
Identity and access sit alongside governance, because controlling who can do what is the other half of keeping an environment safe. Microsoft Entra ID (Azure's cloud identity service) manages users, groups, and the sign-in experience, and supports capabilities like single sign-on, multi-factor authentication (requiring a second proof beyond a password), and conditional access (granting or blocking access based on signals like location or device). Role-based access control assigns permissions by role rather than by handing out broad access, and the principle to internalize is least privilege — giving each identity only the access it genuinely needs. Zero Trust, the idea of verifying every request rather than trusting anything by default, frames the whole approach. The exam expects you to recognize the right identity or access control for a described situation, not to configure directory objects.
The domain closes with monitoring and the tools that tell you how your deployed resources are behaving. Azure Monitor collects metrics and logs across your resources; Azure Advisor inspects your environment against best practices and recommends improvements across cost, security, reliability, performance, and operational excellence; and a service-health capability tells you when Azure itself is having problems that could affect you. The exam wants you to know these exist and to match a described need — 'recommend where we could save money or tighten security', 'is this outage on our side or Azure's?' — to the tool that answers it.
Study this domain by clicking, because it rewards it more than any other: in a free account you can open Cost Management, set a budget, and read Azure Advisor's recommendations in minutes. The lab below has you set a budget alert with your own hands, which teaches the single most important cost-safety habit on the platform — being warned before you overspend rather than after. And as with every domain on this track, read the official AZ-900 study guide for the authoritative topic list; our explanation paraphrases its scope in our own words rather than reproducing it.
Create a free budget alert in a free Azure account you own so you are warned before you overspend Tour the cost, governance, access, health, and compliance surfaces read-only and match each tool to a described need
Confirm the worksheet records creating a free $1 budget alert, tours the cost/governance/access/health/compliance surfaces with a purpose note each, matches each described need to the right tool, and confirms nothing beyond the budget alert was created or assigned.
Practice evidence maps to exam_domain_microsoft_az_900_az_900_03
Stay safe & legal: Work ONLY in a free Azure account you own — never a work, school, employer, or client tenant. The only thing you create is a free budget alert (no billable resource); everything else is view-only. Do not assign a policy, assign a role, or change any setting, and set the budget alert FIRST before any other Azure lab that creates resources. A budget is an alert, not a hard cap. Account required: yes; payment required: no; maximum designed cost: $0.
4RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 3 of 3 · domain 1 · 25-30% of the exam
Touch this first even though it carries the lightest range. Microsoft weights this domain at 25-30% of the exam, but it defines what the cloud is and the value vocabulary — elasticity, pay-as-you-go, economies of scale, the shared responsibility model — that the architecture and governance domains all assume you already speak.
Plain-language explanation in our own words — paraphrased from, and checked against, the official objectives. Microsoft Azure Fundamentals (AZ-900) study guide
This is the 'why cloud, and what does that even mean' domain. Before AZ-900 asks you to name an Azure service or reason about governance, it establishes what the cloud actually is and why an organization would move to it. Microsoft weights this domain at 25-30% of the exam — the lightest of the three ranges — but it deals in ideas rather than product names: the mental models the rest of the exam quietly leans on. If a later question about a service or a cost tool ever feels like it is written in a language you do not speak, the gap is usually somewhere in here.
The center of gravity is the cloud value proposition — the honest business case for renting computing instead of owning it. A handful of ideas recur. Elasticity means you can add capacity when demand rises and release it when demand falls, instead of buying hardware months ahead for a peak that may never come; scalability is the related idea of growing (or shrinking) capacity as need changes, either by resizing a resource or by adding more of them. Pay-as-you-go, or consumption-based pricing, means you are billed for what you actually use, turning a large upfront capital purchase into a smaller ongoing operating cost. High availability means designing so a service keeps running even when a component fails, and disaster recovery is the plan for getting back after a larger outage. The exam expects you to recognize these benefits from a described situation, not to recite them — a scenario about 'unpredictable traffic' is really asking you to name elasticity.
Around the value proposition sits cloud economics: the way costs change shape when you move. The key contrast is capital expenditure versus operating expenditure — owning a data center is a large upfront capital bet, while the cloud converts much of that into an operating expense that tracks usage. The domain also leans on the idea that a provider serving many customers can often run infrastructure more cheaply per unit than one company running a small data center could — economies of scale. A recurring theme is letting a provider handle the generic, undifferentiated work — powering, cooling, and maintaining hardware — so your people can spend time on the things that actually distinguish your organization.
The domain also introduces the shared responsibility model, which the security and governance topics later reuse. The idea is that responsibility for security and operation is split between the cloud provider and you, the customer, and where the line falls depends on the kind of service. For infrastructure services you manage more (operating systems, applications, configuration); for fully managed or software services the provider manages more, and your responsibility narrows toward your data and who can access it. Microsoft frames some responsibilities as always yours no matter the model — your information and data, your devices, and your accounts and identities. The exam wants you to reason about where a described responsibility falls, not to memorize a chart.
Finally, the domain frames the cloud service models and deployment models. The service models describe how much the provider manages for you: infrastructure as a service gives you raw compute and storage to build on with the most control and the most responsibility; platform as a service hands you a managed environment to run applications without minding the servers; and software as a service delivers finished applications you simply use. The deployment models describe where workloads live — a public cloud shared across many organizations, a private cloud dedicated to one, or a hybrid mix that spans both — each with different trade-offs in control, cost, and responsibility. The exam wants you to match a described need to the right model, for example recognizing that 'we want to run software without managing any servers' points toward platform as a service.
On the job, this domain is the difference between parroting 'the cloud is cheaper' and being able to explain when and why it is — or is not. A useful way to study is to take a system you understand, even a personal project, and narrate its move to the cloud out loud: what would become elastic, what would shift from a capital purchase to a metered operating bill, what heavy lifting a provider would take over, and which service model fits. The Pricing Calculator lab below turns the elasticity and consumption-pricing ideas into numbers you generate yourself. Read the official AZ-900 study guide for the exact topic list — the wording there is Microsoft's own, and this explanation deliberately paraphrases rather than reproduces it.
Tour the Azure portal read-only to see regions, availability zones, and the core service categories that the cloud-concepts vocabulary describes Classify seven Azure services as IaaS, PaaS, or SaaS on a worksheet you fill in yourself, with no resource created
Confirm the worksheet answers the regions/availability-zone/region-pair prompts, classifies all seven services as IaaS/PaaS/SaaS with a who-manages-what note each, includes the control-versus-convenience reflection, and confirms no resource was created.
Practice evidence maps to exam_domain_microsoft_az_900_az_900_01
Stay safe & legal: Tour the Azure portal read-only ONLY in a free Azure account you own — never a work, school, employer, or client tenant — and set a $1 budget / spending alert FIRST. This lab creates, changes, and deletes nothing: you read Create blades and documentation and record what you see, and you must not click the final Create on any resource. Account required: optional; payment required: no; maximum designed cost: $0.
4RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Studying Microsoft Azure Fundamentalsbuilds transferable skills that carry across employers and platforms, not just toward this one exam. Each has a free, source-cited RoleMath primer — what it is, a step-by-step free learning path, clearly labeled free resources, and a safe hands-on exercise:
Work through the modules above, then get a personalized read on where you stand: the readiness check maps your background against these same published domains and suggests what to study first — no score, no pass prediction.
Check your Microsoft Azure Fundamentals readiness →Full Microsoft Azure Fundamentals decision page →
A free, source-cited study companion built on Microsoft's published AZ-900 study guide — not official training, not a pass guarantee. AZ-900 is an entry-level, no-prerequisite Fundamentals exam, and every lab runs in the learner's own free Azure account with a budget alert set first. Verify the current objectives on the official page before your exam.
Certification and vendor names are used only to identify the program this independent study companion refers to. RoleMath is not affiliated with, endorsed by, or sponsored by Microsoft.