Azure AZ-204 30-, 60-, and 90-day study plan with topic order, review loops, and final-week priorities.
This page answers the question most candidates actually have: “How do I structure my AZ-204 prep?” The schedules below follow Microsoft’s January 14, 2026 skills measured. The current version of the exam is scheduled to retire on July 31, 2026, so the safest plan is to study against the current scope directly instead of mixing it with older objective lists.
Use the plan that matches your available time, but keep it grounded in runnable Azure workloads. Each week should include one short build, one auth or configuration check, one timed drill set, and one miss-log review.
Use the plan as a weighted review order, not as a rigid checklist.
| Your starting point | Typical total study time | Best-fit timeline |
|---|---|---|
You build on Azure weekly (App Service, Functions, Entra ID) |
40-60 hours | 30-60 days |
| You have used Azure but not deeply as a developer | 60-90 hours | 60-90 days |
| You are newer to Azure development patterns | 90-120 hours | 90 days |
Choose a plan based on hours per week:
| Time you can commit | Recommended plan | What it feels like |
|---|---|---|
| 10-15 hrs/week | 30-day intensive | Fast learning plus lots of practice |
| 6-9 hrs/week | 60-day balanced | Steady progress plus room for review |
| 3-5 hrs/week | 90-day part-time | Slow and solid with repetition |
| Skill lane | Weight | What you should be good at |
|---|---|---|
| Compute | 25-30% | App Service, Functions, containers, diagnostics, scaling, and deployment slots |
| Storage | 15-20% | Cosmos DB SDK, consistency, change feed, Blob SDK, metadata, and lifecycle controls |
| Security | 15-20% | Entra ID auth, SAS, Microsoft Graph, Key Vault, App Configuration, and managed identity |
| Monitoring | 5-10% | Application Insights instrumentation, metrics, traces, availability tests, and alerts |
| Integration | 20-25% | API Management, Event Grid, Event Hubs, Service Bus, and Queue Storage |
If you want one rule: spend roughly 70% learning and 30% practice early, then invert it to roughly 30% learning and 70% practice in the final one or two weeks.
AZ-204 is much easier when you can picture one concrete workload instead of memorizing service names. A useful minimum lab includes:
If you cannot picture one concrete app path, one identity path, and one messaging path, timed practice will stay too abstract.
Target pace: about 10-15 hours/week.
Goal: cover the official skills quickly, then harden instincts through drills and mixed sets.
| Week | Focus | What to do | Links |
|---|---|---|---|
| 1 | Compute | Build runtime pickers: containers, App Service, Functions, diagnostics, scaling, and slots. Start a miss log. | Resources • Cheat Sheet |
| 2 | Storage + Security | Focus on Cosmos DB, Blob Storage, Entra auth, SAS, Graph, Key Vault, and managed identity. End the week with a mixed set. | Resources • Glossary |
| 3 | Integration | Drill API Management, Event Grid, Event Hubs, Service Bus, and Queue Storage so eventing and messaging no longer blur together. | Cheat Sheet • FAQ |
| 4 | Monitoring + full review | Finish Application Insights and alerting, then do 2 full mocks under time and re-drill the weakest lanes. | Cheat Sheet • FAQ |
Target pace: about 6-9 hours/week.
Goal: build clean coverage plus room for repetition and small labs.
| Week | Focus | What to do |
|---|---|---|
| 1 | 1.1 Containers, ACR & Container Apps | Drill the container hosting and image-publishing lanes. |
| 2 | 1.2 App Service, Scaling & Slots | Focus on web-app deployment, diagnostics, config, scaling, and staged rollouts. |
| 3 | 1.3 Functions, Triggers & Bindings + 2.1 Cosmos DB, Consistency & Change Feed | Drill event-driven functions plus Cosmos DB change behavior. |
| 4 | 2.2 Blob Storage, Metadata & Lifecycle + 3.1 Auth, SAS & Microsoft Graph | Cover the storage and identity access paths together. |
| 5 | 3.2 Key Vault, Config & Managed Identity + 4.1 App Insights, Logs & Alerts | Drill secure config and observability together. |
| 6 | 5.1 API Management & Policies | Build clear API gateway instincts. |
| 7 | 5.2 Event Grid & Event Hubs + 5.3 Service Bus & Queue Storage | Finish the integration lane and run mixed sets. |
| 8 | Final review | Do 2 full mocks, review every miss, and re-drill the weakest lesson families. |
Target pace: about 3-5 hours/week.
Goal: slow repetition with consistent drills and periodic mixed sets.
| Weeks | Focus |
|---|---|
| 1-3 | Compute |
| 4-5 | Storage |
| 6-7 | Security |
| 8 | Monitoring |
| 9-10 | Integration |
| 11-12 | mixed review and full mocks |
Use spaced re-drills on weak areas. 48-72 hour spacing works especially well on AZ-204 because the same service-confusion mistakes tend to repeat unless you revisit them deliberately.
If you have less than a week left before the exam retires or before your scheduled sitting:
If you still confuse:
then those are still your highest-return review targets