Configuring Azure VNet Peering by using the Azure Portal
VNet peering is a mechanism that connects Azure networks (VNets) within the same Azure region through Azure backbone network. Once peered, virtual networks will work as a single network and resources can be accessed from both VNets via private IP addresses. VNet peering routes packets between virtual networks through the internal Azure backbone network. So VNet has not require Azure gateway between these networks. This allows a low-latency, high-bandwidth connection via virtual network peering.
To configure VNet peering we need at least two Virtual network in the same Azure region. In my previous Azure article, we have created virtual network and subnets in the Azure portal. Now, we need to create one more virtual network to configure VNet peering. So we start from creating Virtual network.
Creating virtual network:
1.In the Hub menu on the left side of the portal page, click New.
2. On the New blade, click Networking. On the Networking blade, click Virtual Network.
3. On the Create virtual network blade, specify the following settings, and then click Create:
- Name: MSSERVERPRODEMO-VNet
- Address space:10.1.0.0/16
- Subnet name: DemoSubnet
- Subnet address range: 1.0.0/24
- Subscription: Your Azure subscription
- Resource group: MSSERVERPRO-RG
- Location: the same Azure region you chose when creating the first virtual network
4. With the virtual network created, in the Azure portal, click All resources to Virtual networks.
Configuring VNet Peering:
Before configuring of Azure VNet Peering, you need to ensure to meet the following pre-requisites:
- Two VNets should be in the same region but can be in two different subscriptions
- Two VNets should have non-overlapping IP addresses
- There is no derived transitive relationship
1. On the dashboard of the Azure portal, click MSSERVEPRO-VNet.
2. On the MSSERVERPRO-VNet blade, click Peerings, then Click + Add.
3. On the Add peering blade, give a peering link in the Name text box, type MSSERVERPRO-VNetTO MSSERVERPRODEMO-VNet. Ensure that the Virtual network deployment model is set to Resource manager.
4. Ensure that Subscription is set to the Azure subscription you intend to use.
5. Click Choose a virtual network. On the Choose virtual network blade, click MSSERVERPRODEMO-VNet.
6. Ensure that Allow virtual network access is set to Enabled. Leave remaining settings Allow forwarded traffic, Allow gateway transit, and Use remote gateways with their default values (disabled). Click OK.
7. After clicking OK, it will take a few minutes until connection is established. Once this VNet peering link is created, you can see the status of the connection in the peering blade as Initiated:
8. Close the MSSERVERPRO-VNet-Peerings Virtual network.
9. Next create the VNet peering link for MSSERVERPRODEMO-VNet to MSSERVERPRO-VNet. On the dashboard of the Azure portal, click MSSERVERPRODEMO-VNet. On the MSSERVERPRODEMO-VNet blade, click Peerings. Click on + Add.
10. On the Add peering blade, give a peering link name in the Name text box, type MSSERVERPRODEMO-VNet to MSSERVERPRO-VNet. Ensure that the Virtual network deployment model is set to Resource manager. Ensure that Subscription is set to the Azure subscription you intend to use.
11. Click Choose a virtual network. On the Choose virtual network blade, click MSSERVERPRO-VNet.
12. Ensure that Allow virtual network access is set to Enabled. Leave remaining settings Allow forwarded traffic, Allow gateway transit, and Use remote gateways with their default values (disabled). Click OK.
13. Once completed this VNet peering link is created, you can see the status of VNet peering updated to “Connected”.
Azure VNet peering is one of the great feature of Azure Virtual network connectivity. VNet peering, which connects Azure virtual networks within the same Azure region through Azure backbone network. I hope this article help.
- Configuring a VNet-to-VNet VPN Gateway Connection Using the Azure Portal - October 27, 2017
- Configuring Azure VNet Peering by using the Azure Portal - October 19, 2017
- Using the Azure Portal to Create Virtual Networks, Add Subnets and Setting up a DNS Server Address - October 17, 2017
- Extend Azure Virtual Machine OS drive using Azure Portal - June 30, 2017
- Creating a Windows Virtual Machine and Availability Set at the same time using the Azure Portal - June 11, 2017
- Remove a Node from a Windows Server 2016 Hyper-V Cluster and Destroy a Cluster Procedure - May 14, 2017
- Best Practices on Setting up Hyper-V Cluster Networks in Windows Server 2016 - May 10, 2017
- Implementing Failover Clustering with Windows Server 2016 Hyper-V - May 6, 2017
- Configuring iSCSI Storage and Initiator in Windows Server 2016 - April 20, 2017
- Upgrading the VM configuration version in Windows Server 2016 Hyper-V - April 5, 2017