Skip to main content

Task 01: Virtual Network & Subnets

Runbook Azure

DOCUMENT CATEGORY: Runbook
SCOPE: Virtual network deployment
PURPOSE: Create management VNet and subnets
MASTER REFERENCE: Microsoft Learn - Virtual Networks

Status: Active

Overview​

This task creates the management Virtual Network (VNet) and all required subnets for Azure Local infrastructure. This VNet hosts management VMs (Domain Controllers, Utility Server, NDM Server, Lighthouse Server) and provides connectivity to on-premises via VPN.

Task Classification

Execution Target: Azure-Only (control-plane API operation) Tab Profile: 3 tabs — Azure Portal · PowerShell · Azure CLI

Terraform Reference

Module: azurelocal-toolkit File: network.tf Mode: Management

Components Created​

ResourceName PatternPurpose
Virtual Networkvnet-azrl-{env}-{region}-01Management address space
GatewaySubnetGatewaySubnetVPN Gateway (required name)
Management Subnetsnet-azrl-{env}-{region}-01Management VMs
Bastion SubnetAzureBastionSubnetAzure Bastion (required name, /26 min)
Endpoints Subnetsnet-endpoints-{env}-{region}-01Private Endpoints

Default Subnet Layout​

SubnetDefault CIDRNotes
GatewaySubnet10.x.x.0/27Required name, no NSG
snet-azrl-*10.x.x.32/27DCs, Utility, NDM, Lighthouse
AzureBastionSubnet10.x.x.64/26Required name, /26 minimum
snet-endpoints-*10.x.x.128/27Key Vault, Storage endpoints

Prerequisites​

  • Phase 01: Landing Zones completed — subscription and resource groups exist
  • Phase 03: RBAC Permissions completed — deployment identity has Network Contributor role
  • Network IP address ranges documented and confirmed (no conflicts with on-prem)
  • Landing zone model confirmed (Single Subscription or CAF/WAF)

Values from infrastructure.yml​

The script reads these keys from infrastructure.yml (schema 5). Each key, with its type, default and example, is in the variables reference.

azure.tenant_id, azure.location, tags
landing_zone.subscriptions[].name, .id the subscription of each network
landing_zone.networks[].name, .subscription, .resource_group, .location, .address_space, .dns_servers, .peer_with
landing_zone.networks[].subnets[].name, .prefix, .network_security_group, .route_table
landing_zone.networks[].allow_forwarded_traffic, .allow_gateway_transit, .use_remote_gateways the peering options (schema 5.6.23)

Peering options​

Deploy-VirtualNetworks.ps1 peers each network with the networks of its peer_with. A peering is made in both directions, and each direction uses the options of the network it starts in (Microsoft Learn: Virtual network peering).

KeyDefaultWhat it is
landing_zone.networks[].allow_forwarded_traffictrueWhether the peerings that start in this network accept traffic that was sent by a machine outside the peered network.
landing_zone.networks[].allow_gateway_transitfalseWhether the peerings that start in this network let the peer use the VPN or ExpressRoute gateway of this network. Set it on the hub that has the gateway. Cannot be true together with use_remote_gateways on the same network.
landing_zone.networks[].use_remote_gatewaysfalseWhether the peerings that start in this network use the gateway of the peer. Set it on the spokes. The peer must set allow_gateway_transit to true and have a gateway.
landing_zone:
networks:
- name: vnet-iic-hub-01
allow_gateway_transit: true # the hub has the VPN gateway
- name: vnet-iic-mgmt-01
peer_with: ["vnet-iic-hub-01"]
use_remote_gateways: true # the spoke uses the hub's gateway

Single Subscription Model​

In the single subscription model, all management infrastructure is deployed to a single subscription under one resource group.

Landing Zone Placement​

FieldValueConfig Path
SubscriptionCustomer subscriptionlanding_zone.subscriptions[].id
Resource Grouprg-azrlmgmt-{env}-{region}-01landing_zone.networks[].resource_group
VNet Namevnet-azrl-{env}-{region}-01landing_zone.networks[].name
LocationAzure regionlanding_zone.networks[].location
Address Space10.x.x.0/24landing_zone.networks[].address_space

Execution Options​

Azure Portal​

When to use: Learning Azure Local, single deployment, prefer visual interface

Procedure​

  1. Navigate to Virtual Networks:
  • In Azure Portal, search for Virtual networks
  • Click + Create
  1. Basics tab: | Field | Value | Source | |-------|-------|--------| | Subscription | Your subscription | landing_zone.subscriptions[].id | | Resource group | rg-azrlmgmt-{env}-{region}-01 | landing_zone.networks[].resource_group | | Virtual network name | vnet-azrl-{env}-{region}-01 | landing_zone.networks[].name | | Region | Your region | landing_zone.networks[].location |

  2. IP Addresses tab:

  • Set IPv4 address space to value from landing_zone.networks[].address_space
  • Add subnets:
