| License Tier | Max Throughput (Firewall) | Max Throughput (Threat Protection) | vCPU Limit (Soft) | | :--- | :--- | :--- | :--- | | | 1 Gbps | 500 Mbps | 2 vCPU | | VM02 | 2 Gbps | 1 Gbps | 2 vCPU | | VM04 | 5 Gbps | 2.5 Gbps | 4 vCPU | | VM08 | 10 Gbps | 5 Gbps | 8 vCPU | | VM16 | 20 Gbps | 10 Gbps | 16 vCPU | | VMXL | Unlimited* | Unlimited* | Unlimited* |
When sizing your instance, performance is determined by more than just raw CPU count. You must consider: fortigate vm sizing azure
2024 Standards Scope: Infrastructure Architects, Security Engineers, Cloud Administrators | License Tier | Max Throughput (Firewall) |
: 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. If you purchase a VM04 license but deploy
If you purchase a VM04 license but deploy a 32-vCPU Azure instance, your throughput will cap at 5 Gbps (Firewall). Conversely, if you purchase a VMXL license but deploy a small instance, you are limited by the instance's hardware.