Configure Global VNet Peering
This “Configure Global VNet Peering” IT Pro Challenge virtual lab will teach you how to enable Global VNet peering in Microsoft Azure. Enabling peering between two virtual networks has many benefits over other connection methods, such as VPN. After completing this challenge, you will have the skills necessary to create and test VNet peerings.
Already have an account? Sign In »

Azure is a public cloud computing platform. Azure can be used for many purposes, such as analytics, virtual computing, and networking. In particular, Azure provides a powerful tool for creating virtual networks and virtual machines. As a network or system administrator, you can control how connections are shared between virtual machines networks. Given its powerful toolset and rising popularity, it is prudent for modern IT workers to be comfortable working with Azure.
This hands-on lab will teach you what Global VNet peering is in Microsoft Azure and how to enable VNet peering in Azure. You will also learn how to test VNet peering. VNet peering allows two virtual networks to connect with each other without using VPN Gateways. VNet peering comes with several benefits, such as:
- Private peering traffic stays on the Azure network.
- Increased network speed.
- Access to the public internet is not required to connect to virtual machines.
As a system or network administrator working in the Azure environment, your responsibilities will include ensuring network access across virtual machines. Global VNet peering is a powerful tool for completing this task, and the ability to enable Global VNet peering is key to a successful career in IT. This virtual lab will give you real-world experience with Global VNet peering in Azure.
Understand the scenario: You’re an Azure administrator assigned to add peerings between the virtual networks for two applications hosted in different Azure regions.
Understand the environment: You are using an Azure resource group that contains an existing storage account for use with Cloud Shell, two virtual networks, and two virtual machines.
Attempt to Create a Peering:
The first step in this lab will introduce you to the process of adding VNet peering. You will try to enable VNet peering between two virtual networks with overlapping address spaces. You will:
- Sign in to the Azure portal using given credentials.
- View the available resources.
- Attempt to add a peering between two virtual networks.
- Note the error received when trying to add the peering.
Configure a New Address Space and Subnet:
To enable VNet peering between the two virtual networks, you must first resolve the overlapping address spaces. You will:
- Add an address space to a virtual network.
- Add a subnet to a virtual network.
- Update the address space and subnet setting in a virtual network.
Create Virtual Network Peerings:
After resolving the network error, you will create a network peering between the two virtual networks.
Use SSH in CloudShell to Test Peering:
For the final step on this virtual lab, you will test the Vnet peering connection. You will:
- Access the Azure bash shell.
- Connect to a virtual machine using its public IP address.
- Use the ping command to verify the connection.
Summary:
Global VNet peering in Microsoft Azure gives system and network administrators a convenient tool for connecting two virtual networks across regions without the need for VPN. Global VNet peering has many benefits over other methods of connecting virtual networks, such as increased network speeds. This guided lab will give you real-world experience understanding Global VNet peering and setting up network peerings between virtual networks.
In the “Configure Global VNet Peering” virtual lab, you will accomplish the following:
- Observe address overlap errors between two virtual networks.
- Modify virtual network address spaces and subnet.
- Create VNet peering between two virtual networks.
- Test the VNet peering connection.
Other challenges in this series:
- GUIDED CHALLENGE: Configure a Network Security Group in a Virtual Network
- GUIDED CHALLENGE: Configure Route Tables in a Virtual Network