New here?
Learn what this repo solves and how the hub-spoke pattern is wired together. Read the architecture →
New here?
Learn what this repo solves and how the hub-spoke pattern is wired together. Read the architecture →
Ready to deploy
Answer a few questions and walk away with a ready-to-use parameter file
(Terraform .tfvars or Bicep .bicepparam) and the exact CLI commands to
run. Open the wizard →
Already deployed
Day-2 ops: monitoring, backup verification, cost tracking, teardown. Day-2 operations →
Hub-spoke VNets, NAT gateway, Private DNS, Key Vault with PE, Log Analytics, Recovery Services.
Adds Azure Firewall (Basic) for managed egress filtering. Replaces NAT, forces 0.0.0.0/0 through the firewall.
Adds a zone-redundant VPN Gateway for hybrid connectivity to the customer’s on-premises network.
Firewall + VPN combined. Highest-control deployment for regulated workloads.
Every resource is provisioned through Azure Verified Modules — AVM-TF on the Terraform side and AVM-Bicep on the Bicep side. Modules are pinned to specific versions and updated by Dependabot. Terraform state lives in an Azure Storage backend with Entra ID auth (no SAS keys, no shared secrets); Bicep deployments are tracked natively in Azure Resource Manager — pick the workflow your team prefers.