AZ-900 — Microsoft Azure Fundamentals Study Plan
A practical AZ-900 study plan for Microsoft Azure Fundamentals candidates, with 7-day, 14-day, 30-day, and 60/90-day preparation schedules.
How to use this Study Plan
This plan is for candidates preparing for Microsoft Azure Fundamentals (AZ-900) from Microsoft. It is designed for practical scheduling: what to study, when to practice, when to take timed mocks, and how to review missed questions.
AZ-900 is a fundamentals exam, so the goal is not deep administration or engineering mastery. Your goal is to recognize Azure concepts, choose the appropriate service in common scenarios, understand cloud terminology, and explain management, governance, security, pricing, and support concepts clearly.
Use the official Microsoft exam skills outline as your scope controller. Do not spend your limited time memorizing obscure service limits, exact pricing numbers, or advanced implementation steps unless they directly support an AZ-900 objective.
Which plan should you use?
| Available time | Use this path | Best for | Main risk |
|---|---|---|---|
| 7 days | Final review sprint | You already studied or have Azure exposure | Too little time for broad relearning |
| 14 days | Focused plan | You know basic cloud terms but need structure | Skipping review of missed questions |
| 30 days | Balanced plan | Most candidates starting from light Azure knowledge | Moving too slowly through objectives |
| 60/90 days | Full preparation path | New to cloud or studying alongside work | Forgetting early material without spaced review |
If you are unsure, take a short diagnostic practice set first. Your result should decide the plan:
| Diagnostic result | Suggested action |
|---|---|
| Strong on cloud concepts, weak on Azure services | Spend more time on compute, storage, networking, databases, identity, and monitoring |
| Strong on services, weak on governance | Drill cost management, policy, resource locks, RBAC, compliance, support, and service lifecycle concepts |
| Many missed questions due to wording | Add timed practice and explanation review earlier |
| Many missed questions due to unfamiliar terms | Build a glossary and review it daily |
| Below your comfort level across all areas | Use the 30-day or 60/90-day plan instead of a cram path |
AZ-900 study priorities
Organize your preparation around these practical buckets:
| Study bucket | What to know for AZ-900 | Practice focus |
|---|---|---|
| Cloud concepts | IaaS, PaaS, SaaS, public/private/hybrid cloud, consumption model, shared responsibility, scalability, elasticity, high availability, fault tolerance | Identify cloud model and responsibility in scenarios |
| Azure architecture | Regions, availability zones, region pairs, subscriptions, management groups, resource groups, Azure Resource Manager | Match structure to governance and resiliency needs |
| Compute | Virtual machines, containers, Azure App Service, serverless concepts, Azure Functions | Choose the right compute option for a basic scenario |
| Networking | Virtual networks, VPN, ExpressRoute, DNS, load balancing concepts, network security basics | Recognize connectivity and isolation choices |
| Storage and databases | Storage accounts, blobs, files, queues, tables, SQL databases, Cosmos DB concepts | Select storage/database type from use case wording |
| Identity and security | Microsoft Entra ID, authentication, authorization, MFA, RBAC, Zero Trust concepts, Defender concepts | Distinguish identity, access, and security monitoring terms |
| Management and governance | Azure Policy, resource locks, tags, Blueprints concepts where relevant, Azure Arc concepts, monitoring | Choose governance tool for control, audit, or organization |
| Cost, SLA, and lifecycle | Pricing calculator, TCO concepts, cost management, budgets, SLAs, preview/general availability concepts, support plans | Interpret cost and support scenario language |
Daily practice rhythm
Use the same rhythm regardless of your timeline. Adjust the number of blocks, not the method.
| Block | Time | What to do |
|---|---|---|
| Warm-up recall | 5-10 min | Write or recite yesterday’s weak terms: subscription, resource group, RBAC, region, availability zone, Policy, SLA, etc. |
| Objective study | 25-45 min | Study one narrow topic from the official AZ-900 skills outline. Keep notes brief. |
| Scenario practice | 20-30 min | Answer questions that force service selection, cloud model identification, or governance choice. |
| Missed-question review | 20-30 min | Review every missed or guessed question. Record the rule you should have applied. |
| Active recall close | 5-10 min | Without notes, explain the topic as if teaching a non-technical stakeholder. |
For busy workdays, use a minimum effective session:
- Review 10 glossary terms.
- Answer 10-15 practice questions.
- Rewrite the explanation for every missed question.
- Mark one weak topic for tomorrow.
Missed-question review method
Do not only record the correct answer. AZ-900 questions often test the difference between similar terms and services.
Use this review table:
| Field | What to write |
|---|---|
| Topic | Example: Microsoft Entra ID, Azure Policy, availability zones, Azure Functions |
| Why I missed it | Did not know term, confused services, missed keyword, rushed, guessed |
| Correct rule | One sentence that would answer the question next time |
| Trap answer | The option that looked attractive but was wrong |
| Follow-up action | Review notes, compare two services, do 5 more questions, or add to glossary |
Example entries:
| Missed area | Corrective rule |
|---|---|
| RBAC vs Azure Policy | RBAC controls who can do actions; Azure Policy evaluates or enforces resource rules. |
| Availability zones vs regions | Zones are separate datacenter locations within a supported region; regions are geographic Azure locations. |
| IaaS vs PaaS | IaaS gives more infrastructure control; PaaS abstracts more platform management. |
| Authentication vs authorization | Authentication verifies identity; authorization determines access. |
| CapEx vs OpEx | Cloud commonly shifts spending toward operating expense and consumption-based billing. |
Review your missed-question log every 2-3 days. Your score improves fastest when repeated mistakes disappear.
When to use timed mock exams
Timed mock exams are most useful after you have covered the main objective areas at least once.
| Preparation stage | Timed mock use |
|---|---|
| First 20% of study time | Use short diagnostics only. Do not overreact to the score. |
| Middle of plan | Use section quizzes and mixed sets to expose weak areas. |
| Final third | Use full timed mocks to practice pacing and question interpretation. |
| Last 24 hours | Avoid heavy testing. Review errors, notes, and high-yield comparisons. |
After each timed mock, spend at least as much time reviewing as you spent testing. The review is where most of the learning happens.
7-day AZ-900 final review sprint
Use this if your exam is in one week and you have already studied some Azure fundamentals. If you are completely new to cloud, this can still help, but it is a high-pressure path.
7-day schedule
| Day | Main focus | Study actions | Practice actions |
|---|---|---|---|
| 1 | Diagnostic and cloud concepts | Take a short diagnostic. Review IaaS, PaaS, SaaS, shared responsibility, public/private/hybrid cloud, elasticity, scalability, availability. | 30-40 mixed questions. Build missed-question log. |
| 2 | Azure architecture | Review regions, availability zones, region pairs, subscriptions, resource groups, management groups, Azure Resource Manager. | Drill architecture and hierarchy scenarios. |
| 3 | Core services | Review compute, storage, databases, and networking at recognition level. Compare similar services. | Do service-selection questions. |
| 4 | Identity, security, and governance | Review Microsoft Entra ID, MFA, RBAC, Zero Trust, Azure Policy, locks, tags, Microsoft Defender concepts. | Drill “which control solves this?” questions. |
| 5 | Cost, SLA, monitoring, support | Review pricing calculator, TCO concepts, budgets, Cost Management, SLAs, Azure Monitor, Service Health, support concepts. | Complete a mixed timed set. |
| 6 | Full timed mock and repair | Take one full timed mock. Review every missed and guessed question. | Create a final weak-area list of no more than 5 topics. |
| 7 | Final review | Stop adding new material. Review glossary, weak-area list, service comparisons, and common traps. | Light practice only. Prioritize sleep and logistics. |
7-day rules
- Stop adding new topics after Day 5 unless a topic appears repeatedly in missed questions.
- Do not take multiple full mocks on the final day.
- Prioritize high-frequency fundamentals over deep Azure administration.
- If you miss a question twice, write the rule in one sentence and review it before bed.
14-day focused AZ-900 plan
Use this if you have two weeks and can study about 60-90 minutes most days.
14-day schedule
| Day | Focus | Study task | Practice task |
|---|---|---|---|
| 1 | Diagnostic | Take a short mixed diagnostic. Categorize misses by objective area. | Build your study tracker. |
| 2 | Cloud concepts | Cloud models, shared responsibility, consumption, availability, scalability, elasticity. | 25-40 cloud concept questions. |
| 3 | Azure structure | Regions, availability zones, subscriptions, resource groups, management groups, ARM concepts. | Architecture hierarchy drills. |
| 4 | Compute | VMs, containers, App Service, serverless, Functions. | Compute service-selection questions. |
| 5 | Storage | Blob, Files, queues, tables, storage account concepts, redundancy concepts at a high level. | Storage scenario questions. |
| 6 | Databases and analytics basics | Azure SQL concepts, Cosmos DB concepts, basic data service recognition. | Database selection questions. |
| 7 | Networking | Virtual networks, VPN, ExpressRoute, DNS, load balancing, basic network security concepts. | Networking scenario set. |
| 8 | Identity | Microsoft Entra ID, MFA, authentication, authorization, RBAC. | Identity and access questions. |
| 9 | Security | Zero Trust concepts, Defender concepts, security posture and monitoring concepts. | Security terminology drills. |
| 10 | Governance | Azure Policy, locks, tags, resource organization, compliance concepts. | Governance scenario questions. |
| 11 | Cost and SLA | Pricing calculator, TCO, budgets, Cost Management, SLAs, support concepts. | Cost and support questions. |
| 12 | Timed mock 1 | Take a full timed mock. | Review all misses and guesses. |
| 13 | Weak-area sprint | Re-study your weakest 3-5 topics. | Targeted question sets only. |
| 14 | Final review | Stop adding new material. Review glossary, comparisons, and missed-question log. | Light mixed practice if needed. |
14-day checkpoints
By the end of Day 7, you should be able to explain:
- The difference between IaaS, PaaS, and SaaS.
- What a subscription, resource group, and management group are used for.
- When to choose common compute, storage, networking, and database options.
- The basic role of Microsoft Entra ID.
- The difference between RBAC and Azure Policy.
By the end of Day 13, your final review should be limited to weak areas, not broad first-time learning.
30-day balanced AZ-900 plan
Use this if you want a practical, steady plan without cramming. This path works well for candidates with limited Azure experience.
Weekly structure
| Week | Goal | Main output |
|---|---|---|
| 1 | Build cloud and Azure foundation | Clear notes on cloud models, Azure structure, and core terms |
| 2 | Learn core Azure services | Service-selection confidence across compute, storage, networking, and databases |
| 3 | Cover security, governance, cost, and monitoring | Strong understanding of controls, identity, pricing, and management tools |
| 4 | Practice, repair, and final review | Timed mocks, weak-area repair, and exam readiness |
30-day schedule
| Day | Focus | What to do |
|---|---|---|
| 1 | Diagnostic | Take a short diagnostic and review the official skills outline. |
| 2 | Cloud models | Study IaaS, PaaS, SaaS, public/private/hybrid cloud. |
| 3 | Cloud benefits | Review scalability, elasticity, availability, reliability, predictability, security, governance, manageability. |
| 4 | Shared responsibility | Compare responsibilities across cloud service models. |
| 5 | Azure hierarchy | Study tenants, subscriptions, resource groups, management groups, and ARM concepts. |
| 6 | Regions and resiliency | Review regions, availability zones, region pairs, and basic resiliency concepts. |
| 7 | Week 1 review | Mixed quiz and missed-question repair. |
| 8 | Compute overview | Compare VMs, containers, App Service, and serverless concepts. |
| 9 | Virtual machines | Review VM use cases and management responsibility at fundamentals level. |
| 10 | Containers and app hosting | Compare containers, App Service, and serverless options. |
| 11 | Storage services | Review blob, file, queue, table, and storage account concepts. |
| 12 | Databases | Compare relational, NoSQL, and globally distributed database concepts. |
| 13 | Networking | Study VNets, VPN, ExpressRoute, DNS, load balancing, and network security basics. |
| 14 | Week 2 review | Service-selection quiz across compute, storage, databases, and networking. |
| 15 | Identity | Study Microsoft Entra ID, authentication, MFA, authorization, and RBAC. |
| 16 | Security concepts | Review Zero Trust, defense in depth, security posture, and Defender concepts. |
| 17 | Governance | Study Azure Policy, locks, tags, compliance concepts, and resource organization. |
| 18 | Monitoring | Review Azure Monitor, alerts, Log Analytics concepts, and Service Health concepts. |
| 19 | Cost management | Study pricing calculator, TCO concepts, budgets, and Cost Management. |
| 20 | SLA and support | Review SLA concepts, lifecycle concepts, and support-plan terminology. |
| 21 | Week 3 review | Mixed timed set and missed-question repair. |
| 22 | Timed mock 1 | Take a full timed mock. Review deeply. |
| 23 | Repair block 1 | Re-study weakest cloud/service area. |
| 24 | Repair block 2 | Re-study weakest governance/security/cost area. |
| 25 | Scenario drill | Do mixed service-selection and governance questions. |
| 26 | Timed mock 2 | Take another full timed mock if you have reviewed Mock 1 properly. |
| 27 | Error pattern review | Identify recurring mistakes and rewrite rules. |
| 28 | Final weak-area sprint | Review only your weakest 3-5 topics. |
| 29 | Final review | Glossary, service comparisons, missed-question log. No new material. |
| 30 | Exam readiness | Light review, exam logistics, rest. |
30-day practice targets
| Practice type | Suggested amount |
|---|---|
| Short topic quizzes | 4-6 per week |
| Mixed review sets | 2-3 per week |
| Full timed mocks | 2 in the final 10 days |
| Missed-question review | After every practice session |
| Glossary review | 5-10 minutes daily |
60/90-day full preparation path
Use this if you are new to cloud, returning to study after a long break, or studying alongside a demanding work schedule. The difference between 60 and 90 days is pace, not scope.
Phase plan
| Phase | 60-day pace | 90-day pace | Goal |
|---|---|---|---|
| Foundation | Days 1-14 | Days 1-21 | Understand cloud concepts and Azure structure |
| Core services | Days 15-30 | Days 22-45 | Recognize compute, storage, networking, and database options |
| Security and governance | Days 31-42 | Days 46-63 | Understand identity, access, controls, monitoring, and cost |
| Practice and repair | Days 43-54 | Days 64-81 | Timed practice, weak-area repair, mixed scenarios |
| Final review | Days 55-60 | Days 82-90 | Stop new material, review errors, confirm readiness |
Phase 1: Foundation
| Topic | Study actions | Practice actions |
|---|---|---|
| Cloud concepts | Learn cloud models, service models, shared responsibility, consumption-based billing, scalability, elasticity, and availability. | Explain each concept in one sentence. Answer concept-identification questions. |
| Azure structure | Study tenants, subscriptions, resource groups, management groups, ARM, regions, and availability zones. | Draw the hierarchy from tenant to resource. Drill structure questions. |
| Cloud value | Review reliability, predictability, governance, security, and manageability benefits. | Identify which cloud benefit is described in short scenarios. |
Phase 2: Core Azure services
| Topic | Study actions | Practice actions |
|---|---|---|
| Compute | Compare VMs, App Service, containers, and serverless concepts. | Choose compute options from scenario wording. |
| Storage | Review blob, files, queues, tables, redundancy concepts, and storage account basics. | Match data types to storage services. |
| Databases | Compare relational and NoSQL concepts, Azure SQL concepts, and Cosmos DB concepts. | Drill database selection scenarios. |
| Networking | Study VNets, subnets, VPN, ExpressRoute, DNS, load balancing, and basic isolation concepts. | Identify connectivity and routing choices at a fundamentals level. |
Phase 3: Security, governance, management, and cost
| Topic | Study actions | Practice actions |
|---|---|---|
| Identity | Microsoft Entra ID, MFA, authentication, authorization, RBAC. | Distinguish identity, access, and permission scenarios. |
| Security | Zero Trust, defense in depth, Defender concepts, security monitoring concepts. | Match security tools and concepts to basic needs. |
| Governance | Azure Policy, locks, tags, compliance concepts, resource organization. | Compare governance tools: policy vs lock vs tag vs RBAC. |
| Monitoring | Azure Monitor, alerts, Log Analytics concepts, Service Health concepts. | Identify which monitoring or health tool fits the scenario. |
| Cost and support | Pricing calculator, TCO, budgets, Cost Management, SLA, support concepts. | Answer cost-control and support terminology questions. |
Phase 4: Practice and repair
| Week action | What to do |
|---|---|
| Mixed sets | Use mixed practice to prevent topic isolation. |
| Timed mock 1 | Take once all major topics have been covered. |
| Review day | Spend a full session reviewing the mock before taking another. |
| Weak-area sprint | Re-study only the topics that caused missed or guessed questions. |
| Timed mock 2 | Take after repairs, not immediately after Mock 1. |
| Final topic comparison | Compare commonly confused items: RBAC vs Policy, region vs zone, IaaS vs PaaS, Monitor vs Service Health, CapEx vs OpEx. |
Phase 5: Final review
In the last 6-10 days:
- Stop broad first-time learning.
- Keep a short list of weak topics.
- Revisit your missed-question log daily.
- Use light mixed practice to keep recall active.
- Take no more than one full mock in the final few days unless you have enough time to review it properly.
- Prioritize sleep, pacing, and clear reading.
High-yield AZ-900 comparison drills
Use these comparisons throughout your plan. They are common sources of missed fundamentals questions.
| Compare | Know the difference |
|---|---|
| IaaS vs PaaS vs SaaS | Level of customer management responsibility changes. |
| Public vs private vs hybrid cloud | Ownership, access model, and integration pattern differ. |
| Scalability vs elasticity | Scaling capability vs automatic adjustment to demand. |
| Availability vs reliability | Uptime/resilience focus vs consistent correct operation. |
| Region vs availability zone | Geographic Azure location vs separate datacenter locations within a supported region. |
| Subscription vs resource group | Billing/security boundary vs logical container for resources. |
| Management group vs subscription | Organizes multiple subscriptions vs contains resource groups/resources. |
| RBAC vs Azure Policy | Access permissions vs rule evaluation/enforcement. |
| Resource lock vs Azure Policy | Prevents certain changes/deletion vs enforces standards. |
| Tags vs resource groups | Metadata for organization/cost reporting vs logical resource container. |
| Azure Monitor vs Service Health | Resource/platform monitoring vs Azure service-impact information. |
| Pricing calculator vs TCO calculator | Estimate Azure costs vs compare current environment to Azure cost model. |
| CapEx vs OpEx | Upfront capital spending vs operating/consumption-based spending. |
| Authentication vs authorization | Proving identity vs granting access. |
Hands-on concept review for AZ-900
AZ-900 does not require deep implementation skill, but light hands-on review can make terms easier to remember.
Use a sandbox, training environment, or non-production Azure subscription if available. Avoid creating paid resources unless you understand the cost.
| Hands-on task | What to observe |
|---|---|
| Open the Azure portal dashboard | Where services, subscriptions, and resource groups appear |
| View resource group creation screens | Required metadata, region selection, tagging options |
| Browse Microsoft Entra ID area | Identity, users, groups, and access terminology |
| Explore Cost Management screens | Budgets, cost analysis, and cost-control language |
| Browse Azure Monitor and Service Health | Difference between monitoring resources and Azure platform health |
| Review storage account creation screens | Storage terminology and redundancy concepts at a high level |
| Review virtual network creation screens | Address space, subnet, and connectivity terminology |
Do not let hands-on exploration replace practice questions. For AZ-900, the exam usually rewards correct concept recognition more than step-by-step portal memory.
Weekly review checklist
Use this checklist at the end of each study week.
| Check | Yes/No |
|---|---|
| I reviewed every missed and guessed question. | |
| I can explain my weakest topic without notes. | |
| I updated my glossary with confusing terms. | |
| I practiced mixed questions, not only topic questions. | |
| I compared similar services and controls. | |
| I scheduled the next timed mock only after reviewing the last one. | |
| I removed topics that are outside the AZ-900 scope. |
Exam-readiness checks
You are approaching readiness when you can do the following consistently:
| Readiness area | You should be able to… |
|---|---|
| Cloud concepts | Identify cloud and service models from short scenarios. |
| Azure services | Choose common Azure services for basic compute, storage, networking, and database needs. |
| Identity and security | Explain Microsoft Entra ID, MFA, RBAC, authentication, authorization, and basic security concepts. |
| Governance | Choose between Azure Policy, locks, tags, resource groups, subscriptions, and management groups. |
| Cost and support | Recognize pricing, TCO, budgets, cost management, SLA, and support terminology. |
| Timing | Complete mixed practice without rushing or rereading every question. |
| Error control | Avoid repeating the same missed-question patterns. |
A practical practice target is to score comfortably above your personal safety margin on multiple independent timed practice sets. Treat practice scores as readiness indicators, not as guarantees.
Final-week rules
During the final week, protect review quality.
- Stop adding new material once you enter the final 48 hours.
- Review missed questions before taking more questions.
- Keep a one-page sheet of confusing comparisons.
- Do not memorize exact prices, obscure limits, or advanced configuration details.
- Read each question for keywords: “most appropriate,” “minimum management,” “control access,” “enforce standard,” “estimate cost,” “monitor health.”
- Sleep before the exam. Fatigue causes avoidable mistakes on fundamentals questions.
- On exam day, mark uncertain questions and return if time allows.
Practical next step
Choose the schedule that matches your exam date, take a diagnostic practice set, and build your missed-question log today. Your next study session should focus on the weakest AZ-900 objective area revealed by that diagnostic, not the topic that feels easiest.