Sizing a FortiGate-VM in Azure requires balancing Azure's virtual machine performance with Fortinet's licensing tiers. Because Azure throttles network throughput based on the instance size, choosing a VM with enough vCPUs and RAM is critical for security performance. 1. Minimum Requirements
| vCPUs | RAM (GB) | Est. Firewall (Gbps) | Est. IPSec (Gbps) | Est. SSL Inspection (Mbps) | |-------|----------|----------------------|--------------------|-----------------------------| | 2 | 4 | 0.5 – 0.8 | 0.2 – 0.3 | 50 – 100 | | 4 | 8 | 1.0 – 1.5 | 0.5 – 0.8 | 150 – 250 | | 8 | 16 | 2.0 – 3.0 | 1.0 – 1.5 | 400 – 600 | | 16 | 32 | 4.0 – 6.0 | 2.0 – 3.0 | 800 – 1200 | fortigate vm sizing azure
Right-Sizing Your FortiGate VM in Microsoft Azure: A Practical Guide Deploying a FortiGate Next-Generation Firewall (NGFW) Sizing a FortiGate-VM in Azure requires balancing Azure's
To reach the multi-gigabit speeds advertised in datasheets, two Azure-specific features are non-negotiable: Minimum Requirements | vCPUs | RAM (GB) | Est
Compute Optimized (F-Series): Ideal for high-throughput tasks like batch processing or high-performance web servers.