- Now we need to establish a connection between gateways and enable the routing: Please go back to your resource group and click Add again. Now we look for Connection in the marketplace. Then select Connection:
- Now change the Connection type to Site-to-site (IPsec):
- In the Settings phase, we first select the Azure Virtual network gateway, Local network gateway, Connection name and Shared key:
- To check if the connection is deployed and working fine, you need to leverage the connection item in your resource group:
- There is an Overview within the detail blade of the connection. When the connection is successful the Status will change to Successful:
In most of the cases when the Status of the connection is not changing to connected, there are misconfiguration on the on premises Firewall or Network device. Mostly it's because there are different configurations of timeouts or encryption. For most of the VPN Devices you can find configuration guides on within the Azure documentation. https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways. If you still have issues, please contact the support of your VPN device manufacturer.
- If you want to connect multiple sites to one Azure environment, you need to configure the Azure Virtual network gateway as a Route-based VPN and create a Local network gateway for each on-premises site. Then you create a connection for each site link. The following diagram illustrates the count of connections that need to be set up:
You need at least one route-based Virtual network gateway (1), one Public IP address for the gateway (2), two Local network gateways (3) and two Connections between Virtual network and Local network gateway (4).
- Now you have deployed a site-to-site tunnel to your on-premises environment.
As of September 2016, Microsoft started to support active/active site-to-site VPN tunnels with high performance virtual network gateway. Therefore, you need to configure two local network gateways: VNets and VPN gateways.