How to Configure Azure VNet Peering Across Regions

In this lab, we will configure Azure VNet peering between the East US and West Europe regions and test connectivity between virtual machines in the two VNets.

This puts Azure VNet peering near the beginning and makes the sentence grammatically complete.

Azure VNet peering allows two virtual networks to communicate with each other over Microsoft’s backbone infrastructure. VNet peering can be used to connect VNets in the same Azure region or across different Azure regions.

In this lab, we connect VNets located in East US and West Europe. We create the required VNets and virtual machines, configure VNet peering, optionally configure Private DNS, and test connectivity between the VMs.

Lab Topology

Azure VNet Connected Devices

Before configuring VNet peering, review the properties of each Azure VNet. Check the VNet address space and subnet configuration to ensure that the networks are configured correctly. The East US and West Europe VNets should use non-overlapping address spaces.

Azure VNet Properties

View VNet Topology Using Network Watcher

Note:Network Watcher was not available in the East US region when this lab was originally tested.

Configure VNet Peering Between Coreservices and Manufacturing

Next, configure VNet peering between the Coreservices VNet and the Manufacturing VNet. Create a peering connection from each VNet and enable the appropriate options for virtual network access.

Configure Private DNS Zone (Optional)

Test Connectivity Between Azure VMs

Azure VNet peering enables you to connect Azure virtual networks using Microsoft’s private backbone network. Once two VNets are peered, resources in each network can communicate with one another using private IP addresses. Traffic between peered VNets does not travel over the public internet.

VNet peering is a useful option when you need to connect Azure VNets across different regions. In this lab, we configured peering between the East US and West Europe VNets and tested connectivity between virtual machines in both networks.

Conclusion

In this lab, we successfully configured Azure VNet peering between virtual networks in the East US and West Europe regions. We created the required VNets, subnets, and virtual machines, configured VNet peering, and tested connectivity between the connected networks.

Azure VNet peering provides private network connectivity between Azure virtual networks through Microsoft’s backbone infrastructure. It is a useful solution for connecting workloads across Azure regions without routing traffic through the public internet.

This lab provides a practical understanding of Azure VNet peering, cross-region connectivity, and communication between virtual machines using private IP addresses.