Create an incoming one from the Azure site, and an outgoing from you local network. Now go to static routes and create a new route to your Azure virtual network you defined.

Remove PFS on phase 2 and set Seconds to 27000

And IKE V2Ĭhange the Key Life Time on Phase 1 to 28800 Then fill out the rest of the info like this, notice that NAT Traversal and Dead Peer Detection is off.Fill out the IP address with the Azure Virtual GW IP.Login to your Fortinet and go to the VPN tab.And click on add and fill inn the information you need. Now go to Connections in the new Local Network gateway and click on connections.Fill inn name, IP adress of your on site VPN device, fill inn ip adress range(Can fill inn more then one), if you have an excisitng Resource Group for your local networkGW use this. If you already have a Virtual Network Gateway and a Local Network Gateway setup and want to add a 2nd or more, go to step 6 in the Microsoft guide and set it up like you did the first one. Make sure they have been recently.įollow the MS guide and it’s straight forward. Combine these with other relevant guides. I recommend using there guides when it comes to azure setup. I used this guide to setup our Azure IPsec tunnel from Microsoft. Use Route Based VPN Type on the Azure Virtual Network Gateway for this. After Site 2 Site connection is deployed review your Azure gateway address and your Local gateway IP address: Login into the forgate management under VPN >. Thought i should write a small post about setting up a Site to Site VPN between Azure Resource Manager and a Fortigate Firewall on 5.4.

Fortigate azure vpn