Fortigate Vm Sizing Azure Updated May 2026

Sizing FortiGate-VM on Microsoft Azure Sizing a FortiGate-VM in Microsoft Azure requires balancing technical resource requirements with licensing models to ensure peak performance for your network security workload. Core System Requirements

Generally avoided for production due to limited Network Interface Card (NIC) support and lower throughput. 2. The NIC Bottleneck: More Than Just Speed One of the most overlooked aspects of Azure sizing is NIC limits fortigate vm sizing azure

• Standard_D2s_v3 (2 vCPU, 8GB RAM) – Standard for VM01.
• Standard_D2s_v4 / v5 – Newer generations, slightly better network burst.

• Fortinet publishes throughput and vCPU guidance per FortiGate-VM SKU/datasheet — use those numbers as baseline.
• On Azure, prefer Dsv3/Dsv4, Ev3/Ev4, or Fsv2 families for predictable CPU/network. For network-intensive workloads, choose SKUs with high network bandwidth and accelerated networking support.

Avoid: Any -as v4 sizes (they have less network acceleration) and older A-series VMs. Sizing FortiGate-VM on Microsoft Azure Sizing a FortiGate-VM

*Throughput varies dramatically with features (SSL inspection, IPS, threat protection). Standard_D2s_v3 (2 vCPU, 8GB RAM) – Standard for VM01

High throughput, IPS, and SSL inspection. Often the best price-to-performance ratio for firewalls. Standard_F4s_v2, Standard_F8s_v2 D-Series (General Purpose)