This post summarize the configuration for allowing Point-2-site vpn users to access your remote peering network. 

Related Post::


Steps to Configure Peering

The following steps assume you have configured both resource groups in different Azure regions, both virtual networks and one Point-2-site virtual network gateway. Your remote users are able to use this p2s gateway to access the resources in one region (one resource group).

To have your remote users to access another region’s network and resources, here are steps:

1 Go to your Azure virtual network, choose Peerings from left panel

2 Click add button

3 Enter local peering link name and remote peering link name. Azure will create two links for you in this one time setup.

4 Choose remote virtual network name 

Once you completed peering, the VMs can talk each other in those two virtual networks ( and without further configuration.

Note: You will notice virtual network gateway or route server ‘s default setting is none. In our next step, we will need to make change on this settings to allow remote P2S users to access peering networks. 

Configure Peering Links

1  Add a route for peering network into Virtual Network Gateway Configuration

2 Change Peering configuration on local

This will allow P2S users to access your remote peering network.

Explanation for Virtual network gateway or Route server: 

Dynamic routes for virtual machines in a virtual network are programmed by virtual network gateways or Route Servers. Additionally, a virtual network gateway routes traffic between on-premises networks and Azure virtual networks. A virtual network gateway can be created for either VPN Gateway or ExpressRoute.

3 Change Peering configuration on remote 

After above steps, your P2S users should be able to access remote site’s network. 

By netsec

Leave a Reply