4 - Multi-Region Virtual WAN with Network Virtual Appliance (NVA)

A full Platform landing zone deployment with Virtual WAN network connectivity in multiple regions, ready for a third party Network Virtual Appliance (NVA).

• Example Platform landing zone configuration file: full-multi-region-nva/virtual-wan.tfvars

• Estimated Costs - Approximate monthly infrastructure costs
• Resources - What gets deployed in this scenario
• Configuration - How DNS, routing, and policies are configured

Note

This estimate does not include the cost of the Network Virtual Appliance (NVA) itself, which varies by vendor and configuration.

Note

Estimated fixed infrastructure costs based on Azure Retail Prices for the westus region in USD as of 2026-04-02. Consumption-based costs (data processing, log ingestion, DNS queries, etc.) are not included and will vary based on usage. DDoS Protection Plan pricing is sourced from the Azure DDoS Protection pricing page. You can generate your own estimates for any region and currency using the Get-ScenarioCostEstimates.ps1 script.

The following resources are deployed by default in this scenario:

• Management Groups
• Policy Definitions
• Policy Set Definitions
• Policy Assignments
• Policy Assignment Role Assignments

• Log Analytics Workspace
• Log Analytics Data Collection Rules for AMA
• User Assigned Managed Identity for AMA
• Automation Account

Tip

Identity and Security subscriptions are recommended but optional. If you do not yet have dedicated subscriptions for identity and security workloads, you can comment out or remove the identity and security subscription placement blocks in the configuration file and add them later.

• Connectivity subscription - placed under the connectivity management group
• Management subscription - placed under the management management group
• Identity subscription - placed under the identity management group (recommended)
• Security subscription - placed under the security management group (recommended)

• DDOS Protection Plan

• Virtual WAN homed in the primary region
• Virtual Hubs in each region

• Sidecar Virtual Networks
• Sidecar to Virtual Hub peering
• Subnets for Bastion, and Private DNS Resolver in each region

• Azure Bastion per region
• Azure Bastion public IP per region

• Azure Private DNS Resolver per region
• Azure non-regional Private Link Private DNS zones in primary region
• Azure regional Private Link Private DNS zones per region
• Azure Virtual Machine auto-registration Private DNS zone per region
• Azure Private Link DNS zone virtual network links per region

• Azure ExpressRoute Virtual Network Gateway per region
• Azure VPN Virtual Network Gateway per region

The following relevant configuration is applied:

Private DNS is configured ready for using Private Link and Virtual Machine Auto-registration. Spoke Virtual Networks should use the Network Virtual Appliance IP Address in the same region as their DNS configuration.

• Network Virtual Appliance should be configured as DNS proxy
• Network Virtual Appliance should forward DNS traffic to the Private DNS resolver
• Azure Private DNS Resolver has an inbound endpoint from the sidecar network
• Azure Private Link DNS zones are linked to the all hub sidecar Virtual Networks