Next, we'll define the gateway network inside of the virtual network we just created. In our case the virtual network is called VNET-01. Click back into VNET-01, select Subnets | Gateway Subnet. Define the gateway subnet (in our case 10.10.1.0/24) and click Create.
Next, we'll create a virtual network gateway. In the search bar at the top of the page start typing gateway. Select Virtual network gateway.
Create a new virtual network gateway. Give the gateway a name and define the VPN type. We'll select gateway type VPN and VPN type Route-based. Select the virtual network (in our case VNET-01) and create a new public IP address. We'll use this public IP address later on while configuring the VPN on the SonicWall. Click Create.
NOTE: Provisioning a virtual network gateway may take up to 45 minutes.
Click on the newly created virtual network gateway. Select Connections | Add.
Give the connection a name. Under connection type select Site-to-site (IPSec). Create a new local network gateway. This will be the public IP of the SonicWall and the local network. In our case the local network of the SonicWall is the default SonicWall subnet 192.168.168.0/24.
Provide a secure shared key. This will also be used on the SonicWall. Click OK.
We'll grab the public IP of Azure and use it in the SonicWall. Navigate to Dashboard and select the Public IP address resource. Take a note of the public IP for the next steps.
Login to the SonicWall firewall.
Navigate to the VPN policy tab. We're using the latest SonicOS 6.5 firmware. Click Manage | VPN | Base Settings. Click Add.
Give the VPN policy a name. We'll use the following settings:
Policy Type: Tunnel Interface Authentication Method: IKE using Preshared Secret
Next click the Proposals tab.Under Proposals select:
IKE (Phase 1) Proposal: Exchange - IKEv2 Mode, DH Group - 2, Encryption - AES-256, Authentication - SHA1, Life Time - 28800. IKE (Phase 2) Proposal: Protocol - ESP, Encryption - 3DES, Authentication - SHA1, Life Time - 27000.
Select the Advanced tab. Select Enable Keep Alive. Deselect Enable Windows Networking. Select Do not send trigger packet during IKE SA negotiation.
Next, navigate to Manage | Network | Routing. Select Route Policies and create a new policy. Set the destination for the Azure network and select the Azure interface.
NOTE: It takes 5-7 minutes for the VPN policy to come up. Once the VPN policy is up we see a green indicator and a new entry under Currently Active VPN Tunnels.