Fortigate Vm Sizing Azure [best]

FortiGate-VM on Microsoft Azure

For sizing a , the most critical factor is aligning your vCPU count with your Fortinet license (BYOL) or choosing an Azure instance family that maximizes throughput and network interface (NIC) support . Core Sizing Recommendations

Finally, test with your real traffic – not synthetic UDP floods. Cloud networking behaves differently on Tuesday at 2 PM vs. Friday at 5 PM. Use FortiView’s “Top Threats” and “Top Applications” to refine your sizing every quarter. fortigate vm sizing azure

• Standard_D4s_v3 (4 vCPU, 16GB RAM) – Matches VM04 license.
• Standard_D4s_v4 / v5 – Recommended for better bandwidth.
• Standard_F4s_v2 (4 vCPU, 8GB RAM) – Compute optimized. Good for heavy IPS/SSL inspection where CPU is the bottleneck, though RAM is lower.

Mandatory.

Without it, you lose SR-IOV, and throughput drops by >70%. FortiGate-VM on Microsoft Azure For sizing a ,

On-premises, a FortiGate 100F has a specific throughput (e.g., 10 Gbps). In Azure, a VM has a "Max Bandwidth" limit set by Microsoft. Standard_D4s_v3 (4 vCPU, 16GB RAM) – Matches VM04

FortiGate VM Sizing Guidelines

Not all Azure VM families work well for firewalls. The following are field-proven: