Study guide

11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths

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

11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths

Key Takeaways Explain This Topic AI

AZ-104 is a strong administrator base for architecture, DevOps, security, and operations career paths.

AZ-305 extends administrator experience into solution design and architecture decisions.

AZ-400 fits candidates moving toward DevOps, delivery automation, source control, pipelines, and platform engineering.

SC-500 fits candidates moving toward Azure security administration, identity protection, platform security, and threat response.

Career growth after AZ-104 should be based on the work you want to do, not only on collecting the next exam code.

Last updated: October 2026

Choosing the next path after AZ-104

AZ-104 is not an endpoint. It is a working administrator foundation. The certification validates that you can implement, manage, monitor, and troubleshoot an Azure environment across identity, governance, storage, compute, networking, monitoring, backup, and maintenance. Those skills transfer directly into architecture, DevOps, security, platform engineering, and operations roles.

Do not choose the next exam only because it is popular. Choose based on the work you want to do and the gaps between your current job and that work. AZ-305, AZ-400, and SC-500 each build on Azure administration in a different direction. A strong AZ-104 candidate can move into any of them, but the study focus changes.

Path Best fit How AZ-104 helps

AZ-305 Solution architecture You know the operational behavior behind design choices.

AZ-400 DevOps engineering You understand Azure resources that pipelines deploy and operate.

SC-500 Azure security You already work with identity, RBAC, networking, governance, and monitoring.

Cloud admin Operations depth You can harden, automate, monitor, and recover real environments.

Platform engineer Shared Azure platform You can package governance, networking, compute, and observability for teams.

AZ-305 after AZ-104

AZ-305 is a natural next step for administrators who want to design Azure infrastructure solutions. AZ-104 asks whether you can implement and manage resources. Architecture asks whether you can choose the right pattern across availability, resiliency, identity, data, governance, migration, network topology, monitoring, and cost. The administrator background is valuable because you know which designs are easy to operate and which ones create hidden work.

If you move toward AZ-305, strengthen design tradeoffs. Practice explaining why a workload needs availability zones, region pairs, backup, Site Recovery, private connectivity, hub-spoke networking, managed identities, policy, or a particular data service. Keep the AZ-104 habit of validation, but add design language: requirements, constraints, risks, tradeoffs, and operational impact.

AZ-400 after AZ-104

AZ-400 fits candidates moving toward DevOps engineering, release automation, infrastructure as code, source control, CI/CD, observability, and collaboration between development and operations. AZ-104 already gives you the resource model: resource groups, RBAC, Bicep or ARM, App Service, containers, registries, networking, monitoring, and recovery. AZ-400 asks you to manage the delivery system around those resources.

If you choose AZ-400, deepen Git, branching strategy, pipeline design, artifact management, deployment strategies, secret handling, infrastructure as code, test automation, monitoring feedback, and incident learning. Practice deploying Azure resources with Bicep from a pipeline and promoting changes through environments. Learn how deployment slots, container registries, managed identities, and role assignments behave when automated.

SC-500 after AZ-104

SC-500 (Cloud and AI Security Engineer Associate) replaced AZ-500 on August 31, 2026, and adds security for AI workloads to the Azure security engineering skills. It fits candidates moving toward Azure security engineering. AZ-104 already covers Microsoft Entra users and groups, RBAC, governance, NSGs, private endpoints, storage access, monitoring, and backup. SC-500 goes deeper into securing identity, platform, data, applications, and operations. It expects more security-specific reasoning around least privilege, threat protection, posture management, key management, network isolation, and incident response.

If you choose SC-500, strengthen Microsoft Entra security, privileged access, conditional access concepts, managed identities, Key Vault, Defender for Cloud, secure networking, storage protection, logging, Sentinel-adjacent operations where relevant to your path, and response workflows. Keep the AZ-104 discipline of checking effective configuration. Security answers often fail when candidates rely on intended design instead of actual applied settings.

Job paths from AZ-104

The most direct job path is Azure administrator or cloud administrator. In that role, AZ-104 maps closely to daily work: user and group support, role assignments, policy compliance, storage accounts, VMs, App Service, networking, monitoring, backup, restore, and cost hygiene. To become stronger, add scripting, repeatable deployment, incident response, and documentation skills.

A platform engineering path uses AZ-104 as the base for building reusable Azure patterns. You might own landing zones, subscription vending, policy initiatives, role models, shared networking, DNS, private endpoint standards, image pipelines, monitoring baselines, and backup standards. This path rewards automation and empathy for application teams.

A cloud network operations path leans into VNets, peering, route tables, firewalls, DNS, Bastion, private endpoints, load balancers, hybrid connectivity, Network Watcher, and connection troubleshooting. A cloud infrastructure operations path leans into compute, patching, backup, restore, scale, cost, and monitoring. A security operations path leans into identity, access review, logging, alerts, Defender signals, incident response, and governance.

Building a portfolio after the exam

After passing, create small projects that prove you can operate Azure. Examples include a hub-spoke lab with private endpoint DNS, a Bicep deployment for a monitored App Service with slot swap, a storage account with private access and lifecycle rules, or a VM workload with backup, alerts, and recovery testing. Keep the projects small enough to finish and documented enough to discuss in interviews.

Use job descriptions as a study guide. If target roles mention Terraform, GitHub Actions, Azure DevOps, Kubernetes, Sentinel, Defender for Cloud, or hybrid networking, decide whether those belong in your next learning cycle. AZ-104 gives the base, but role readiness comes from combining certification knowledge with tools used by the teams you want to join.

The strongest post-AZ-104 path is intentional. Choose AZ-305 if you want to design. Choose AZ-400 if you want to automate delivery. Choose SC-500 if you want to secure Azure. Stay in administration if you want deeper operations ownership. In every path, the administrator foundation remains useful because real cloud roles reward people who understand how Azure behaves after the diagram is deployed.