Overview
Select the Azure virtual machine (VM) tier and size to meet your ASA Virtual needs. Any ASA Virtual license can be used on any supported ASA Virtual vCPU/memory configuration. This allows you to run the ASA Virtual on a wide variety of Azure VM sizes.
VM Size |
vCPUs |
Memory (RAM) in GB |
vNICs |
Supported ASA Virtual Version |
---|---|---|---|---|
Standard_D3 |
4 |
14 |
4 |
Any |
Standard_D3_v2 |
4 |
14 |
4 |
Any |
Standard_DS3 |
4 |
14 |
4 |
9.13 or above |
Standard_DS3_v2 |
4 |
14 |
4 |
9.13 or above |
Standard_D4 |
8 |
28 |
8 |
9.13 or above |
Standard_D4_v2 |
8 |
28 |
8 |
9.13 or above |
Standard_DS4 |
8 |
28 |
8 |
9.13 or above |
Standard_DS4_v2 |
8 |
28 |
8 |
9.13 or above |
Standard_D5_v2 |
16 |
56 |
8 |
9.15.1 or above |
Standard_DS5_v2 |
16 |
56 |
8 |
9.15.1 or above |
Standard_D8_v3 |
8 |
32 |
4 |
9.13 or above |
Standard_D16_v3 |
16 |
64 |
8 |
9.15.1 or above |
Standard_D8s_v3 |
8 |
32 |
4 |
9.17.1 or above |
Standard_D16s_v3 |
16 |
64 |
8 |
9.17.1 or above |
Standard_D8s_v5 |
8 |
32 |
8 |
9.24 or above |
Standard_D16s_v5 |
16 |
64 |
8 |
9.24 or above |
Standard_F4 |
4 |
8 |
4 |
9.13 or above |
Standard_F4s |
4 |
8 |
4 |
9.13 or above |
Standard_F8 |
8 |
16 |
4 |
9.13 or above |
Standard_F8s |
8 |
16 |
4 |
9.13 or above |
Standard_F16 |
16 |
32 |
4 |
9.15.1 or above |
Standard_F16s |
16 |
32 |
4 |
9.15.1 or above |
Standard_F8s_v2 |
8 |
32 |
4 |
9.17.1 or above |
Standard_F16s_v2 |
16 |
64 |
8 |
9.17.1 or above |
Performance Tier |
VM size (Core/RAM) |
Rate Limit |
RA VPN Session Limit |
---|---|---|---|
ASAv5 |
Standard_D3_v2 4 core/14 GB |
100 Mbps |
50 |
ASAv10 |
Standard_D3_v2 4 core/14 GB |
1 Gbps |
250 |
ASAv30 |
Standard_D3_v2 4 core/14 GB |
2 Gbps |
750 |
ASAv50 |
Standard_D4_v2 8 core/28 GB |
5.5 Gbps |
10,000 |
ASAv100 |
Standard_D5_v2 16 core/56 GB |
11 Gbps |
20,000 |
You can deploy the ASA Virtual on Microsoft Azure:
-
As a stand-alone firewall using the Azure Resource Manager on the standard Azure public cloud and the Azure Government environments
-
As an integrated partner solution using the Azure Security Center
-
As a high availability (HA) pair using the Azure Resource Manager on the standard Azure public cloud and the Azure Government environments
Note
In the event of unexpected failovers in a ASA Virtual HA setup, check the logs for any brief communication interruptions with peer ASA Virtual instances or Azure services. If such failover is observed, then it is advisable to configure a static IP address for the management interface instead of assigning IP address through DHCP.
See Deploy the ASA Virtual from Azure Resource Manager. Note that you can deploy the ASA Virtual HA configuration on the standard Azure public cloud and the Azure Government environments.