Setting up site-to-site on Microsoft Azure
  • 4 Minutes to read

Setting up site-to-site on Microsoft Azure


Note: If your device/service supports SHA256 and DH group 14, it is recommended to use these settings instead.

Creating Gateway Subnet

  1. In your Azure Management Portal, navigate to the Virtual networks

01 Setting up site-to-site on Microsoft Azure.png

  1. Select the name of the Virtual Network to which you'd like to create a gateway

  2. Under the Settings section of your VNet page, select Subnets

02 Setting up site-to-site on Microsoft Azure.png

  1. Select + Gateway subnet (the name of the subnet is filled in with the value "Gateway subnet" by default)

03 Setting up site-to-site on Microsoft Azure.png

  1. If needed, adjust the auto-filled Address range values to match your configuration requirements

In case this range is not automatically filled in:

  • Go to address space-> +Add
  • Select a random /27 bit mask subnet space (for example 10.1.255.0/27)

04 Setting up site-to-site on Microsoft Azure.png

Creating Virtual Network Gateway

  1. On the left side of the portal page, select + and type Virtual Network Gateway in the Search line

05 Setting up site-to-site on Microsoft Azure.png

  1. Locate and select the Virtual network gateway

06 Setting up site-to-site on Microsoft Azure.png

  1. Select Create

07 Setting up site-to-site on Microsoft Azure.png

  1. Fill in the fields with the following information:
  • Name: Your gateway name
  • Region/Location: Select the Virtual Network location\region where your resources are
  • Gateway type: Select VPN
  • VPN type: Select Route-based
  • SKU: Select the gateway SKU from the dropdown. The SKUs listed in the dropdown depend on the VPN you select

08 Setting up site-to-site on Microsoft Azure.png

  • Virtual network: Select the Virtual network that contains the resources you want to reach via the tunnel

Select a Virtual network to open the Choose a virtual network page.
If you don't see your VNet, make sure the Location/Region field is pointing to the region in which your virtual network is located.

09 Setting up site-to-site on Microsoft Azure.png

  • Gateway subnet address range: You will only see this setting if you did not previously create a gateway subnet for your virtual network. If you previously created a valid gateway subnet, this field will not appear
  • Public IP address: This specifies the public IP address object that's associated with the VPN gateway. The public IP address is dynamically assigned to this object when the VPN gateway is created
  • Enable active-active mode: Disabled
  • Configure BGP ASN: Disabled
  • Select Review+create to begin creating the VPN gateway

It can take up to 45 minutes for the task to be completed.

10 Setting up site-to-site on Microsoft Azure.png

Creating Local Network Gateway

  1. In the portal, select + Create a resource

11 Setting up site-to-site on Microsoft Azure.png

  1. In the search box type "Local network gateway"

12 Setting up site-to-site on Microsoft Azure.png

  1. Select Local network gateway, then select Create to open the Create local network gateway page

13 Setting up site-to-site on Microsoft Azure.png

  1. Fill in the fields with the following information:
  • Name Your gateway name
  • IP address: This is the public IP address of the VPN device that you want Azure to connect to. Specify the IP of your NordLayer dedicated server
  • Address Space: 10.6.0.0/20 (make sure that the ranges you specify here do not overlap with ranges of other networks that you want to connect to)
  • Subscription: Verify that the correct subscription is showing
  • Resource Group: Select the resource group that you want to use. You can either create a new resource group or select one that you have already created
  • Location: Select a location that this object will be created in. You may want to select the location in which your Virtual Network resides, however it is not a requirement
  • SKU: Select the gateway SKU from the dropdown. The SKUs listed in the dropdown depend on the VPN you select
  1. Select Create at the bottom of the page to create the local network gateway

14 Setting up site-to-site on Microsoft Azure.png

Creating the IPSEC tunnel connection

  1. Open your virtual network gateway page

  2. On the sidebar, select All resources

15 Setting up site-to-site on Microsoft Azure.png

  1. Select the Local network gateway you created. Once it opens, go to Settings, select Connections, and then +Add

16 Setting up site-to-site on Microsoft Azure.png

  1. Fill in the fields with the following information:
  • Name: Your connection name
  • Connection type : Select Site-to-site (IPSec)
  • Virtual network gateway: Since you are connecting from this gateway this value (the IP you received from Azure) is fixed
  • Local network gateway: The local network gateway (your NordLayer network address) which you have just created is the fixed value
  • Shared Key: the value here must match the value that you are using for your local on-premises VPN device
  • The remaining values for Subscription, Resource Group, and Location are fixed as well
  • Select OK to create your connection

17 Setting up site-to-site on Microsoft Azure.png

Verifying the VPN connection

  1. Go to the Azure Portal and select All Resources

18 Setting up site-to-site on Microsoft Azure.png

  1. Select the Virtual network gateway

19 Setting up site-to-site on Microsoft Azure.png

  1. Go to Connections

20 Setting up site-to-site on Microsoft Azure.png

  1. Select the connection you created

21 Setting up site-to-site on Microsoft Azure.png

  1. Under the Overview tab, make sure that the Status is Connected

22 Setting up site-to-site on Microsoft Azure.png

Ending note:

In order to finalize the site-to-site setup on our end, please provide these values via Site-to-site request from in the NordLayer Control Panel:

  • Pre-shared key - you can generate it or we can provide it
  • Encryption  details (AES, SHA and DH group) - AES256, SHA256 and DH group 14 are recommended (also must support IKEv2)
  • Remote gateway/router public IP (must be reachable while connected to the dedicated server)
  • Remote subnet and mask (the subnet is used in your local network)

Note: In case you are experiencing different results, make sure that you have you carefully gone through all the steps. Having said that, in case the issue persists please feel free to contact our 24/7 customer support team.


Was this article helpful?