{"id":9530,"date":"2026-04-06T21:50:40","date_gmt":"2026-04-06T21:50:40","guid":{"rendered":"https:\/\/pariswells.com\/blog\/?p=9530"},"modified":"2026-04-06T21:50:40","modified_gmt":"2026-04-06T21:50:40","slug":"how-to-use-azure-vpn-gateway-with-fortigate","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/research\/how-to-use-azure-vpn-gateway-with-fortigate","title":{"rendered":"How to use Azure VPN Gateway with Fortigate"},"content":{"rendered":"\n

We have gone from a setup which did the Site to Site VPNs via a Azure VPN Gateway as well as the Point to Site VPNs.<\/p>\n\n\n\n

We are migrating to a Fortigate in Azure to give Users a static IP Outbound. We will Migrate Site to Site VPNS to this also.<\/p>\n\n\n\n

We want to keep the Azure VPN Gateway for Point to Site as the Client supports SAML and also you don’t need to pay for the client upgrades like you do with Fortigate<\/p>\n\n\n\n

Setup Fortigate via Marketplace – See this for what you have to to https:\/\/pariswells.com\/blog\/research\/errors-when-deploying-azure-fortigate-from-marketplace-in-azure<\/a><\/p>\n\n\n\n

For example you’ve set the internal IP Fortigate to 10.5.6.4<\/p>\n\n\n\n

You will need to setup 2 new Routes<\/p>\n\n\n\n

A route that attaches to your Server Subnets routes all traffic apart from Local Traffic to Fortigate
<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n


A Route for the Azure VPN Gateway Subnet that Routes ALL Traffic to Fortigate. You have to divide the Subnet by 2 as a Route Table on the Gateway Subnet Doesn’t support 0.0.0.0\/0
<\/p>\n\n\n\n

    <\/ol>\n\n\n\n
    \"\"<\/a><\/figure>\n\n\n\n

    On the VPN Gateway you will want to add all the Routes to any Site to Site VPNs<\/p>\n\n\n\n

    \"\"<\/a><\/figure>\n\n\n\n

    Push the PPTP Subnet Back to Internal Port on the Fortigate<\/p>\n\n\n\n

    \"\"<\/a><\/figure>\n\n\n\n

    For Users that want to have their outbound internet via Fortigate for Static IP you will need to deploy new Azure VPN Config with the below Added<\/p>\n\n\n\n

     <includeroutes>\n      <route>\n          <destination>0.0.0.0<\/destination><mask>1<\/mask>\n      <\/route>\n      <route>\n          <destination>128.0.0.0<\/destination><mask>1<\/mask>\n      <\/route>\n  <\/includeroutes><\/code><\/pre>\n\n\n\n
    <\/p>\n","protected":false},"excerpt":{"rendered":"
    We have gone from a setup which did the Site to Site VPNs via a Azure VPN Gateway as well as the Point to Site VPNs. We […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-9530","post","type-post","status-publish","format-standard","hentry","category-research"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t