Fortinet | unable to deploy FortiGate in Azure

Recently I tried to deploy a Fortinet Fortigate into azure. When I tried to add the FortiGate to the current VNETit wasn’t possible The option to select the current Vnet was greyed out. I figured out there is a workaround and the support of Microsoft was also amazed that it worked. In the following steps you can find how to work around this issue.

Th problem is that you have already a Gateway subnet with VPN connections. This cause the grey out selection. as you see n the first picture.

In this case, you have 3 options create a new VNETor cancel the deployment or delete all the existing VPN Connectoins and Gateway Subnet This is something new it seems with Azure that this isn’t possible anymore. Begin April of 2021 it was possible to add a FortiGate into the same subnet.

There is a workaround to get it working. You will need to add the subnets which you want to use for the deployment manually in the vnet selection.

Name the subnets like the options which is given in the template “see next steps” with a subnet range you want to use.

You need to go to Github for the Fortinet Azure Template.
At the subject Deployment, you need to choose under Azure Portal.

When you click on this button you will be redirected to your custom deployment screen. The red marked locations are important to have it correct.

names should be identical to the ones which are already exits. if you doing this right then the deployment will succeed, otherwise, you might receive an error that the deployment failed because of region-related settings.

If the deployment succeed you can access this virtual appliance and enter the license of FortiGate

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.