Use this study plan when you want a structured route through AZ-900 instead of treating Azure Fundamentals as a random list of services. The exam is broad, but it stays manageable when you keep the three current skill areas separate and practice at the right altitude.
Pick the pace that matches your background
| Starting point |
Typical study time |
Good timeline |
| business, project, or sales role |
20-30 hours |
4-6 weeks |
| help desk or general IT support |
15-25 hours |
3-4 weeks |
| already using another cloud provider |
10-20 hours |
2-4 weeks |
A practical four-week sequence
- Week 1: cloud concepts, cloud models, and the shared-responsibility model
- Week 2: Azure architecture, regions, availability zones, and core services
- Week 3: management, governance, cost, deployment, and monitoring tools
- Week 4: mixed review using the cheat sheet, glossary, faq, and official prep links from resources
How to use this study plan well
| If you are… |
Use the plan like this |
| non-technical but business-oriented |
spend extra time on cloud concepts, pricing, and governance language |
| already in general IT |
spend extra time on Azure hierarchy, identity, and service families |
| coming from AWS or another cloud |
focus on Azure naming, hierarchy, and governance differences rather than relearning cloud basics |
| short on time |
complete one pass of all three skill areas before chasing edge-case service details |
What a good 30-minute study block looks like
| Minutes |
What to do |
Why |
| 0-10 |
review one concept, service family, or governance tool |
keeps the session bounded |
| 10-20 |
contrast it with the two most likely distractors |
builds elimination skill |
| 20-30 |
write one short rule and one memory hook |
turns review into retrieval instead of rereading |
Weekly loop
flowchart LR
R["Read one Azure topic cluster"] --> C["Classify it: concept, service, or governance"]
C --> N["Write one short comparison rule"]
N --> P["Use official practice or sandbox resources"]
P --> M["Log misses and revisit weak terms"]
What strong prep usually does
- learns Microsoft’s product categories before chasing smaller details
- keeps governance, compliance, and pricing in their own lane
- uses Microsoft Learn and the current certification page as the scope boundary
- treats the practice assessment as a signal for weak buckets, not as the only study method
Week-by-week focus
| Week |
Main pages |
What to get right by the end |
| 1 |
Cloud Concepts |
public/private/hybrid, shared responsibility, consumption, elasticity, IaaS/PaaS/SaaS |
| 2 |
Azure Architecture and Services |
hierarchy, regions/zones, core compute, networking, storage, identity basics |
| 3 |
Azure Management and Governance |
pricing tools, tags, Policy, locks, portal, Cloud Shell, Azure Monitor, Service Health |
| 4 |
appendix pages plus official practice |
mixed classification under time pressure without drifting into admin detail |
What to do after every mixed set
| Step |
What to record |
| 1 |
the weak area: cloud concepts, Azure architecture/services, or management/governance |
| 2 |
the real failure mode: service confusion, scope confusion, governance confusion, or cost confusion |
| 3 |
the one sentence rule you should have applied |
| 4 |
the exact page to revisit next |
Booking signal
You are getting close when:
- you can tell whether a question is asking about cloud concepts, Azure architecture and services, or management and governance
- you stop mixing identity tools with governance tools
- you can explain why one Azure service family is a better conceptual fit than another
- the exam sandbox interface no longer feels unfamiliar
Last-week compression plan
Final 48-hour plan
- reread the cheat sheet once for high-confusion pairs
- use the glossary only for terms you still mix up
- use the resources page to confirm the current certification page, practice assessment, and sandbox
- use the faq for exam logistics and last-mile judgment
What not to do in the final 48 hours
- do not switch into
AZ-104 or AZ-204 implementation detail
- do not memorize long Azure product lists without grouping them by job to be done
- do not keep doing mixed sets if the same lane is still collapsing; isolate and fix it first