Hi Amir,
That's interesting. What you’re seeing is likely a redundancy or inconsistency in the lab instructions.
Typically, only one VNet with a GatewaySubnet is needed to deploy a VPN Gateway.
The first command creates a subnet named GatewaySubne
(note the typo—it should be GatewaySubnet
) inside the existing VNet Azure-VNet-1
.
The second command creates a new VNet named VNG-Azure-VNet-1
with its own GatewaySubnet
.
Then the VPN Gateway is created on this second VNet.
In most real-world and tutorial scenarios, you just create one VNet with a properly named GatewaySubnet
, then create the VPN Gateway inside it.
The second VNet creation seems unnecessary unless the lab intends to demonstrate managing multiple VNets or a specific scenario involving multiple VNets.