Introduction Users of Microsoft Azure might have received a several
notifications regarding the retirement of the basic SKU public IP
addresses.
https://azure.microsoft.com/en-gb/updates/upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-sept...
Introduction IPSEC is a group of protocols that can be challenging to
get right. There are multiple parameters to take into account. Microsoft
Azure networking and the FortiGate NGFW deployment in it, has some
specific design and limitations to take ...
Introduction In case a specific release provided by Fortinet is required
or the use of the Azure Marketplace is not possible the FortiGate-VM can
be deploy using an Azure Compute Gallery. The regular VHD images are
available via support.fortinet.com....
Introduction The FortiGate-VM ARM and Terraform templates for a Single
VM and Active/Passive architectures attach a public IP directly on the
VM. In some organisations a public IP can't be attached to a VM enforced
by Azure Policy to prevent direct a...
Introduction FortiGate on Microsoft Azure supports the PAYG as well as
the BYOL model. PAYG allows you to pay for the FortiGate VM on a
consumption basis, meaning you are billed only for the resources you
use. This can be particularly advantageous fo...
Hi, In Azure the public IP is never seen by the VM running inside of a
VNET. The public IP is translated to the private IP attached to the VM.
In case of a FortiGate VM this means you will have a private IP on the
external side of the FortiGate linke...
Hi, This is a support forum for AWS. From the image you have downloaded
I can see you are trying to install on KVM. Is that the case? The FFW is
not the same as the regular FortiGate. You should download an image that
has the following name. It shoul...
Hi, There are 2 options for migration between zones in the same region.
The blog below will allow you to retain the config and license on the
unit.
https://nicolgit.github.io/Moving-a-virtual-machine-between-availability-zones-in-Azure/
An alternativ...
Hi, If you want to make sure only your traffic passing via Azure Front
Door enters your network via the FortiGate, working with a private
endpoint would give you the most secure solution. I'm not aware of a
document that combines all of this. However...
Hi RJ1, As you are using the Azure Load Balancer (external and
internal), make sure to review the behavior when a back-end server (FGT
in this case) fails.
https://learn.microsoft.com/en-us/azure/load-balancer/components#health-probes
Joeri