Configuring an Azure VNet-to-VNet VPN Gateway
Pluralsight Hands-On Lab — Networking
At a Glance
| Platform | Pluralsight |
|---|
| Category | Azure Networking |
|---|
| Lab Type | Guided + Challenge Mode |
|---|
| Environment | Azure Portal, Windows VMs via Remote Desktop |
|---|
| Completed | 2026 |
|---|
Overview
Virtual network gateways enable secure connectivity between Azure virtual networks and on-premises infrastructure. In this lab, I connected two Azure virtual networks — one representing a Dallas-Fort Worth location and one representing New York City — using a VNet-to-VNet VPN gateway connection. I verified the lack of connectivity before configuration, established bidirectional gateway connections with a shared key, and confirmed successful VM-to-VM connectivity across both VNets after the gateways were linked. The concepts apply directly to hybrid cloud scenarios connecting on-premises networks to Azure.
What I Did
- Connected to both VMs (vm-dfw and vm-nyc) via Remote Desktop using their public IP addresses
- Verified the absence of connectivity between the two VMs using Remote Desktop Connection to the private IP before gateway configuration
- Reviewed the process for creating a Virtual Network Gateway from the Azure Marketplace, including GatewaySubnet configuration, SKU selection, and public IP assignment
- Configured a VNet-to-VNet connection on the VNG-DFW gateway with bidirectional connectivity enabled, creating both dfw-to-nyc and nyc-to-dfw connections in a single step
- Set a shared key (PSK) and selected VNG-NYC as the second virtual network gateway
- Waited for both connections to reach Connected status and confirmed successful RDP connectivity from the DFW VM to the NYC VM's private IP (10.1.0.4) and vice versa (10.0.0.4)
← Back to Pluralsight Labs