πŸ”— Azure VNet Peering: Dashboard Steps

πŸ“Œ Overview

VNet Peering connects two separate Virtual Networks (VNets) so they can talk to each other using private IP addresses. It’s like building a direct bridge between two isolated islands.

Hinglish Analogy: "Do alag colonies (VNets) ke beech mein ek private bridge banana, taaki log (data) bina main road (Internet) par gaye ek dusre se mil sakein."


βœ… Prerequisites

Before you start, ensure you have:

  1. Two VNets (e.g., VNet-A and VNet-B).
  2. No Overlapping Address Spaces (e.g., 10.0.0.0/16 and 10.1.0.0/16 is OK. 10.0.0.0/16 and 10.0.0.0/16 will FAIL).

πŸ› οΈ Step-by-Step: Creating a Peering

In the modern Azure Portal, you can create the link for BOTH sides in one go.

1. Go to the First VNet

2. Open Peering Menu

3. Configure "This Virtual Network" (VNet-A Side)

4. Configure "Remote Virtual Network" (VNet-B Side)

5. Finalize


🚦 Verifying the Connection

  1. Wait for a few seconds.
  2. Refresh the Peerings list.
  3. Peering Status: Should show Connected.
    • If it says Initiated, it means only one side is linked. Wait or check the other VNet.

βš™οΈ Key Settings Explained

SettingMeaningUse Case
Allow Traffic to RemoteCan I talk to them?Always Yes for normal communication.
Allow Traffic ForwardedCan I accept traffic not originating from them?Use Yes if the other side is a specific Router/Gateway/NVA.
Use Remote GatewayCan I use their VPN Gateway?Use Yes in Hub-Spoke topology (Spoke uses Hub's VPN).

⚑ Exam Tips

  1. Cost: Peering is NOT free. You pay for data ingress and egress across the peering.
  2. Transitive: Peering is non-transitive.
    • If A matches B, and B matches C... A cannot talk to C. (You need to peer A directly to C).
  3. Cross-Region: You can peer VNets in different regions (Global VNet Peering).