Study guide

7.1 VNet, Subnet, and Address Space Design

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

7.1 VNet, Subnet, and Address Space Design

Key Takeaways Explain This Topic AI

A VNet is a regional private address boundary, and subnets are the control points for delegation, NSGs, route tables, private endpoints, and service endpoints.

Address spaces must be planned to avoid overlap with peered VNets, VPN-connected networks, and future expansion ranges.

Azure reserves addresses in every subnet, so administrator sizing must include usable addresses plus growth, platform services, and scale-out behavior.

Subnet changes can be blocked by existing resources, delegations, private endpoints, or route and security dependencies.

AZ-104 scenarios often test whether a candidate can place the right resource in the right subnet instead of just creating a larger VNet.

Last updated: May 2026

Design the address plan first

An Azure virtual network, or VNet, is a regional private network that uses address prefixes you choose. It is not automatically global, and it does not automatically connect to other VNets, on-premises networks, or the internet in a way that bypasses Azure controls. The address plan is the first administrator decision because route tables, peering, VPN connectivity, private endpoints, and service integration all depend on non-overlapping prefixes.

The most important AZ-104 rule is simple: do not overlap address spaces that must communicate. If VNetA uses 10.10.0.0/16 and VNetB also uses 10.10.0.0/16 , normal peering will not solve that conflict. The same problem appears when a corporate network already uses 10.0.0.0/8 broadly and an Azure team casually creates VNets inside that range. Exam case studies often hide this inside a requirement such as connect two VNets or connect a VNet to the datacenter.

A practical design starts with a table like this:

Network Prefix Purpose Notes

hub-vnet-eastus 10.40.0.0/16 Shared firewall, Bastion, DNS, gateways Leave room for gateway and firewall subnets.

spoke-app-prod 10.41.0.0/16 Production app workloads Peer to hub, no overlap with on-premises.

spoke-data-prod 10.42.0.0/16 Data tier and private endpoints Separate private endpoint subnet if operations require it.

on-premises 172.20.0.0/16 Corporate network Must not overlap Azure prefixes.

Subnet sizing and Azure reservations

A subnet is a range inside the VNet address space. Azure reserves addresses in each subnet, so the number of usable addresses is smaller than the raw CIDR count. That matters when selecting a subnet for scale sets, Azure Bastion, private endpoints, App Service VNet integration, Azure Firewall, or application tiers that may scale out.

Do not size a subnet only for today's virtual machines. Count expected growth, IPs consumed by platform services, private endpoints, load balancer backends, blue-green deployments, and temporary migration overlap. A subnet that looks acceptable for two VMs can become a blocker when the same application later needs 20 instances, a private endpoint, and additional test nodes.

Common subnet patterns:

Subnet Typical purpose Design warning

AzureBastionSubnet Azure Bastion Must use the required name and needs enough space for scale and platform requirements.

GatewaySubnet VPN or ExpressRoute gateway Must use the required name and should not host normal workloads.

AzureFirewallSubnet Azure Firewall Must use the required name and should be sized for firewall deployment.

workload subnet VMs, scale sets, app tiers Attach NSG and route table based on tier behavior.

private endpoint subnet Private endpoints to PaaS services Private endpoint NICs consume IPs and change service access path.

delegated subnet App Service integration, Container Apps, database services, or other services Delegation limits which resource type can use the subnet.

Resource placement is an exam skill

AZ-104 is not asking you to memorize only definitions. It asks whether you can place resources correctly. A VPN gateway belongs in GatewaySubnet , not a random workload subnet. Azure Bastion belongs in AzureBastionSubnet , not beside a VM NIC. A private endpoint creates a NIC in a subnet, so it needs available addresses and appropriate DNS. A service endpoint is enabled on a subnet and changes the path to a supported Azure service, but it does not create a private IP for that service in your VNet.

Portal path: Azure portal > Virtual networks > Create for the VNet and initial subnet. After creation, use Virtual networks > <vnet> > Subnets to add subnets, associate NSGs, associate route tables, enable service endpoints, or configure delegation.

  • CLI example: az network vnet create \
  • -resource-group rg-network \
  • -name vnet-prod-eastus \
  • -location eastus \
  • -address-prefixes 10.41.0.0/16 \
  • -subnet-name snet-web \
  • -subnet-prefixes 10.41.1.0/24
  • az network vnet subnet create \
  • -resource-group rg-network \
  • -vnet-name vnet-prod-eastus \
  • -name snet-app \
  • -address-prefixes 10.41.2.0/24
  • Changing subnets safely

Administrators often need to add, resize, or split subnets. The safe workflow is to inspect what is already using the subnet, confirm there is no overlap with existing subnets, verify route table and NSG dependencies, check delegations, and confirm whether resources must be moved or recreated. You cannot freely shrink a subnet around existing IP addresses. You also cannot assign a prefix that overlaps another subnet in the same VNet.

A basic troubleshooting flow:

If subnet creation fails, check for overlap with existing VNet address spaces and subnets.

If a subnet cannot be deleted, list NICs, private endpoints, delegated resources, and service associations.

If a VM cannot be moved into a subnet, check the VM NIC, subnet availability, NSG rules, route table, and whether the resource type is allowed.

If the subnet has no more addresses, resize if possible or create a new subnet and migrate resources by planned redeployment.

  • Useful commands: az network vnet show -g rg-network -n vnet-prod-eastus --query addressSpace.addressPrefixes
  • az network vnet subnet list -g rg-network --vnet-name vnet-prod-eastus -o table

az network nic list -g rg-network --query "[?ipConfigurations[0].subnet.id!=null].[name, ipConfigurations[0].privateIPAddress]" -o table

Design traps

Do not assume every resource in a VNet can talk to every other resource in every VNet. A VNet gives private addressing inside its boundary, but communication across VNets needs peering, VPN, ExpressRoute, or another connectivity pattern. Do not assume a public IP is required for VM-to-VM communication inside the same VNet. Private IPs are used by default inside the VNet.

Do not place management services in workload subnets just because the portal allows subnet selection. Required platform subnet names are significant. Do not choose tiny subnets for services that may scale. Do not ignore future peering or hybrid connectivity; overlap discovered after production deployment is expensive to fix.

A final exam trap is confusing subnet security with address assignment. Creating a subnet does not automatically deny inbound traffic between its VMs. Azure has default NSG rules, and if no NSG is associated, you have fewer filtering controls. Proper subnet design usually pairs addressing with NSGs, route tables, DNS decisions, and private access choices.