Study guide
1.5 Scoring, Retakes, Renewal, and Account Choice
AZ-104 Microsoft Azure Administrator Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Orientation and Microsoft Learn Source Control
1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log
2 Chapter 2: Identity, RBAC, and Governance Foundations
2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab
3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization
3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab
4 Chapter 4: Storage Accounts, Access, and Data Protection
4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab
5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep
5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab
6 Chapter 6: Containers, App Service, and Platform Compute
6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab
7 Chapter 7: Virtual Networking, Routing, and Secure Access
7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab
8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting
8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab
9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery
9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab
10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs
10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab
11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path
11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths
1.5 Scoring, Retakes, Renewal, and Account Choice
Key Takeaways Explain This Topic AI
The passing score for AZ-104 is 700 or greater.
After a first failed attempt, the candidate must wait 24 hours before retaking.
After subsequent failed attempts, a 14-day waiting period applies, up to five attempts within a 12-month period from the first attempt.
A passed exam cannot be retaken unless the certification has expired.
Microsoft recommends registering with a personal Microsoft account so exam records are not lost when leaving an organization.
Last updated: May 2026
Scoring is a threshold, not a public percentage story
The AZ-104 passing score is 700 or greater. Do not convert that into a claimed percentage and do not attach a public pass-rate statistic. Microsoft does not publish a public AZ-104 pass-rate percentage. A score report can help identify weaker areas, but it is not a complete diagnostic transcript of every mistake. Use the result to refine study, then return to hands-on practice and official objectives.
A passing score should be treated as the minimum certification threshold, not proof that every operational skill is complete. Azure administrators still need to maintain real environments after the exam. If you barely pass while missing networking or backup concepts, keep those notes. Certification is a milestone; production administration requires continued accuracy.
Rule or fact Current value Planning effect
Passing score 700 or greater Aim above the threshold in practice to leave margin.
Public pass rate Not published by Microsoft Ignore vendor claims that imply official pass-rate certainty.
First failure wait 24 hours Do not schedule an immediate same-day retake.
Later failure wait 14 days between subsequent attempts Build remediation time into your plan.
Attempt limit Five attempts in 12 months from first attempt Avoid using paid attempts as practice sessions.
Passed exam retake Not allowed unless certification expired You cannot retake just to improve a passing score.
Renewal Every 12 months Track expiration and renew before it lapses.
Retake policy behavior
If a candidate does not pass the first time, Microsoft requires a 24-hour wait before retaking. A 14-day waiting period applies between all subsequent attempts, up to five attempts. A candidate may not take a given exam more than five times within a 12-month period from the first attempt. Retake fees apply when applicable. A passed exam cannot be retaken unless the certification has expired.
That policy should change how you prepare. A first attempt should not be a paid diagnostic if you already know you have weak domains. Use the local practice bank, hands-on labs, and an error log first. If you fail, do not spend the 24-hour wait rereading everything randomly. Sort the score feedback and your remembered misses into domains. Then pick two or three causes: missing product knowledge, poor scenario reading, command confusion, or time pressure.
Post-failure remediation checklist
Write down remembered topics immediately after leaving the exam center or online session.
Map each weak area to an official domain, not to a vague feeling such as "Azure is hard."
Rebuild one lab for each missed operational pattern.
Redo only relevant practice questions first, then mix domains again.
Update the error log with the cause of each miss and the rule that fixes it.
Reschedule only after practice results are stable and explanations are clear.
Renewal cycle
The Azure Administrator Associate certification can be renewed at no cost by passing an online assessment on Microsoft Learn. The renewal frequency is 12 months. Renewal is not the same as the original proctored exam. The renewal path is tied to keeping an active certification current, so do not wait until after expiration to learn the rules.
Renewal also reinforces why source control matters. Azure features and exam objectives change. A candidate who passed under an earlier outline may still need to refresh knowledge about newer service behavior, governance controls, monitoring capabilities, or portal workflow. Keep a lightweight renewal file with the certification expiration date, Microsoft Learn renewal link, and two or three weak domains to revisit.
Account choice
Microsoft recommends registering with a personal Microsoft account so exam records are not lost when leaving an organization. This is practical advice. Work accounts can change when you leave a company, move tenants, or lose access to an employer-managed identity. Certification history should follow the person who earned it.
Use a personal Microsoft account for the certification profile unless your organization has a specific policy that requires another arrangement. If employer benefits, vouchers, or learning portals are involved, confirm how those attach to the exam registration without surrendering long-term control of the certification record. Keep account recovery methods current before exam day. A locked account near renewal time is an avoidable administrative problem.
Account decision Risk Better control
Use only an employer account Loss of access after job change Register with a personal Microsoft account when possible.
Use outdated recovery email Renewal or transcript access failure Update recovery methods before scheduling.
Mix multiple profiles Split certification records Consolidate or verify profile links before testing.
Ignore expiration notices Certification lapses Track renewal date in a calendar.
Study margin and retake economics
Because retake fees may apply and waiting periods can delay career or project goals, build a passing margin before the first attempt. In practice, that means you should be able to explain why each correct answer is correct and why each distractor is wrong. A raw practice score without explanation is fragile. If you guessed correctly on private endpoints, RBAC scope, backup vault selection, or App Service slots, treat it as a miss in your error log.
The strongest retake plan is prevention. Do hands-on work before the first appointment. Keep notes tied to official domains. Drill scenario wording such as "least privilege," "minimize administrative effort," "prevent deletion," "allow only selected networks," "restore to a point in time," and "identify the cause." Those phrases determine the control you choose.
If you do need a retake, use the policy as a pacing structure. The first 24 hours are for capture and triage. The next study block is for labs. The final block is for mixed practice and time management. Do not simply reread the same chapter and hope recognition improves.