Configure Azure Virtual Network Peering (Step-by-Step Guide)

📘 Overview

In this hands-on lab, we explore how to configure Azure Virtual Network (VNet) Peering, a key feature that allows seamless communication between Azure virtual networks.

We’ll walk through:

• Understanding the scenario

• Configuring VNet peering

• Creating virtual machines using Azure PowerShell (Aditional step)

• Testing the peering connection

🧠 Scenario

You are working as an Administrator, and if you have task to connect two Azure virtual networks. The goal is to enable secure and efficient communication between these networks.

🔗 What is VNet Peering?

Azure Virtual Network Peering allows:

• Private connectivity between VNets

• Low-latency, high-bandwidth communication

• Seamless routing without gateways

⚙️ Step 1: Review the Environment

Before configuring peering, ensure:

• Two virtual networks exist (e.g., VNET1 and VNET2)

• Each VNet has at least one subnet (e.g., FrontEnd)

• Both are deployed in valid Azure regions (e.g., East US, East US 2)

🔄 Step 2: Configure Azure Virtual Network Peering

🔹 Steps via Azure Portal:

1. Go to Virtual Networks

2. Select VNET1

3. Click on Peerings

4. Click + Add

5. Configure:

   • Peering link name

   • Remote virtual network (VNET2)

   • Allow virtual network access ✅

   Note - Repeat the same steps for VNET2 to VNET1

   
   

   

💻 Step 3: Create Virtual Machines Using Azure PowerShell - If you don't have already

Now, deploy two virtual machines in each VNet to test connectivity.

🖥️ Create VM1 in VNET1

PowerShell

Follow the MS doc - https://learn.microsoft.com/en-us/azure/virtual-machines/windows/quick-create-powershell

🖥️ Create VM2 in VNET2

PowerShell

Follow the MS doc - https://learn.microsoft.com/en-us/azure/virtual-machines/windows/quick-create-powershell

🧪 Step 4: Test Virtual Network Peering

Once both VMs are deployed:

✅ Validation Steps:

1. Connect to VM1 via RDP

2. Use ping or Test-NetConnection to verify connectivity to VM2's private IP

3. Confirm successful communication

If peering is configured correctly, both VMs should communicate using private IP addresses.

✅ Key Takeaways

• VNet Peering enables private, fast communication across networks

• No gateways are required

• Works across regions (Global VNet Peering)

• Ideal for multi-tier applications and hybrid architectures

🚀 Conclusion

In this lab, we successfully:

• Configured Azure VNet Peering

• Deployed virtual machines using PowerShell

• Verified connectivity between peered networks