Hybrid and Multi-VNet Connectivity: VPN Gateway, ExpressRoute, Virtual WAN, Peering and Hub-and-Spoke Design
Connection Options
| Option | Path | Bandwidth | Use |
|---|---|---|---|
| Site-to-site VPN | Encrypted IPsec over the internet to a VPN Gateway | Up to a few Gbps by SKU | Quick, lower cost, backup path |
| Point-to-site VPN | Individual clients connect to the VNet | Per user | Remote workers, admins |
| ExpressRoute | Private connection through a provider, not over the internet | 50 Mbps to 100 Gbps | Predictable latency, large volumes, compliance |
| ExpressRoute Direct | Direct 10 or 100 Gbps ports at Microsoft peering locations | High | Very large or special needs |
| Virtual WAN | Managed hub networking for branches, VPN, ExpressRoute, SD-WAN and VNets | Scalable | Many sites at scale |
VPN Gateway
- A gateway in the GatewaySubnet of a VNet. Use zone-redundant SKUs (VpnGw1AZ and up) in production
- Active-active gateways give two tunnels for high availability
- Needs the on-premises device public IP and shared key. BGP gives dynamic routing
bash
az network public-ip create -g rg-hub -n pip-vpngw --sku Standard --zone 1 2 3
az network vnet-gateway create -g rg-hub -n vpngw-hub --vnet vnet-hub --public-ip-addresses pip-vpngw --gateway-type Vpn --vpn-type RouteBased --sku VpnGw2AZ --no-wait
az network local-gateway create -g rg-hub -n lgw-office --gateway-ip-address 203.0.113.10 --local-address-prefixes 192.168.0.0/16
az network vpn-connection create -g rg-hub -n cn-office --vnet-gateway1 vpngw-hub --local-gateway2 lgw-office --shared-key 'REPLACE-WITH-SECRET'
ExpressRoute
- A circuit is ordered from a connectivity provider at a peering location. Use two connections (primary and secondary) for redundancy
- Private peering reaches your VNets. Microsoft peering reaches Microsoft 365 and public Azure services
- Pair with a VPN as backup, or use two circuits in two locations for resilience
- ExpressRoute is private but not encrypted by default. Add MACsec (Direct) or IPsec over ExpressRoute if encryption is needed
- Global Reach links your sites through the Microsoft network
Peering and Hub-and-Spoke
text
On-premises ─ VPN / ExpressRoute ─┐
▼
Spoke VNet A (app 1) ─peering─► HUB VNet: Gateway, Azure Firewall, DNS, Bastion ◄─peering─ Spoke VNet B (app 2)
Spokes use UDRs: 0.0.0.0/0 and other spokes → Firewall in the hub
- Peering is not transitive. Spokes talk through the hub's firewall or router
- Enable gateway transit on the hub peering and use remote gateways on spokes so spokes share the hub's VPN or ExpressRoute
- Place shared services (firewall, DNS, Bastion) in the hub, workloads in spokes (usually in separate subscriptions)
- Global VNet peering connects VNets across regions
bash
az network vnet peering create -g rg-hub -n hub-to-spoke1 --vnet-name vnet-hub --remote-vnet /subscriptions/<sub>/resourceGroups/rg-spoke1/providers/Microsoft.Network/virtualNetworks/vnet-spoke1 \
--allow-vnet-access --allow-gateway-transit --allow-forwarded-traffic
az network vnet peering create -g rg-spoke1 -n spoke1-to-hub --vnet-name vnet-spoke1 --remote-vnet vnet-hub-id --allow-vnet-access --use-remote-gateways --allow-forwarded-traffic
Virtual WAN
- Microsoft-managed hub-and-spoke at scale: VPN, ExpressRoute, point-to-site, SD-WAN partners and VNet connections with automatic routing between them
- Hubs can be secured with Azure Firewall Manager and routing intent
- Choose it for many branches or global networks. Use a self-built hub when you need full custom control
Other Useful Services
| Service | Use |
|---|---|
| Azure Route Server | Exchange routes with network virtual appliances using BGP |
| Azure DNS Private Resolver | Hybrid DNS forwarding |
| Network Watcher | Connection troubleshoot, next hop, IP flow verify, packet capture |
| Azure Arc | Manage on-premises and other-cloud servers and Kubernetes from Azure |
Choosing
| Situation | Choose |
|---|---|
| Quick connection, low cost | Site-to-site VPN |
| Remote workers | Point-to-site VPN or Entra-based VPN |
| Steady large traffic, strict latency | ExpressRoute with VPN backup |
| Dozens of branches | Virtual WAN |
| Few VNets in one region | Peering with a hub |
Practice
- Draw hub-and-spoke for two apps and on-premises
- List the settings needed on both peering sides to share a VPN gateway
- Choose between VPN and ExpressRoute for 5 Gbps, predictable latency
- Use Network Watcher to test connectivity between two VMs
Conclusion
VPN Gateway links sites over the internet, ExpressRoute gives private connections and Virtual WAN scales many sites. Build hub-and-spoke with peering, gateway transit and a central firewall, and add redundancy for every link.
Quick Summary: options; VPN; ExpressRoute; hub-spoke; Virtual WAN; other services; choosing.

