In 2026, with the increasing complexity of cloud workloads, proper sizing involves analyzing throughput, network connectivity requirements, and the specific security features enabled. This guide covers how to size your FortiGate VM in Azure for optimal performance. 1. Key Factors for FortiGate VM Sizing in Azure
Microsoft Azure offers dozens of VM families, but only a few are optimized for compute-intensive and network-heavy security virtual appliances. The Standard Choice: Dv4 / Dsv4 / Ddv4 Series
Deploying a virtual appliance in the cloud requires a strict balance between security performance and infrastructure costs. Unlike physical firewalls with fixed hardware capacities, a Fortinet FortiGate Virtual Machine (VM) running in Microsoft Azure depends entirely on the underlying Azure virtual machine size for its CPU, memory, networking, and storage capabilities. fortigate vm sizing azure
Sizing FortiGate VMs in Microsoft Azure: A Comprehensive Engineering Guide
| Use Case | VM Size | vCPU | RAM (GB) | Max NICs | Est. Real Throughput | |----------|---------|------|----------|----------|----------------------| | (<500 Mbps) | D2s v3 / D2ds v4 | 2 | 8 | 4 | ~500-800 Mbps | | Medium branch (1-2 Gbps) | D4s v3 / D4ds v4 | 4 | 16 | 8 | ~1.5-2 Gbps | | Large branch / DC (2-4 Gbps) | D8s v3 / D8ds v4 | 8 | 32 | 8 | ~3-4 Gbps | | Enterprise / VPN hub (5-8 Gbps) | D16s v3 / D16ds v4 | 16 | 64 | 8 | ~6-8 Gbps | | Heavy SSL inspection (4-6 Gbps) | E8s v3 / E8ds v4 | 8 | 64 | 8 | ~4-5 Gbps | In 2026, with the increasing complexity of cloud
Select a new VM instance type (e.g., moving from Standard_D2s_v5 to Standard_D4s_v5 ). Start the VM.
You can resize your existing FortiGate-VM to a larger Azure instance type within the same series. For example, upgrading from a Standard_F4s_v2 to a Standard_F8s_v2 requires you to stop the VM (deallocate it), change its size, and then restart it. This process is disruptive, so it should be planned during a maintenance window. Key Factors for FortiGate VM Sizing in 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
Note: For BYOL (Bring Your Own License) scenarios, check the CPU limits associated with your license tier. 3. Sizing Guidelines (Throughput & CPU)
If your traffic needs change, you can resize the VM without losing configuration: Stop the FortiGate VM within the Azure Portal. Navigate to in the VM menu.