| Use Case | FortiGate SKU | Azure VM Size | vCPU | RAM | |----------|--------------|---------------|------|-----| | Small office (100 users, 300 Mbps) | FG-VM01 | D2s v3 | 2 | 8 GB | | Branch (500 users, 1.5 Gbps, IPS) | FG-VM02 | D4s v3 | 4 | 16 GB | | HQ (2000 users, 3 Gbps + SSL) | FG-VM04 | D8s v3 | 8 | 32 GB | | VPN concentrator (1000 tunnels) | FG-VM08 | D16s v3 | 16 | 64 GB | | Heavy SSL + logging (5 Gbps) | FG-VM08 | E8s v3 | 8 | 64 GB |
Final tip: Always over-provision by one VM size in Azure—you can scale down later, but undersizing causes production packet loss. Use Azure’s reserved instances for 1-3 year commitment to reduce cost. fortigate vm sizing azure
For environments above 2 Gbps, consider FortiGate-VM with vSRX or native Azure Firewall Premium for cost comparison – FGT-VM often wins on features but not always on raw Azure throughput. | Use Case | FortiGate SKU | Azure
Note: Always refer to the latest Fortinet Azure Sizing Guide (FortiOS 7.4+) and Microsoft’s VM documentation, as both companies update performance data quarterly. Final tip : Always over-provision by one VM
This is a comprehensive guide and "paper-style" breakdown regarding FortiGate VM Sizing on Microsoft Azure. This document covers the selection methodology, specific SKU mappings, licensing implications, and architectural best practices.
UTM cuts throughput by 40–60% compared to raw firewalling.