Easiest way to create Regional Virtual Network Peering.
Tags: cloudcomputing, azure, programming, beginners
Published: 2023-12-14 23:45:54

## Introduction
Through Azure Virtual Network Peering, virtual networks in the same or separate regions can be connected. Secure communication between resources in the peering networks is facilitated by Azure Virtual Network peering. Azure Virtual Network peering comes in two types: regional and global.
Azure virtual networks located in the same region can be connected using regional virtual network peering.
Azure virtual networks located in various locations are connected through global virtual network peering.
We will be looking at regional virtual network peering in this article and the steps involved are shown below.

NOTE: The Network Contributor or Classic Network Contributor must have an Azure account given to them in order to implement virtual network peering.

- Log in to your azure account.
- Click create a resource
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/7ipp1ekp3fojovmd6xnb.png)
- Search for virtual network in the Market place
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/zki4801xus2g7betv479.png)
- Fill in the project details which comprises subscription and resource group
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/4k6x0dkzwe0gjffxp4qf.png)
- Then fill the instance details which comprises virtual network name and region.
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2ci1vslkrha23nfskq19.png)
- Change the tab from Basics to Ip addresses
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ncx7oudqaww3cm73gj2y.png)
- Edit the Ipv4 address space to 10.1.0.0
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/n7mrbkrxu11o3ic3tmql.png)
- We are going to create two subnets: frontend and backend with subnet address range 10.1.0.0/24 and 10.1.1.0/24 respectively
- Click Default to edit the subnet, give a name for the subnet and change the starting address to 10.1.0.0 and leave the other settings as default and click save
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/v4jlpwsx8z10wlhk3h2a.png)
- Click Add a subnet to create the second subnet called backend
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/uy9w3aap9yzyvxhl5xad.png)
- Click review + create
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/mdeuc89k3oz5e94r1t5j.png)
- Click create once validation is passed
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/widaldugnurfsoe6flgt.png)
- Next thing is to create the second virtual network with the same method above in the same resource group.
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/6h2fnkm8zxijsgeba03b.png)
You will see the two virtual network app-vnet and shared-service-net in the same region Eastus

## How to establish Region Peering between the two virtual networks
- Click the first virtual network in the resource group
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/s6pu638tmvvafftsfeu5.png)
- Click peering 
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/x0ztn0m4jbpigwylmhaq.png)
- Select +Add in the peering pane
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/wl6zp6029s6r2tj2vpa3.png)
- Give a name to peering link name under this virtual network and under remote virtual network.
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vzhvy0kuocujn4y5k723.png)
- Select the virtual network, leave other settings as default and click Add
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/5rsrci07liglvtpzycbq.png)
- This will take you to a page where the peering status is showing connected. That means you have successfully peered the two virtual networks.
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2k4oq6gfw2yv72jo8yi0.png)