Fortigate Vm Sizing Azure Official

To avoid performance bottlenecks, ensure your chosen size supports Accelerated Networking . This offloads packet processing from the CPU to the NIC, drastically reducing latency and jitter. 2. Matching FortiGate Licenses to Azure Sizes

The number of interfaces you can attach is strictly limited by the VM size. A single FortiGate instance often requires at least four NICs (Management, External, Internal, and HA Sync).

When selecting your size in the Azure Marketplace, keep these three technical limits in mind: fortigate vm sizing azure

Generally recommended for FortiGate because they offer a higher NIC-to-CPU ratio , which is essential for network-heavy workloads.

Official Fortinet datasheets often list performance for large packets (1518 bytes). If your traffic is dominated by small packets (e.g., VoIP or DNS), you will need a larger VM size than the datasheet suggests to handle the higher packet-per-second (PPS) rate. 4. Deployment Strategies for Scalability To avoid performance bottlenecks, ensure your chosen size

If a single VM isn't enough, consider these advanced architectures: FortiGate VM on Microsoft Azure Data Sheet - Fortinet

While FortiGate-VM can run on as little as 2 GB of RAM, features like Intrusion Prevention (IPS) and Antivirus are memory-intensive. For production, aim for at least 4 GB to 8 GB to ensure the system doesn't enter conserve mode . Matching FortiGate Licenses to Azure Sizes The number

Azure offers several VM families, but not all are suited for high-performance security inspection.

If you use Bring Your Own License (BYOL) , you can upgrade from a VM-01S to a VM-02S and then resize the Azure VM to match the new vCPU count within minutes. 3. Critical Sizing Constraints