Disable VNET selection based on address range when deploying FortGate about azure-templates HOT 5 CLOSED

Hi, Joeri

Thank you for applying the revised VNET form

Thank you.

from azure-templates.

Hi,

Thank you for contacting Fortinet. We have reviewed your report and it seems the minimum values are a little too strict. We will be working on getting these changed. For now, can you try with the templates on the GitHub repo below which already have the changes applied. Select the deployment you would like and use the 'Deploy to Azure' button next to the Azure Portal Wizard text.

https://github.com/40net-cloud/fortinet-azure-solutions/tree/main/FortiGate

Hope this helps you in your deployment.

Kind regards,

Joeri

from azure-templates.

Hi, Joeri

Thank you for your quick reply.

I deployed Fortgate using the modified template.
The creation of a new VNET seems to remove the address space (prefix25 to 32).
However, previously created VNETs are still not available.

I look forward to hearing from you about this.
Have a nice day :)

from azure-templates.

Hi,

One limitation I hadn't removed was the size of the subnet. It has now been lowered to the smalest size possible for the deployment. Can you retry again in the below repo?

https://github.com/40net-cloud/fortinet-azure-solutions/tree/main/FortiGate

Regards,

Joeri

from azure-templates.

Closing the issue now. We will publish this on the repo here as well this week.

from azure-templates.