Azure AZ-104 30-, 60-, and 90-day study plan with topic order, review loops, and final-week priorities.
Use this plan if you want a clean path through AZ-104 without bouncing randomly between Microsoft Learn modules. The goal is to build administrative judgment, not just touch every service once.
Start with Identities & Governance, then work through Users, Groups, and SSPR, Azure RBAC and Scope, and Policy, Tags, Locks, and Cost Control.
Hands-on goal:
| If you are… | Use the plan like this |
|---|---|
| already comfortable in the Azure portal | move faster through concept review and spend more time on task execution and troubleshooting |
| stronger in identity than networking | spend extra time on private endpoints, DNS, routing, and ingress choices |
| stronger in ops than governance | spend extra time on scope hierarchy, Entra roles, RBAC, Policy, and Locks |
| short on time | keep one pass through all five current skill areas before chasing edge-case services |
Work through Storage, then study Storage Account Design, Redundancy, and Encryption, Storage Access, SAS, and Private Connectivity, and Azure Files, Blob Lifecycle, and Recovery.
Hands-on goal:
| Minutes | What to do | Why |
|---|---|---|
| 0-10 | review one admin task cluster | keeps the session scoped to a real skill |
| 10-20 | restate the key boundary or dependency | prevents shallow recognition-only review |
| 20-35 | do one small lab, portal walkthrough, or scenario drill | turns the topic into a task instead of a label |
| 35-45 | write one miss rule and one fix order | improves recall on exam-style troubleshooting |
Work through Compute, then cover ARM, Bicep, and Deployment Workflows and Virtual Machines, Disks, and Scale Sets.
Hands-on goal:
Finish Containers and ACR and App Service Plans, TLS, Networking, and Slots, then move into Networking, VNets, Subnets, Peering, Public IPs, and Routing, and Secure Private Access Patterns.
Hands-on goal:
Study Azure DNS and Load Balancing, then complete Monitoring & Recovery, Azure Monitor, Insights, and Alerting, and Backup, Site Recovery, and Network Watcher.
Hands-on goal:
Final-week checklist:
Final review priorities:
| Step | What to record |
|---|---|
| 1 | the weak area: identities/governance, storage, compute, networking, or monitoring/recovery |
| 2 | the real failure mode: scope confusion, DNS/path confusion, redundancy confusion, or signal confusion |
| 3 | the one sentence rule you should have applied |
| 4 | the exact page or lab to revisit next |
| Day | Focus |
|---|---|
| 7 | identities and governance only |
| 6 | storage only |
| 5 | compute only |
| 4 | networking only |
| 3 | monitoring and recovery only |
| 2 | one mixed set plus miss-log repair |
| 1 | glossary, cheat-sheet, and official-page check only |
If you already administer Azure daily, compress this plan into three or four weeks by combining adjacent weeks. Keep the lab work. AZ-104 punishes shallow recognition more than it rewards memorized terminology.
One timing note matters in this cycle: Microsoft says the English-language version of AZ-104 updates on April 17, 2026, so if you are testing near that date, verify the live objective list again on the certification page and study guide.
AZ-305 architecture patterns when the exam wants task-level admin judgment