VNet-to-VNet connectivity in Azure - Mini Project: Build & Apply

VNet-to-VNet connectivity

📖 Scenario: You are setting up a simple network connection between two virtual networks (VNets) in Azure. This connection allows resources in one VNet to communicate with resources in the other VNet securely and privately.

🎯 Goal: Create two Azure VNets and establish a VNet-to-VNet connection between them using virtual network peering.

📋 What You'll Learn

Create two VNets named VNet1 and VNet2 with specified address spaces

Create virtual network peerings between VNet1 and VNet2

Ensure peering allows traffic to flow both ways

💡 Why This Matters

🌍 Real World

Connecting VNets allows different parts of an application or different teams to communicate securely within Azure without exposing traffic to the internet.

💼 Career

Network engineers and cloud architects often set up VNet peerings to build scalable and secure cloud network architectures.

1

Create two VNets with address spaces

Create two virtual networks named VNet1 and VNet2 with address spaces 10.0.0.0/16 and 10.1.0.0/16 respectively using Azure CLI commands.

Azure

# Create VNet1 and VNet2 with specified address spaces
# Your code here

Need a hint?

Use az network vnet create command with --name and --address-prefix options.

2

Create peering from VNet1 to VNet2

Create a virtual network peering named VNet1ToVNet2 from VNet1 to VNet2 allowing virtual network access using Azure CLI.

Azure

az network vnet create --resource-group MyResourceGroup --name VNet1 --address-prefix 10.0.0.0/16
az network vnet create --resource-group MyResourceGroup --name VNet2 --address-prefix 10.1.0.0/16
# Create peering from VNet1 to VNet2
# Your code here

Need a hint?

Use az network vnet peering create with --vnet-name VNet1 and --remote-vnet VNet2.

3

Create peering from VNet2 to VNet1

Create a virtual network peering named VNet2ToVNet1 from VNet2 to VNet1 allowing virtual network access using Azure CLI.

Azure

az network vnet create --resource-group MyResourceGroup --name VNet1 --address-prefix 10.0.0.0/16
az network vnet create --resource-group MyResourceGroup --name VNet2 --address-prefix 10.1.0.0/16
az network vnet peering create --resource-group MyResourceGroup --name VNet1ToVNet2 --vnet-name VNet1 --remote-vnet VNet2 --allow-vnet-access
# Create peering from VNet2 to VNet1
# Your code here

Need a hint?

Repeat the peering creation but swap --vnet-name and --remote-vnet values.

4

Verify peering connection status

Use Azure CLI to check the peering status of VNet1ToVNet2 and VNet2ToVNet1 to ensure the connection is Connected.

Azure

az network vnet create --resource-group MyResourceGroup --name VNet1 --address-prefix 10.0.0.0/16
az network vnet create --resource-group MyResourceGroup --name VNet2 --address-prefix 10.1.0.0/16
az network vnet peering create --resource-group MyResourceGroup --name VNet1ToVNet2 --vnet-name VNet1 --remote-vnet VNet2 --allow-vnet-access
az network vnet peering create --resource-group MyResourceGroup --name VNet2ToVNet1 --vnet-name VNet2 --remote-vnet VNet1 --allow-vnet-access
# Check peering status
# Your code here

Need a hint?

Use az network vnet peering show with the correct --vnet-name and --name parameters.