VNet peering for connectivity in Azure - Mini Project: Build & Apply

VNet Peering for Connectivity

📖 Scenario: You are setting up two virtual networks (VNets) in Azure for a company. These VNets need to communicate with each other securely and efficiently without going through the internet.To achieve this, you will create two VNets and then connect them using VNet peering.

🎯 Goal: Build two Azure VNets named VNetA and VNetB with specified address spaces, and configure VNet peering between them to enable direct connectivity.

📋 What You'll Learn

Create an Azure virtual network called VNetA with address space 10.0.0.0/16 in resource group ResourceGroup1.

Create an Azure virtual network called VNetB with address space 10.1.0.0/16 in resource group ResourceGroup1.

Create VNet peering from VNetA to VNetB with allowVirtualNetworkAccess enabled.

Create VNet peering from VNetB to VNetA with allowVirtualNetworkAccess enabled.

💡 Why This Matters

🌍 Real World

Companies often need to connect different parts of their cloud network securely. VNet peering allows this without exposing traffic to the internet.

💼 Career

Cloud engineers and network administrators use VNet peering to design scalable and secure network architectures in Azure.

1

Create the first virtual network VNetA

Create an Azure virtual network called VNetA with address space 10.0.0.0/16 in resource group ResourceGroup1. Use the Azure CLI command az network vnet create with the exact parameters.

Azure

# Your code here

Need a hint?

Use az network vnet create with --resource-group, --name, and --address-prefix options.

2

Create the second virtual network VNetB

Create an Azure virtual network called VNetB with address space 10.1.0.0/16 in resource group ResourceGroup1. Use the Azure CLI command az network vnet create with the exact parameters.

Azure

az network vnet create --resource-group ResourceGroup1 --name VNetA --address-prefix 10.0.0.0/16 --location eastus
# Your code here

Need a hint?

Repeat the az network vnet create command with the new name and address prefix.

3

Create VNet peering from VNetA to VNetB

Create a VNet peering connection from VNetA to VNetB in resource group ResourceGroup1. Use the Azure CLI command az network vnet peering create with --allow-vnet-access enabled.

Azure

az network vnet create --resource-group ResourceGroup1 --name VNetA --address-prefix 10.0.0.0/16 --location eastus
az network vnet create --resource-group ResourceGroup1 --name VNetB --address-prefix 10.1.0.0/16 --location eastus
# Your code here

Need a hint?

Use az network vnet peering create with --vnet-name as VNetA and --remote-vnet as VNetB.

4

Create VNet peering from VNetB to VNetA

Create a VNet peering connection from VNetB to VNetA in resource group ResourceGroup1. Use the Azure CLI command az network vnet peering create with --allow-vnet-access enabled.

Azure

az network vnet create --resource-group ResourceGroup1 --name VNetA --address-prefix 10.0.0.0/16 --location eastus
az network vnet create --resource-group ResourceGroup1 --name VNetB --address-prefix 10.1.0.0/16 --location eastus
az network vnet peering create --resource-group ResourceGroup1 --name VNetA-to-VNetB --vnet-name VNetA --remote-vnet VNetB --allow-vnet-access
# Your code here

Need a hint?

Repeat the peering creation with --vnet-name as VNetB and --remote-vnet as VNetA.