Fortigate Vm Sizing Azure ~repack~ (Trusted Source)

A single FortiGate-VM on Azure provides an Azure service-level agreement (SLA) of . For most production deployments, however, you will want higher availability. A single VM remains a single point of failure during both operations and planned maintenance.

Minimal CPU overhead. Traffic is processed via basic packet filtering. fortigate vm sizing azure

If you license a FG-VM04 but deploy it on a Standard_F8sv2 (8 vCPUs) Azure instance, FortiOS will artificially cap its resource usage to 4 vCPUs, wasting paid Azure infrastructure. Pay-As-You-Go (PAYG / On-Demand) A single FortiGate-VM on Azure provides an Azure

| | Example Instance | Max NICs | |---|---|---| | Fsv2-series (small) | Standard_F4s_v2, Standard_F8s_v2 | 2-4 | | Fsv2-series (large) | Standard_F16s_v2, Standard_F32s_v2 | 4-8 | | F-series (older) | Standard_F8, Standard_F16 | 8 | | Fs-series | Standard_F8s, Standard_F16s | 8 | | DSv2/Dsv3 (general purpose) | Standard_DS4_v2, Standard_D8s_v3 | 4-8 | Minimal CPU overhead

| Use Case | Recommended VM Size (BYOL) | License | Expected Throughput | |----------|----------------------------|---------|----------------------| | Small branch / Dev test | D2sv5 (2 vCPU, 8 GB) | PAYG | 300–500 Mbps | | Medium enterprise hub | D4sv5 (4 vCPU, 16 GB) | BYOL | 1–1.5 Gbps | | IPS + SSL inspection (1 Gbps) | E8sv5 (8 vCPU, 64 GB) | BYOL | 800 Mbps – 1.2 Gbps | | VPN concentrator (500 users) | F8sv2 (8 vCPU, 16 GB) | BYOL | 1.5 Gbps IPSec | | Large perimeter (>2 Gbps) | E16sv5 (16 vCPU, 128 GB) | BYOL | 4–6 Gbps |