A Virtual WAN Hub with Connections and Encrypted Branches

A hub is billed from the moment it exists and routes nothing until something connects; disable_vpn_encryption sends branch traffic in clear; and a VNet connection without internet security sends 0.0.0.0/0 out its own default route, bypassing the hub firewall. Connections come with it, branch encryption stays on, every connection routes the internet through the hub, and the prefix must be a /23.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

terraformAzureNetworking & VPCv1.0.0static-validated

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A Site-to-Site VPN with Modern Crypto, BGP, and a Connection An ExpressRoute Circuit with Peering and No Illusion of Encryption Azure Private Endpoint (Private Link)Azure Virtual Network (hub-ready)Egress with Enough SNAT Ports to Survive the Afternoon

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "azure_virtual_wan" {
  source  = "www.iac-bazaar.com/iac-bazaar/azure-virtual-wan/azure"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.