Skip to main content

Task 11: Deploy Management VMs

Runbook Azure

DOCUMENT CATEGORY: Runbook
SCOPE: Management VM provisioning
PURPOSE: Deploy all management VMs from Azure Marketplace images
MASTER REFERENCE: Microsoft Learn - Create VM

Status: Active

Overview​

This task deploys all five management VMs needed for the Azure Local environment. Each VM is deployed from Azure Marketplace images into the management subnet. OS-level configuration (AD DS, utilities, etc.) is handled in Tasks 12–16.

Task Classification

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

Admin Credentials

VM admin passwords are stored in Key Vault. Never hardcode passwords. Retrieve the admin password from keyvault://kv-{name}/azlocal-admin-password at deploy time.

Terraform Reference

Module: azurelocal-toolkit Files: nic.tf, VM resources Mode: Management

VMs to Deploy​

VM KeyNameRoleOSSizeIPConfig Path
dc01vm-azrldc-{env}-{region}-01Primary Domain ControllerWindows Server 2025Standard_D2s_v4Per configlanding_zone.virtual_machines[]
dc02vm-azrldc-{env}-{region}-02Secondary Domain ControllerWindows Server 2025Standard_D2s_v4Per configlanding_zone.virtual_machines[]
utilityvm-util-{env}-{region}-01Utility/Management ServerWindows Server 2025Standard_D2as_v6Per configlanding_zone.virtual_machines[]
ndmvm-ndm-{env}-{region}-01NDM (SYSLOG/SNMP)Ubuntu 24.04 LTSStandard_D2s_v4Per configlanding_zone.virtual_machines[]
lighthousevm-lh-{env}-{region}-01Lighthouse Central MgmtOpenGear LighthouseStandard_D2s_v4Per configlanding_zone.virtual_machines[]

Prerequisites​

  • Task 01: Virtual Network completed — Management subnet exists
  • Task 10: Key Vault completed — Admin password stored in Key Vault
  • VM sizes available in target region (check quotas)
  • Marketplace terms accepted for OpenGear Lighthouse image (if deploying)

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.virtual_machines[]: name, hostname, role, deploy_target, subscription, resource_group, network, subnet, private_ip, size, os,
admin_username, admin_password
landing_zone.networks[].name, .subscription, .resource_group, .location where the network is
landing_zone.subscriptions[].name, .id the subscription that holds the network

Keys added in registry 5.0.62 (schema 5.6.28, all optional) for the Terraform compute module and the Ansible domain-controller role, so that neither keeps a value of its own:

KeyWhat it isDefault
landing_zone.virtual_machines[].os_disk_size_gbSize of the OS disk in GB (VMs in Azure)128
landing_zone.virtual_machines[].os_disk_typeStorage type of the OS disk: Standard_LRS, StandardSSD_LRS, StandardSSD_ZRS, Premium_LRS, Premium_ZRSPremium_LRS
landing_zone.virtual_machines[].os_disk_cachingCaching of the OS disk: None, ReadOnly, ReadWriteReadWrite
landing_zone.virtual_machines[].image_versionVersion of the Marketplace image of os: latest, or a version such as 26100.1234.250101latest
landing_zone.virtual_machines[].dc_promotionFor a machine with role domain_controller: new_forest (the first domain controller: it creates the forest of identity.active_directory.domain_fqdn) or replica
landing_zone.virtual_machines[].dsrm_passwordFor a machine with role domain_controller: a Key Vault reference (keyvault://<vault>/<secret>) to the Directory Services Restore Mode password; the role reads it on the controller and never generates one
identity.active_directory.forest_functional_level, .domain_functional_levelFunctional levels of a new forest and its domain that the Ansible domain-controller role creates: WinThreshold or Win2025WinThreshold
identity.active_directory.dns_forwardersDNS forwarders of the domain controllers the role promotes; when empty, Azure DNS for a VM in Azure only

Single Subscription Model​

Landing Zone Placement​

FieldValueConfig Path
SubscriptionCustomer subscriptionlanding_zone.subscriptions[].id
Resource Grouprg-azrlmgmt-{env}-{region}-01landing_zone.virtual_machines[]
SubnetManagement subnetlanding_zone.virtual_machines[]

Execution Options​

Azure Portal​

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

Procedure (repeat for each VM)​

  1. Create Virtual Machine:
  • Search for Virtual machines → + Create → Azure virtual machine
  1. Basics: | Field | Value | Source | |-------|-------|--------| | Name | Per VM table above | landing_zone.virtual_machines[] | | Region | Your region | landing_zone.virtual_machines[] | | Image | Per VM table | landing_zone.virtual_machines[] | | Size | Per VM table | landing_zone.virtual_machines[] | | Username | azureadmin | Standard | | Password | From Key Vault | keyvault://<vault>/azlocal-admin-password |

  2. Disks: | Field | Value | Source | |-------|-------|--------| | OS disk type | Premium SSD | landing_zone.virtual_machines[].os_disk_type (Terraform route; default Premium_LRS) | | OS disk size | Per config | landing_zone.virtual_machines[].os_disk_size_gb (Terraform route; default 128) |

  3. Networking: | Field | Value | Source | |-------|-------|--------| | Virtual network | Management VNet | landing_zone.networks[].name | | Subnet | Management subnet | landing_zone.virtual_machines[] | | Public IP | None | No public IPs on mgmt VMs | | NIC name | Per config | landing_zone.virtual_machines[] |

  4. Advanced → IP Configuration: Set static private IP: | Field | Value | Source | |-------|-------|--------| | Private IP | Static | landing_zone.virtual_machines[] |

  5. Review + create: Verify → Click Create

  6. Repeat for all 5 VMs

Validation​

  • All 5 VMs provisioning state: Succeeded
  • Each VM has correct static private IP
  • No public IPs assigned
  • All VMs accessible via Bastion (Task 05)

Validation​

  • All 5 VMs running
  • Correct static IPs assigned
  • No public IPs
  • Bastion connectivity works to each VM

CAF/WAF Landing Zone Model​

In the CAF/WAF model, management VMs are deployed in the Management subscription in a spoke VNet peered to the Hub.

Landing Zone Placement​

FieldValueConfig Path
SubscriptionManagement subscriptionlanding_zone.subscriptions[].id
Resource Grouprg-azrlmgmt-{env}-{region}-01landing_zone.virtual_machines[]
VNet/SubnetManagement spokeMay differ from single-sub

Execution Options​

Azure Portal​

Follow the same procedure, targeting the Management subscription and spoke VNet.

Validation​

  • VMs in Management subscription
  • Reachable via Bastion from Connectivity Hub

Troubleshooting​

IssueRoot CauseRemediation
VM size not availableQuota or region limitationRequest quota increase or change region
Marketplace terms not acceptedOpenGear Lighthouse requires acceptanceSet-AzMarketplaceTerms -Publisher opengear -Product lighthouse -Name lighthouse -Accept
Static IP conflictIP already in useVerify IP availability in subnet
Password too weakAzure policy enforcedUse 12+ chars with upper, lower, number, special
NIC creation failsSubnet NSG blockingCheck NSG rules on management subnet


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
Task 10: Key VaultManual Deployment IndexVM Configuration

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-machines, management, deployment
  • Keywords: VM deployment, domain controller, utility server, NDM, Lighthouse, Azure VM
  • Author: Hybrid Cloud Solutions

Version Control​

VersionDateAuthorChanges
1.0.02025-03-25Azure Local CloudInitial release