Study guide
1.2 Administrator Role and Candidate Profile
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.2 Administrator Role and Candidate Profile
Key Takeaways Explain This Topic AI
AZ-104 candidates should have subject matter expertise in implementing, managing, and monitoring Azure environments.
The role spans virtual networks, storage, compute, identity, security, and governance.
Administrators often coordinate with networking, security, database, application development, and DevOps roles.
PowerShell, Azure CLI, Azure portal, ARM templates or Bicep, and Microsoft Entra ID are expected tools.
The exam rewards operational decision-making more than vocabulary recognition.
Last updated: May 2026
What Microsoft means by Azure administrator
The AZ-104 candidate is expected to have subject matter expertise in implementing, managing, and monitoring an organization's Microsoft Azure environment. That phrase is more important than it looks. It means the exam is not asking whether you have heard of a storage account, a virtual network, a role assignment, or an alert rule. It is asking whether you can make those resources work together under constraints.
The administrator role covers virtual networks, storage, compute, identity, security, and governance. Those areas do not stay separate in real environments. A VM question may require understanding managed disks, availability zones, network security groups, Bastion, Azure Monitor, backup policy, and role-based access control. A storage question may require firewall rules, private endpoints, lifecycle management, SAS token scope, and identity-based access for Azure Files.
Administrator area What the exam can make you decide
Identity Which user, group, role, assignment scope, or Microsoft Entra setting fits the requirement.
Governance Whether tags, locks, policy, management groups, budgets, or Advisor recommendations solve the problem.
Storage Which redundancy, access, firewall, SAS, lifecycle, snapshot, or soft-delete setting matches the scenario.
Compute Whether to use VM, scale set, App Service, container instance, Container Apps, ACR, ARM, or Bicep.
Networking How to connect, isolate, route, secure, publish, and troubleshoot Azure network paths.
Monitoring Which metric, log, alert, insight, backup, or failover tool supports operations.
Microsoft also states that candidates often work with networking, security, database, application development, and DevOps roles. That is an exam clue. AZ-104 does not require you to be the database engineer or application developer, but it expects you to administer the Azure platform around them. You might grant access to a managed identity, configure App Service networking, apply policy to a subscription, expose an internal load balancer, or diagnose why a route table sends traffic to the wrong appliance.
Tool expectations
The profile names experience with PowerShell, Azure CLI, Azure portal, Azure Resource Manager templates or Bicep files, and Microsoft Entra ID. Do not read that as a list of optional extras. The exam can describe an admin task and expect you to recognize the fastest or most appropriate control plane. The portal is useful for discovery and one-off configuration. Azure CLI and PowerShell are better for repeatable commands, automation, and scripted troubleshooting. ARM and Bicep appear when the question is about declarative deployment, template interpretation, export, conversion, or modification.
- Task pattern Likely tool decision
- Explore an unfamiliar resource and inspect effective settings Azure portal
- Repeat a resource change across many objects Azure CLI or PowerShell
- Deploy consistent infrastructure from source control Bicep or ARM template
- Assign Azure role access at the correct scope Portal, CLI, PowerShell, or IaC depending on repeatability
Investigate Microsoft Entra users, groups, SSPR, and external users Microsoft Entra admin experience and Azure role context
From vocabulary to operations
A vocabulary-only learner says, "An NSG filters traffic." An administrator says, "I need to inspect effective security rules on the NIC and subnet, confirm priority order, check whether an application security group is referenced, and compare that with route and load balancer behavior." That difference is the AZ-104 level. The same pattern applies everywhere. Knowing that a resource lock exists is not enough; know that a delete lock can block deletion, that a read-only lock can block management operations, and that RBAC permissions do not override a lock.
A vocabulary-only learner says, "Blob lifecycle management moves data to cool or archive." An administrator asks whether versioning, soft delete, snapshots, access tier, legal or retention settings, and access patterns support the required recovery and cost outcome. When a question says "least administrative effort" or "minimize cost," those phrases steer the answer just as much as the service name.
Candidate readiness checklist
You can create and troubleshoot users, groups, role assignments, policy, locks, tags, and budgets.
You can configure storage access with keys, SAS, stored access policies, identity, network rules, and private access patterns.
You can deploy and manage VMs, scale sets, containers, App Service plans, deployment slots, custom domains, certificates, and backups.
You can design and troubleshoot VNets, subnets, peering, public IPs, UDRs, NSGs, ASGs, Bastion, endpoints, DNS, and load balancers.
You can configure metrics, logs, alerts, action groups, processing rules, insights, Network Watcher, backup, restore, and failover.
You can read a Bicep or ARM fragment and predict the deployed result.
Scenario recognition
When a scenario includes "organization," think governance scope. Management groups, subscriptions, resource groups, tags, policy, and budgets are likely. When it includes "developer team," think least-privilege access, deployment repeatability, and integration with DevOps workflows. When it includes "branch office," "on-premises," or "cannot connect," think DNS, routes, NSGs, peering, endpoints, and Network Watcher.
When it includes "restore," "accidental deletion," or "ransomware," think soft delete, backup vaults, Recovery Services vaults, snapshots, versioning, and restore points. When it includes "scale," ask whether the workload is VM-based, App Service-based, container-based, or a VM scale set. When it includes "compliance," ask whether Azure Policy, locks, tags, management groups, resource graph, logs, or role assignments is the actual control.
The correct mindset is operational ownership. You are not memorizing service brochures. You are deciding which Azure control solves a requirement, which side effect it creates, and how to validate that it worked.