Study guide
5.1 ARM Templates, Bicep, and Deployment Workflow
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
5.1 ARM Templates, Bicep, and Deployment Workflow
Key Takeaways Explain This Topic AI
ARM templates and Bicep describe desired Azure resource state and are deployed through Azure Resource Manager at subscription, resource group, management group, or tenant scope.
Bicep is the preferred authoring language for most administrator scenarios because it compiles to ARM JSON while remaining easier to read and modify.
Use what-if, validation, deployment names, parameters, outputs, and deployment history to predict and troubleshoot infrastructure changes.
Exported templates are useful for discovery, but exam scenarios usually expect you to simplify, parameterize, and redeploy rather than blindly reuse exported JSON.
Last updated: May 2026
Deployment Model
Azure Resource Manager is the control plane for most Azure resources. When you create a virtual machine in the portal, run az vm create , deploy a Bicep file, or submit an ARM template, the request is evaluated by ARM. ARM checks identity, RBAC, policy, resource provider registration, location availability, dependencies, quotas, and resource properties before the target resource provider creates or updates the resource.
For AZ-104, the important point is that templates are not a separate provisioning engine. They are a repeatable way to send the same desired-state request to ARM. You should be comfortable reading a template, finding the resource type, API version, location, name, properties, dependencies, parameters, and outputs. You should also be able to choose the right deployment scope.
- Scope Common command Use case Exam clue
- Resource group az deployment group create VMs, NICs, disks, NSGs, public IPs Most compute deployments
Subscription az deployment sub create Resource groups, policy assignments, role assignments Template creates the resource group
Management group az deployment mg create Governance across subscriptions Policy or initiative at hierarchy level
- Tenant az deployment tenant create Tenant-level configuration Rare administrator scenario
- Bicep Versus ARM JSON
ARM templates are JSON documents. They are powerful, but complex expressions and nested objects can be hard to maintain. Bicep is a domain-specific language that compiles to ARM JSON. It uses symbolic names, cleaner parameters, modules, loops, and conditionals. You can decompile many ARM templates with az bicep decompile , but decompilation is a starting point, not guaranteed production-quality code.
A compact Bicep deployment for a VM support resource might look like this: param location string = resourceGroup().location
- param vnetName string = 'vnet-prod-compute'
- param subnetName string = 'snet-vms'
- resource vnet 'Microsoft.Network/virtualNetworks@2024-05-01' = {
- name: vnetName
- location: location
- properties: {
- addressSpace: {
- addressPrefixes: [
- '10.40.0.0/16'
- ]
- }
- subnets: [
- {
- name: subnetName
- properties: {
- addressPrefix: '10.40.1.0/24'
- }
- }
- ]
- }
- }
output subnetId string = vnet.properties.subnets[0].id
The equivalent ARM template would contain the same resource provider type and properties but with JSON syntax, parameters, variables, and expression strings such as [resourceGroup().location] . In exam questions, Bicep answers often stand out because the symbolic resource name is used for dependency tracking. Explicit dependsOn is still possible, but Bicep usually infers dependencies when one resource references another.
Deployment Workflow
A practical workflow starts with a small, validated file. Use parameters for names, locations, VM sizes, admin usernames, environment labels, and settings that vary between dev, test, and production. Avoid hard-coding passwords. Use secure parameters, Key Vault references, managed identities, or deployment-time secrets handled by your pipeline.
- Typical CLI workflow: az login
- az account set --subscription 00000000-0000-0000-0000-000000000000
- az group create --name rg-prod-compute --location eastus
- az deployment group what-if \
- -resource-group rg-prod-compute \
- -template-file main.bicep \
- -parameters vmName=vm-app-01 adminUsername=azureadmin
- az deployment group create \
- -name vm-build-20260505 \
- -resource-group rg-prod-compute \
- -template-file main.bicep \
- -parameters @prod.parameters.json
Use what-if before changes that may replace, delete, or reconfigure resources. A deployment mode also matters. Incremental mode updates or creates resources defined in the template and leaves unrelated resources alone. Complete mode can delete resources not present in the template at the deployment scope. Complete mode is dangerous in shared resource groups and should not be selected casually in an exam scenario.
Parameters, Outputs, and Modules
A parameter file keeps environment values separate from reusable logic. Secure values should not be committed. Outputs are useful when later deployments need IDs, host names, or principal IDs. Modules let you split a design into network, VM, monitoring, and backup pieces. param location string
param vmNames array
- module vmModule './modules/windows-vm.bicep' = [for vmName in vmNames: {
- name: 'deploy-${vmName}'
- params: {
- location: location
- vmName: vmName
- }
- }]
Loops are common for VM Scale Sets, diagnostic settings, role assignments, and repeated resource creation. The exam may ask you to identify a syntax issue, missing parameter, bad scope, or invalid dependency. Read the error and locate the layer: template parsing, ARM validation, Azure Policy denial, RBAC denial, provider registration, quota, or resource provider runtime error.
Export and Convert
The portal can export a template from a resource group or from deployment history. Export is useful for learning the property shape of a VM, disk, NIC, or scale set. It often includes generated names, defaults, read-only properties, and values you should parameterize or remove. For study purposes, compare the exported resource type with Microsoft Learn examples and current API versions.
- Command examples: az group export --name rg-prod-compute > exported.json
- az bicep decompile --file exported.json
- az bicep build --file main.bicep
A common troubleshooting scenario is a deployment that works in one subscription but fails in another. Check whether the destination subscription has the resource provider registered, the VM family quota available in the selected region, the same policy assignments, the same allowed locations, and permissions at the target scope. The same template can fail because the environment is different.
Troubleshooting Tree
Symptom First check Likely fix
AuthorizationFailed Role assignment at deployment scope Assign Contributor, VM Contributor plus network rights, or a custom role
InvalidTemplate Syntax, parameter name, function, scope Build Bicep locally and validate deployment
RequestDisallowedByPolicy Policy assignment and exemption Choose allowed SKU, tag, location, or request exemption
- SkuNotAvailable Region and VM size Pick a supported region or size
- OperationNotAllowed quota Compute usage and limits Request quota increase or choose another family
- Resource provider error Activity log and deployment operations Fix resource-specific properties
In the portal, use Resource group > Deployments > deployment name > Deployment details to inspect failed operations. In CLI, use az deployment operation group list --resource-group rg-prod-compute --name vm-build-20260505 . The failed child operation usually contains more useful detail than the top-level deployment status.
Scenario Recognition
If a question asks for repeatable VM deployment across environments, choose Bicep or ARM templates. If it asks for one-time manual creation, the portal or CLI may be sufficient. If it asks to preview effects, choose what-if. If it asks to create resource groups and then VMs in one file, use subscription-scope deployment with modules or nested deployments. If it asks to simplify an exported template, remove read-only properties, parameterize environment differences, and keep only required resource definitions.
On the exam, do not assume Microsoft Learn access means you can research every syntax detail. Role-based exams can provide Learn access, but no extra exam time is added and access excludes Q&A, Practice Assessments, and profile. Know the deployment workflow well enough to answer from the scenario.