Subnet NameAddress RangeSource
GatewaySubnet/27 rangelanding_zone.networks[].subnets[].prefix
Management subnet/27 rangelanding_zone.networks[].subnets[].prefix
AzureBastionSubnet/26 rangelanding_zone.networks[].subnets[].prefix
Endpoints subnet/27 rangelanding_zone.networks[].subnets[].prefix
  1. Security tab: Leave defaults (no Bastion/Firewall/DDoS at this stage)

  2. Tags tab: Apply standard tags per tags.* config paths

  3. Review + create: Verify settings → Click Create

Validation​

  • VNet created successfully in the correct resource group
  • All four subnets visible under the VNet
  • Address space matches landing_zone.networks[].address_space
  • GatewaySubnet has no NSG attached

Validation​

  • VNet created in the correct resource group
  • All four subnets present with correct CIDRs
  • GatewaySubnet has no NSG attached
  • Address space does not conflict with on-premises networks

CAF/WAF Landing Zone Model​

In the CAF/WAF model, networking resources are deployed to the Connectivity subscription under the Connectivity management group, separate from management and identity resources.

Landing Zone Placement​

FieldValueConfig Path
SubscriptionConnectivity subscriptionlanding_zone.subscriptions[].id
Resource Grouprg-azrlconn-{env}-{region}-01landing_zone.networks[].resource_group
VNet Namevnet-azrl-{env}-{region}-01landing_zone.networks[].name
LocationAzure regionlanding_zone.networks[].location
Address Space10.x.x.0/24landing_zone.networks[].address_space
Different Subscription Target

In CAF/WAF, this VNet is created in the Connectivity subscription — not the same subscription as management VMs. VNet peering or cross-subscription subnet references may be required for VM NICs.

Execution Options​

Azure Portal​

When to use: Learning Azure Local, single deployment, prefer visual interface

Procedure​

  1. Navigate to Virtual Networks:
  • In Azure Portal, search for Virtual networks
  • Click + Create
  1. Basics tab: | Field | Value | Source | |-------|-------|--------| | Subscription | Connectivity subscription | landing_zone.subscriptions[].id | | Resource group | rg-azrlconn-{env}-{region}-01 | landing_zone.networks[].resource_group | | Virtual network name | vnet-azrl-{env}-{region}-01 | landing_zone.networks[].name | | Region | Your region | landing_zone.networks[].location |

  2. IP Addresses tab:

  • Set IPv4 address space to value from landing_zone.networks[].address_space
  • Add subnets identical to Single Subscription model (same names, same CIDRs)
  1. Security tab: Leave defaults

  2. Tags tab: Apply standard tags per tags.* config paths

  3. Review + create: Verify settings → Click Create

Validation​

  • VNet created in the Connectivity subscription and resource group
  • All four subnets visible under the VNet
  • Address space matches config
  • GatewaySubnet has no NSG attached

Validation​

  • VNet created in the Connectivity subscription resource group
  • All four subnets present with correct CIDRs
  • Address space does not conflict with on-premises or other VNets
  • GatewaySubnet has no NSG attached

Troubleshooting​

IssueRoot CauseRemediation
Address space overlapsConflict with existing VNet or on-prem rangeChoose non-overlapping CIDR from Planning & Discovery
Subnet creation failsAddress prefix outside VNet address spaceVerify subnet CIDRs fit within VNet CIDR
GatewaySubnet too smallLess than /27Use /27 minimum for VPN Gateway
AzureBastionSubnet too smallLess than /26Use /26 minimum for Azure Bastion
Permission deniedMissing Network Contributor roleVerify RBAC from Phase 03


Alternatives​

The procedures in this task use the methods shown in the tabs above. The toolkit is PowerShell 7 only and has no Bash scripts. A few tasks that act on Azure also have an Azure CLI script written in PowerShell. The script status page of the toolkit lists which task has which script.

PreviousUpNext
Manual Deployment IndexManual Deployment IndexTask 02: VPN Gateway

Version Control

  • Created: 2025-09-15 by Hybrid Cloud Solutions
  • Last Updated: 2026-03-03 by Hybrid Cloud Solutions
  • Version: 4.0.0
  • Tags: azure-local, virtual-network, subnets, networking, management-infrastructure
  • Keywords: virtual network, VNet, subnets, GatewaySubnet, AzureBastionSubnet, IP addressing
  • Author: Hybrid Cloud Solutions

Version Control​

VersionDateAuthorChanges
1.0.02025-03-25Azure Local CloudInitial release