AZ-104 — Microsoft Azure Administrator Study Plan
A practical time-based study plan for the Microsoft Azure Administrator AZ-104 exam.
This Study Plan is for candidates preparing for the real Microsoft Azure Administrator (AZ-104) exam from Microsoft. It is designed for working IT professionals who need to turn limited study time into a practical schedule.
AZ-104 preparation should combine three activities:
- Objective review — know the administrative concepts Microsoft expects.
- Hands-on Azure practice — configure, troubleshoot, and compare services.
- Timed exam practice — build speed, accuracy, and scenario judgment.
Use the plan that matches your remaining time, then follow the daily rhythm and missed-question review method consistently.
Which plan should you use?
| Time until exam | Best plan | Use this if | Main goal |
|---|---|---|---|
| 7 days | Final review plan | You already studied most topics or cannot move the date | Find weak areas, drill them, avoid new rabbit holes |
| 14 days | Focused plan | You know Azure basics but need structure and exam practice | Cover every major AZ-104 area once and review misses |
| 30 days | Balanced plan | You can study most days and want a realistic full pass | Build knowledge, hands-on skill, and timed readiness |
| 60/90 days | Full preparation path | You are newer to Azure administration or starting from scratch | Learn, lab, review, and test without rushing |
If you are not sure, start with a timed diagnostic set of practice questions before choosing. Do not spend the first several days only reading documentation or watching videos. AZ-104 requires scenario judgment, and practice questions reveal what you actually need to fix.
What AZ-104 preparation needs to cover
Organize your study around the major Azure administrator skill areas instead of studying random services.
| Area | What to be able to do |
|---|---|
| Identity and governance | Microsoft Entra ID basics, users, groups, RBAC, subscriptions, management groups, policies, locks, tags |
| Storage | Storage accounts, blob access, lifecycle options, redundancy concepts, Azure Files, shared access, data movement |
| Compute | Virtual machines, scale sets, containers where relevant, App Service basics, availability, backup and recovery choices |
| Virtual networking | VNets, subnets, NSGs, routing, peering, DNS, VPN concepts, load balancing, private access patterns |
| Monitoring and backup | Azure Monitor, alerts, Log Analytics concepts, metrics, activity logs, backup, recovery, update and performance review |
| Operational judgment | Choosing the right service, diagnosing broken access, reading scenario constraints, least-privilege administration |
Keep Microsoft’s current AZ-104 skills outline nearby while studying. Use it as the checklist, but use labs and practice questions to test whether you can apply each item.
Baseline setup before you begin
Complete this setup once, regardless of your schedule.
| Setup item | Why it matters |
|---|---|
| Current AZ-104 skills outline | Prevents studying outdated or unrelated topics |
| Practice question bank or mock exams | Needed for diagnostics, timing, and missed-question review |
| Azure lab environment | Lets you configure services instead of only memorizing them |
| Notes tracker | Keeps weak areas visible |
| Timer | Builds exam pacing |
| Cleanup habit | Avoids leaving unnecessary lab resources running |
Suggested tracker columns:
| Date | Topic | Question or lab issue | Why I missed it | Correct rule | Retest date |
|---|
Daily practice rhythm
Use the same rhythm every study day. Adjust the duration, not the structure.
If you have 60 minutes
| Time | Activity |
|---|---|
| 10 min | Review yesterday’s missed questions or notes |
| 25 min | Study one AZ-104 objective area |
| 15 min | Complete a small lab or scenario drill |
| 10 min | Answer 8-12 targeted questions and log misses |
If you have 90 minutes
| Time | Activity |
|---|---|
| 10 min | Warm-up review of weak notes |
| 30 min | Learn or review one topic |
| 25 min | Hands-on Azure configuration or troubleshooting |
| 20 min | Targeted practice questions |
| 5 min | Update missed-question tracker |
If you have 2-3 hours
| Time | Activity |
|---|---|
| 15 min | Review previous misses |
| 45 min | Topic study |
| 45 min | Hands-on lab |
| 45 min | Practice questions |
| 15-30 min | Deep review of explanations and documentation |
Do not separate all learning from all practice. For AZ-104, you should study a topic, configure it, then answer questions on it while the details are fresh.
Missed-question review method
The fastest way to improve is to classify every missed question. Do not only read the explanation and move on.
| Miss type | What it means | Fix |
|---|---|---|
| Knowledge gap | You did not know the service or feature | Review the objective and make a short rule note |
| Misread scenario | You missed a constraint, keyword, or requirement | Re-read slowly and underline decision words |
| Service confusion | You mixed up similar Azure services or features | Create a comparison table |
| Order-of-operations error | You knew the tools but not the sequence | Write the steps in order |
| Permission or identity error | You missed RBAC, scope, policy, or access behavior | Drill least privilege and scope inheritance |
| Timing error | You rushed or spent too long | Practice timed sets, not untimed reading |
Use this review loop:
- Re-answer the question without looking at the explanation.
- Identify the exact reason your answer was wrong.
- Write one short correction rule.
- Link the rule to an AZ-104 objective area.
- Retest the same concept within 48 hours.
- Add repeat misses to your final-week list.
Example correction rule:
“RBAC permissions are evaluated at the assigned scope and inherited downward. If the requirement is limited to one resource group, do not assign at the subscription unless the scenario requires it.”
7-day final review plan
Use this if your exam is one week away. This is not a full learning plan. It is a triage plan.
7-day schedule
| Day | Focus | Required actions |
|---|---|---|
| 1 | Diagnostic and plan | Take a timed diagnostic set. Identify your weakest 3 areas. Build a final review list. |
| 2 | Identity and governance | Drill Microsoft Entra ID, RBAC, policy, locks, tags, subscriptions, scopes. Do targeted questions. |
| 3 | Storage | Review storage account choices, access, redundancy concepts, Azure Files, blob management, data movement. Do a storage lab. |
| 4 | Compute | Review VMs, availability, disks, backup, scale options, App Service basics. Practice deployment and recovery scenarios. |
| 5 | Networking | Review VNets, subnets, NSGs, routing, peering, DNS, load balancing, VPN/private access concepts. Do scenario questions. |
| 6 | Monitoring, backup, and timed mock | Review Azure Monitor, alerts, logs, activity logs, backup. Take one timed mock or large timed set. Review every miss. |
| 7 | Final consolidation | No new major topics. Review notes, repeat missed questions, light hands-on only. Stop heavy study early. |
7-day rules
- Do not try to master every Azure service.
- Stop adding new material after Day 6 unless it fixes a repeated miss.
- Spend more time on questions you got wrong than on questions you got right.
- Use short labs only; do not build large architectures.
- Prioritize scenario reading and service selection.
Best final-week drills for AZ-104
| Drill | What to practice |
|---|---|
| RBAC scope drill | Which role assignment scope satisfies the requirement with least privilege? |
| Policy vs RBAC drill | Is the scenario about allowed actions or allowed configurations? |
| Storage access drill | Which access method or configuration fits the requirement? |
| NSG and routing drill | Why can or cannot traffic flow? |
| Monitoring drill | Which log, metric, alert, or diagnostic setting is relevant? |
| Backup and recovery drill | What protects the workload and how is it restored? |
14-day focused plan
Use this if you have two weeks and can study most days. The goal is to touch every major area, complete one full timed mock, and revisit weak topics.
14-day schedule
| Day | Focus | Study actions |
|---|---|---|
| 1 | Diagnostic | Take a timed diagnostic set. Build your weak-area tracker. |
| 2 | Identity basics | Users, groups, Microsoft Entra ID concepts, administrative units where relevant, access patterns. |
| 3 | RBAC and governance | Role assignments, scopes, policies, locks, tags, management hierarchy. |
| 4 | Storage accounts | Blob storage, Azure Files, access control, redundancy concepts, lifecycle and movement scenarios. |
| 5 | Compute I | VM deployment, disks, availability choices, extensions, backup considerations. |
| 6 | Compute II | Scale options, App Service basics, containers at an administrator level, operational management. |
| 7 | Mixed review | Targeted questions from Days 2-6. Fix repeat misses. Light lab cleanup. |
| 8 | Networking I | VNets, subnets, NSGs, routing, DNS fundamentals, peering. |
| 9 | Networking II | Load balancing, VPN/private connectivity concepts, troubleshooting traffic flow. |
| 10 | Monitoring | Azure Monitor, metrics, logs, alerts, activity logs, diagnostic settings. |
| 11 | Backup and recovery | Azure Backup, Recovery Services concepts, VM protection, restore scenarios. |
| 12 | Timed mock | Take a timed mock or large timed set. Review all missed and guessed questions. |
| 13 | Weak-area sprint | Re-study your weakest 2-3 topics. Use targeted practice only. |
| 14 | Final review | Review notes, comparison tables, and repeat misses. No new major topics. |
14-day study priorities
| Priority | What to do |
|---|---|
| Highest | Fix repeated missed-question patterns |
| High | Practice RBAC, networking, storage, and monitoring scenarios |
| Medium | Fill isolated knowledge gaps |
| Low | Memorize obscure details not tied to objectives or practice misses |
30-day balanced plan
Use this if you have about one month. This is the best fit for many working professionals because it allows time for learning, labs, and review.
Weekly structure
| Week | Main goal | Output by end of week |
|---|---|---|
| 1 | Establish Azure administration foundation | Diagnostic complete, identity/governance reviewed, first labs done |
| 2 | Build storage and compute confidence | Core storage and VM scenarios practiced |
| 3 | Master networking, monitoring, and backup | Traffic flow, observability, and recovery scenarios reviewed |
| 4 | Exam readiness | Timed mocks, weak-area sprint, final notes |
30-day schedule
| Day range | Focus | Actions |
|---|---|---|
| Days 1-2 | Diagnostic and exam map | Take a diagnostic set. Review Microsoft AZ-104 objective areas. Set up tracker. |
| Days 3-5 | Microsoft Entra ID and RBAC | Users, groups, roles, scopes, least privilege, administrative access. Do targeted questions. |
| Days 6-7 | Governance | Subscriptions, management groups, policy, locks, tags, resource organization. Complete a small governance lab. |
| Days 8-10 | Storage | Storage accounts, blob access, Azure Files, redundancy concepts, lifecycle, transfer tools. |
| Days 11-13 | Compute | VMs, disks, images, availability, backup, extensions, scale and management scenarios. |
| Day 14 | Review checkpoint | Timed mixed set. Update weak-area list. Revisit missed concepts. |
| Days 15-18 | Networking | VNets, subnets, NSGs, routes, peering, DNS, load balancing and connectivity scenarios. |
| Days 19-21 | Monitoring and backup | Azure Monitor, Log Analytics concepts, alerts, metrics, activity logs, backup and recovery. |
| Day 22 | Timed mock 1 | Take a timed mock. Review every missed and guessed question. |
| Days 23-25 | Weak-area labs | Rebuild or troubleshoot the areas you missed most. Focus on hands-on correction. |
| Days 26-27 | Timed mixed practice | Complete timed sets by domain. Practice reading scenarios quickly. |
| Day 28 | Timed mock 2 | Take another timed mock or full-length timed set. Compare miss patterns. |
| Day 29 | Final weak-area sprint | Review only repeat misses, comparison notes, and high-value scenarios. |
| Day 30 | Light final review | No new topics. Prepare exam logistics and rest. |
30-day lab checklist
| Area | Lab task |
|---|---|
| Identity and access | Assign RBAC at different scopes and verify what changes |
| Governance | Apply tags, create a policy assignment, test a resource lock |
| Storage | Create a storage account, configure blob access, test Azure Files conceptually or hands-on |
| Compute | Deploy a VM, attach or manage disks, review backup options |
| Networking | Build a VNet with subnets and NSGs, test traffic assumptions |
| Monitoring | Create alerts, inspect metrics, review activity logs and diagnostic settings |
| Recovery | Configure or review VM backup and restore decision points |
For lab work, use small disposable resources in an approved Azure environment and clean up when finished.
60/90-day full preparation path
Use this path if you are newer to Azure administration or want a less compressed schedule. A 60-day plan assumes steady study. A 90-day plan gives more time for labs, documentation review, and repeated practice.
60-day path
| Phase | Days | Focus | What to complete |
|---|---|---|---|
| Foundation | 1-10 | Azure administration basics and diagnostic | Skills outline review, diagnostic set, lab setup, identity overview |
| Identity and governance | 11-20 | Microsoft Entra ID, RBAC, policy, subscriptions | Role/scope labs, governance questions, comparison notes |
| Storage and compute | 21-35 | Storage accounts, files, blobs, VMs, backup, scale options | Storage and VM labs, targeted question sets |
| Networking | 36-45 | VNets, NSGs, routing, DNS, peering, load balancing | Traffic-flow labs and troubleshooting drills |
| Monitoring and operations | 46-52 | Azure Monitor, logs, alerts, backup, recovery | Observability and recovery scenarios |
| Mock and repair | 53-58 | Timed mocks and weak-area review | Two timed mocks or equivalent large timed sets |
| Final review | 59-60 | Exam consolidation | Repeat misses, final notes, no new major content |
90-day path
| Phase | Weeks | Focus | What to complete |
|---|---|---|---|
| Foundation | 1-2 | Azure platform, portal, CLI/PowerShell awareness, resource model | Build a basic resource group, review ARM concepts, start tracker |
| Identity and governance | 3-4 | Microsoft Entra ID, RBAC, policy, locks, tags, subscriptions | Hands-on governance labs and targeted questions |
| Storage | 5 | Storage accounts, blob, files, access, redundancy concepts, movement | Storage comparison notes and lab validation |
| Compute | 6-7 | VMs, disks, images, availability, backup, App Service basics | VM deployment and operational troubleshooting |
| Networking | 8-9 | VNets, subnets, NSGs, routes, DNS, peering, load balancing, connectivity | Network diagramming and traffic-flow practice |
| Monitoring and recovery | 10 | Azure Monitor, alerts, logs, activity logs, backup, recovery | Monitoring lab and recovery scenarios |
| First mock cycle | 11 | Timed mock and deep review | Full review of misses and guessed answers |
| Weak-area repair | 12 | Lowest-scoring areas | Re-lab and retest weak domains |
| Final readiness | 13 | Timed practice and final review | Final mock, repeat misses, exam-week checklist |
How to pace a longer plan
| Study frequency | Recommended pattern |
|---|---|
| 3 days per week | 1 topic day, 1 lab day, 1 practice/review day |
| 4 days per week | 2 topic/lab days, 1 targeted question day, 1 review day |
| 5 days per week | Shorter daily sessions with one timed set each week |
| Weekend-heavy | Use weekdays for notes/questions and weekends for labs/mocks |
Hands-on review guidance for AZ-104
AZ-104 is an administrator exam. You should be comfortable recognizing how Azure resources are configured, secured, monitored, and troubleshot.
Suggested hands-on pattern
For each service area:
- Read the objective topic.
- Configure a small example in Azure.
- Change one setting and observe the effect.
- Identify which permissions were needed.
- Review how it is monitored.
- Answer scenario questions on the topic.
- Delete or clean up lab resources.
Useful administration commands to recognize
You do not need to turn your study plan into a command memorization exercise, but basic Azure CLI or PowerShell familiarity helps reinforce administration workflows.
az group create --name rg-az104-lab --location eastus
az network vnet create --resource-group rg-az104-lab --name vnet-lab --address-prefix 10.10.0.0/16 --subnet-name subnet-web --subnet-prefix 10.10.1.0/24
az role assignment list --scope /subscriptions/<subscription-id>
Use commands like these to understand resource groups, networking, and RBAC scope. Do not spend final-week time memorizing syntax unless command usage is one of your weak areas.
When to use timed mock exams
Timed mocks are most useful after you have reviewed enough content to interpret the results.
| Timing | What to do |
|---|---|
| Start of plan | Use a shorter diagnostic set, not necessarily a full mock |
| Midpoint | Take a timed mixed set to identify weak areas |
| Final third | Take one full timed mock or large timed set |
| Final week | Take one final timed mock no later than 24-48 hours before the exam |
| Final day | Avoid full mocks; use light review and repeat misses |
How to review a timed mock
For every missed or guessed question, write:
- The topic area
- The scenario clue you missed
- The wrong assumption you made
- The correct Azure concept
- Whether you need a lab, a note, or more practice
Do not judge readiness only by one mock score. Look for stable performance, fewer repeat mistakes, and better timing.
High-value comparison tables to build
Create your own short tables for topics that commonly cause confusion.
| Compare | Question to answer |
|---|---|
| RBAC vs Azure Policy | Is the issue who can act, or what configurations are allowed? |
| NSG vs route table | Is traffic blocked by security rules or directed incorrectly? |
| Metrics vs logs | Do you need numeric time-series data or detailed event/query data? |
| Backup vs replication | Are you protecting against deletion/corruption or improving availability? |
| Blob access methods | Which access model fits the scenario and security requirement? |
| Load balancing options | Is the traffic internal, external, global, HTTP-based, or network-level? |
| Resource locks vs RBAC | Are you preventing deletion/changes or controlling user permissions? |
Final-week rules
Use these rules during the last seven days, even if you followed a 30-, 60-, or 90-day plan.
| Rule | Why |
|---|---|
| Stop adding major new material 48 hours before the exam | New topics create anxiety and rarely improve performance late |
| Review missed questions daily | Repeat misses are the highest-value study material |
| Prioritize weak domains | Balanced review is useful, but weak areas decide readiness |
| Practice timed reading | Many AZ-104 questions are scenario-based |
| Keep labs small | Final week is for confirmation, not exploration |
| Sleep and logistics matter | Fatigue causes misreads and poor time management |
Exam-readiness checks
You are likely ready when you can do most of the following without heavy notes:
| Readiness check | Yes/No |
|---|---|
| Explain RBAC scope and least-privilege role assignment decisions | |
| Distinguish Azure Policy, locks, tags, and RBAC | |
| Choose storage access and redundancy options based on requirements | |
| Diagnose basic VNet, subnet, NSG, route, DNS, and peering scenarios | |
| Select VM availability, backup, disk, and management options | |
| Identify which Azure Monitor feature fits a monitoring requirement | |
| Review a timed question set without running out of time | |
| Explain why your wrong answers were wrong | |
| Avoid repeating the same miss type across multiple sessions |
If several checks are still “No,” use your remaining time for targeted practice and hands-on confirmation instead of broad passive review.
Practical next step
Choose your time path today, take a diagnostic practice set, and build your missed-question tracker. Then study one AZ-104 objective area at a time: review the concept, configure a small Azure example, answer targeted questions, and repair every miss before moving on.