This exercise walks you through building a simple hub‑and‑spoke network architecture in Azure. You’ll create two virtual networks, configure subnets, and establish secure VNet peering between them.
Scenario
Your organization is migrating a web-based application to Azure. To prepare the environment, you must:
Create two VNets: app‑vnet (spoke) and hub‑vnet (hub)
Add subnets for frontend, backend, and firewall
Peer the VNets so they can communicate privately
Step-by-Step Instructions
- Sign in to Azure
ii. In the search bar, type Virtual Networks and open the service.

**
Create the app‑vnet Virtual Network**
Configure the VNet using the following values:
Property: Value
Resource group: RG1
Virtual network name: app-vnet
Region: East US
IPv4 address space: 10.1.0.0/16
- Add the **frontend **subnet:
- Add the **backend **subnet:
3. Create the hub‑vnet Virtual Network
Repeat the creation process with these values:
Property Value
Resource group: RG1
Name: hub-vnet
Region: East US
IPv4 address space: 10.0.0.0/16
Subnet name: AzureFirewallSubnet
Subnet range: 10.0.0.0/26
Once deployed, verify both VNets and their subnets appear in the Virtual Networks list.

4. Configure VNet Peering
Now connect the two VNets so they can communicate privately.
In the left menu, select Peerings.

Configure the peering:
Property Value
Remote peering link name: app-vnet-to-hub
Virtual network: hub-vnet
Local peering link name: hub-to-app-vnet
Leave all other settings as default.
Select Add.
After deployment, confirm the Peering status shows Connected.



















Top comments (0)