• Table of contents
• Deploy to Azure
• Introduction
• Description
• LAB Builder scenario's
• Topology drawing
• Deployment Steps
• Deployment notes
• Resource Names
• Appendix
  • Parameters
  • Backlog... whishlist items

Description	Template
Deploy to Azure Subscription

⚠️ Warning: This deployment is meant for Demo, Test, Learning, Training, Practice or Reproduction purposes ONLY!! Please don't deploy to production environments!!

In my daily work I've created numerous times a (semi-)manual Hub & Spoke topology for Testing, (Self)Training, Demo or Reproduction purposes. I've always done this in multiple ways, like: PowerShell scripts, Azure CLI, ARM or Azure Potal GUI.....whatever was the best fit. But bottom line: Wathever option is fine by me as long as it has the least amount of effort to build it.

With that in mind I've created a "Hub & Spoke playground Lab builder" so you'll be able to deploy Hub & Spoke scenario's in notime. It takes approx. 30min to deploy a 'full option Hub & Spoke' deployment with 2 Spoke VNET's.

With this 'Hub & Spoke playground - LAB Builder' you'll be able to deploy Hub & Spoke topologies in various ways.

Optionaly you can deploy Azure Firewall (Standard or Premium) in Hub VNET incl. Route table, deploy Virtual Machine in Hub VNET and/or Spoke VNET's and deploy Bastion Host in Hub VNET and/or Spoke VNET's. Optional deploy default Azure Firewall rule Collection group which enables spoke-to-spoke and internet traffic.

On deployemnt you can specify the amount of Spoke VNET's to be deployed. VNET peerings will be deployed if both Hub and Spoke(s) are selected for deployement.

To simulate OnPrem hybrid connectivity you can optionaly deploy a 'OnPrem' VNET. Optionaly deploy a Bastion Host, Virtual Machine and Virtual Network Gateway in the OnPrem VNET. When a Hub is also deployed with a VPN Gateway you can optionaly deploy a site-to-site VPN connection.

With LABbuilder you can deploy 4 main scenario's.

1. Only deploy Spoke(s)
2. Only deploy Hub
3. Deploy Hub and Spoke(s)
4. Deploy Hub and Spoke(s) and OnPrem simulating Hybrid connectivity

Within these main scenario's there are multiple options:

Step	Screenshot
Select Subscription and Region Enter the a /16 subnet example: 172.16.0.0/16 Note: Hub VNET will always get the first available /24 subnet, first spoke the second subnet etc. like: 172.16.0.0/24 = Hub VNET 172.16.1.0/24 = Spoke1 172.16.2.0/24 = Spoke2 etc.
Deploy Hub Optional enable: - Azure Bastion - Azure Firewall Standard or Premium - Azure Firewall Policy rule Collection group
Deploy Spokes Enter resource group prefix name Enter amount of Spokes to deploy (Max 25) Optional enable: - Azure Bastion Note: VM and Azure Bastion will be deployed in every Spoke
Deploy a simulated OnPrem incl. Hybrid Connectivity. Enter resource group name Optional enable: - Azure Bastion - Virtual Network Gateway - Site-to-Site connection between OnPrem and Hub
Enable Virtual Machine deployment in Hub, Spoke or OnPrem. Select OS Type (Windows or Linux) Select VM SKU Size Enter Local Admin credentials If Virtual Machine is selected for Hub and/or Spoke
Setup Tags
Validate and Deploy

• VNET Peering will be deployed when Hub and Spoke are selected
• ICMPv4 Firewall rule will be enabled on Virtual Machines
• Windows VM image is Windows Server 2022 Datacenter Gen2
• Linux VM image is Ubuntu Server 22.04 LTS Gen2
• Route tables incl. Default route will be deployed if Azure Firewall is selected (0.0.0.0/0 -> Azure Firewall)
• Network Security group will be deplyed to 'default' subnets only
• At deployemt use a /16 subnet. every VNET (Hub and Spoke VNET's) will get a /24 subnet
• Hub VNET will always get the first available /24 subnet. eg. 172.16.0.0/24
• Spoke(s) VNET gets subsequent subnets. eg. 172.16.1.0/24, 172.16.2.0/24 etc.
• OnPrem VNET will always get the latest available /24 subnet. eg. 172.16.255.0/24
• see subnet details:

Spoke VNET's subnets:

Hub VNET subnets:

OnPrem VNET subnets:

• Choose between Azure vWAN and Hub & Spoke
• Add default Firewall Network & Application rules
• Deploy separate VNET (simulate OnPrem) and deploy VPN gateways including Site-to-Site tunnel
• remove static Resource Group names
• use CIDR notation as Address Space (Instead of first two octets)
• Virtual machine OS Type. Windows and Linux support
• Virtual Machine SKU size selection
• Virtual machine boot diagnostics (Managed storage account)
• Virtual machine delete option of Disk and Nic
• Tags support for resources deployed
• etc...