Azure Peering connection

Question

In Azure, when you create a peering from one VNet (e.g., vnet1) to another (e.g., vnet2), a corresponding peering link is automatically created in the reverse direction as well. This means once you've set up peering from vnet1 to vnet2, Azure automatically establishes the reverse connection (vnet2 to vnet1).

This question is related to the following Learning Module

Answer

Hi

Thank you for reaching out to us on the Microsoft Q&A forum.

In Azure, VNet peering lets two virtual networks (VNets) communicate, but the connection doesn't automatically work both ways.

Here’s a simple breakdown of how it works:

1.Creating the First Peering (vnet1 to vnet2):

When you set up peering from vnet1 to vnet2, traffic can only go from vnet1 to vnet2.

Manual Reverse Peering:
- Azure won’t automatically set up the reverse connection from vnet2 to vnet1.
- For traffic to flow from vnet2 back to vnet1, you need to create another peering from vnet2 to vnet1.

Why Two Peerings Are Needed?

Each VNet controls its own traffic and security. So, to allow communication in both directions, you need to set up peerings in both directions.

In short:

To enable full communication between two VNets, you need to create two peering connections one in each direction.

Should you find this information helpful, kindly express your acknowledgment by clicking the "Upvote" and "Accept Answer" buttons on the post.

Thank you.

Share via

Azure Peering connection

1 answer

Your answer