Azure Network Architecture - Terraform Examples

1. Hub and Spoke

Terraform codes in this collection cover different hub and spoke network patterns using standard Virtual Network (Vnet) network topologies.

1.1. Secured Hub and Spoke - Single Region

⚙️ Deploy Terraform Code

This lab deploys a single-region Hub and Spoke Secured Virtual Network (Vnet) topology using Azure Firewall for traffic inspection. The lab demonstrates traffic routing patterns, hybrid DNS resolution, firewall security policies, and PrivateLink Services access to IaaS, PrivateLink access to PaaS services.

1.2. Secured Hub and Spoke - Dual Region

⚙️ Deploy Terraform Code

This lab deploys a dual-region Secured Hub and Spoke Vnet topology using Azure Firewalls for traffic inspection. The lab demonstrates multi-region traffic routing patterns, hybrid DNS resolution, firewall security policies, and PrivateLink Services access to IaaS, PrivateLink access to PaaS services.

1.3. Hub and Spoke - Single Region (NVA)

⚙️ Deploy Terraform Code

This lab deploys a single-region Hub and Spoke Vnet topology using Virtual Network Appliances (NVA) for traffic inspection. The lab demonstrates traffic routing patterns, hybrid DNS resolution, NVA deployment, and PrivateLink Services access to IaaS, PrivateLink access to PaaS services.

1.4. Hub and Spoke - Dual Region (NVA)

⚙️ Deploy Terraform Code

This lab deploys a dual-region Hub and Spoke Vnet topology using Virtual Network Appliances (NVA) for traffic inspection. The lab demonstrates multi-region traffic routing patterns, hybrid DNS resolution, NVA deployment, and PrivateLink Services access to IaaS, PrivateLink access to PaaS services.

2. Virtual WAN

Terraform codes in this collection cover different hub and spoke network patterns using Virtual WAN.

2.1. Virtual WAN - Single Region

⚙️ Deploy Terraform Code

This lab deploys a single-region Virtual WAN (Vwan) topology. The lab demonstrates traffic routing patterns, hybrid DNS resolution, connecting NVA into the virtual hub, and PrivateLink Services access to IaaS, PrivateLink access to PaaS services.

2.2. Virtual WAN - Dual Region

⚙️ Deploy Terraform Code

This lab deploys a dual-region Virtual WAN (Vwan) topology. The lab demonstrates multi-region traffic routing patterns, hybrid DNS resolution, connecting NVA into the virtual hubs, and PrivateLink Services access to IaaS, PrivateLink access to PaaS services.

2.3. Secured Virtual WAN - Single Region

⚙️ Deploy Terraform Code

This lab deploys a single-region Secured Virtual WAN (Vwan) topology. Routing Intent feature is enabled to allow traffic inspection through the Azure firewall in the virtual hub. The lab demonstrates traffic routing patterns, routing intent security policies, hybrid DNS resolution, NVA integration into the virtual hub, and PrivateLink Services access to IaaS, PrivateLink access to PaaS services.

2.4. Secured Virtual WAN - Dual Region

⚙️ Deploy Terraform Code

This lab deploys a dual-region Secured Virtual WAN (Vwan) topology. Routing Intent feature is enabled to allow traffic inspection through the Azure firewalls in the virtual hubs. The lab demonstrates multi-region traffic routing patterns, routing intent security policies, hybrid DNS resolution, connecting NVA into the virtual hubs, and PrivateLink Services access to IaaS, PrivateLink access to PaaS services.

3. Virtual Network Manager

3.1. Secured Hub and Spoke - Single Region (Virtual Network Manager)

⚙️ Deploy Terraform Code

Deploy a single-region Hub and Spoke Secured Virtual Network (Vnet) topology using the Azure Virtual Network Manager (AVNM) service. Learn about traffic routing patterns, hybrid DNS resolution, firewall security policies, and PrivateLink Services access to IaaS, PrivateLink access to PaaS services.

3.2. Secured Hub and Spoke - Dual Region (Virtual Network Manager)

⚙️ Deploy Terraform Code

Deploy a dual-region Hub and Spoke Secured Virtual Network (Vnet) topology using the Azure Virtual Network Manager (AVNM) service. Learn about traffic routing patterns, hybrid DNS resolution, firewall security policies, and PrivateLink Services access to IaaS, PrivateLink access to PaaS services.

4. General

(In progress)