Fortigate Vm Sizing Azure _verified_ -

FortiGate VM sizing for Azure

Summary

Storage: Most deployments start with 32 GB of disk space, expandable up to 2 TB for logging and reporting. 2. Selecting the Right Azure Instance Series fortigate vm sizing azure

Cons:

Part 7: Common Sizing Mistakes (And How to Avoid Them)

Mistake #1: Using B-series VMs for Production

Why it fails: B-series earns CPU credits then throttles. Packet loss begins at 30 minutes of sustained 100 Mbps.
Fix: Minimum D2s_v3 for any production FortiGate.

Select vCPUs:

config log disk
    set status enable
    set max-log-file-size 100
    set full-final-warning threshold 90
end

The most flexible option. You are charged based on the Azure instance size, and the license scales automatically as you resize the VM. Bring Your Own License (BYOL): FortiGate VM sizing for Azure Summary Storage: Most

8. Common Sizing Mistakes

| Mistake | Consequence | |---------|--------------| | Using B-series VMs | Severe throttling during bursts → packet loss | | Forgetting accelerated networking | Throughput drops to <200 Mbps even on large VMs | | Matching on-prem VM size directly | Azure has higher virtualization overhead → need 2x vCPUs often | | Ignoring IPS session table size | Large tables need more RAM (E-series) | | Single NIC for LAN+WAN | Bypasses Azure routing best practices; use at least 2 NICs | Why it fails: B-series earns CPU credits then throttles

Compute Optimized (F-Series / Fs-Series): Best for high-performance security processing where CPU speed is critical .