Tutorial: Connect virtual networks with virtual network peering using the Azure portal
You can connect virtual networks to each other with virtual network peering. These virtual networks can be in the same region or different regions (also known as Global VNet peering). Once virtual networks are peered, resources in both virtual networks are able to communicate with each other, with the same latency and bandwidth as if the resources were in the same virtual network. In this tutorial, you learn how to:
- Create two virtual networks
- Connect two virtual networks with a virtual network peering
- Deploy a virtual machine (VM) into each virtual network
- Communicate between VMs
Before you begin, you require an Azure account with an active subscription. If you do not have one, you can create an account for free.
Log in to Azure
Log in to the Azure portal at https://portal.azure.com.
Create virtual networks
On the Azure portal, select Create a resource.
Select Networking, and then select Virtual network.
On the Basics tab, enter or select the following information and accept the defaults for the remaining settings:
Setting Value Subscription Select your subscription. Resource group Select Create new and enter myResourceGroup. Region Select East US. Name myVirtualNetwork1
On the IP Addresses tab, enter 10.0.0.0/16 for the Address Space field. Click the Add subnet button below and enter Subnet1 for Subnet Name and 10.0.0.0/24 for Subnet Address range.
Select Review + Create and then select Create.
Complete steps 1-5 again, with the following changes:
Setting Value Name myVirtualNetwork2 Address space 10.1.0.0/16 Resource group Select Use existing and then select myResourceGroup. Subnet name Subnet2 Subnet Address range 10.1.0.0/24
Peer virtual networks
In the Search box at the top of the Azure portal, begin typing MyVirtualNetwork1. When myVirtualNetwork1 appears in the search results, select it.
Select Peerings, under Settings, and then select Add, as shown in the following picture:
Enter, or select, the following information, accept the defaults for the remaining settings, and then select OK.
Setting Value Name of the peering from myVirtualNetwork1 to remote virtual network myVirtualNetwork1-myVirtualNetwork2 - When the page first loads, you'll see the phrase "remote virtual network" here. After you choose the remote virtual network, the phrase "remote virtual network" will be replaced with the name of the remote virtual network. Subscription Select your subscription. Virtual network myVirtualNetwork2 - To select the myVirtualNetwork2 virtual network, select Virtual network, then select myVirtualNetwork2 (myResourceGroup). You can select a virtual network in the same region or in a different region. Name of the peering from myVirtualNetwork2 to myVirtualNetwork1 myVirtualNetwork2-myVirtualNetwork1
The PEERING STATUS is Connected, as shown in the following picture:
If you don't see the status, refresh your browser.
Create virtual machines
Create a VM in each virtual network so that you can communicate between them in a later step.
Create the first VM
On the Azure portal, select Create a resource.
Select Compute, and then select Windows Server 2016 Datacenter. You can select a different operating system, but the remaining steps assume you selected Windows Server 2016 Datacenter.
Enter, or select, the following information for Basics, accept the defaults for the remaining settings, and then select Create:
Setting Value Resource group Select Use existing and then select myResourceGroup. Name myVm1 Location Select East US. User name Enter a user name of your choosing. Password Enter a password of your choosing. The password must be at least 12 characters long and meet the defined complexity requirements.
Select a VM size for the Size option.
Select the following values for under Networking:
Setting Value Virtual network myVirtualNetwork1 - If it's not already selected, select Virtual network and then select myVirtualNetwork1. Subnet Subnet1 - If it's not already selected, select Subnet and then select Subnet1.
Select Networking. Choose Allow selected ports for the Public inbound ports option. Choose RDP for the Select inbound ports option below this.
Select the Review + Create button in the lower, left-hand corner to start the VM deployment.
Create the second VM
Complete steps 1-6 again, with the following changes:
The VMs take a few minutes to create. Do not continue with the remaining steps until both VMs are created.
Azure provides an ephemeral IP for Azure Virtual Machines which aren't assigned a public IP address, or are in the backend pool of an internal Basic Azure Load Balancer. The ephemeral IP mechanism provides an outbound IP address that isn't configurable.
The ephemeral IP is disabled when a public IP address is assigned to the virtual machine or the virtual machine is placed in the backend pool of a Standard Load Balancer with or without outbound rules. If a Azure Virtual Network NAT gateway resource is assigned to the subnet of the virtual machine, the ephemeral IP is disabled.
For more information on outbound connections in Azure, see Using Source Network Address Translation (SNAT) for outbound connections.
Communicate between VMs
In the Search box at the top of the portal, begin typing myVm1. When myVm1 appears in the search results, select it.
Create a remote desktop connection to the myVm1 VM by selecting Connect, as shown in the following picture:
To connect to the VM, open the downloaded RDP file. If prompted, select Connect.
Enter the user name and password you specified when creating the VM (you may need to select More choices, then Use a different account, to specify the credentials you entered when you created the VM), then select OK.
You may receive a certificate warning during the sign-in process. Select Yes to proceed with the connection.
In a later step, ping is used to communicate with the myVm2 VM from the myVm1 VM. Ping uses the Internet Control Message Protocol (ICMP), which is denied through the Windows Firewall, by default. On the myVm1 VM, enable ICMP through the Windows firewall, so that you can ping this VM from myVm2 in a later step, using PowerShell:
New-NetFirewallRule –DisplayName "Allow ICMPv4-In" –Protocol ICMPv4
Though ping is used to communicate between VMs in this tutorial, allowing ICMP through the Windows Firewall for production deployments is not recommended.
To connect to the myVm2 VM, enter the following command from a command prompt on the myVm1 VM:
Since you enabled ping on myVm1, you can now ping it by IP address:
Disconnect your RDP sessions to both myVm1 and myVm2.
Clean up resources
When no longer needed, delete the resource group and all resources it contains:
- Enter myResourceGroup in the Search box at the top of the portal. When you see myResourceGroup in the search results, select it.
- Select Delete resource group.
- Enter myResourceGroup for TYPE THE RESOURCE GROUP NAME: and select Delete.