Skip to content

Commit 88ebeb6

Browse files
duongauduongau
committed
docs: fix metadata, Next steps heading, style edits
1 parent 8223636 commit 88ebeb6

1 file changed

Lines changed: 29 additions & 30 deletions

File tree

‎articles/firewall/firewall-performance.md‎

Lines changed: 29 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -1,77 +1,76 @@
11
---
2-
title: Azure Firewall performance
3-
description: Compare Azure Firewall performance for Azure Firewall Basic, Standard, and Premium.
4-
services: firewall
2+
title: Azure Firewall performance
3+
description: Learn about Azure Firewall performance data and throughput benchmarks for Basic, Standard, and Premium SKUs across different use cases.
54
author: duongau
65
ms.service: azure-firewall
76
ms.topic: concept-article
8-
ms.date: 12/26/2024
7+
ms.date: 03/28/2026
98
ms.author: duau
109
# Customer intent: As a network engineer, I want to compare the performance metrics of Azure Firewall Basic, Standard, and Premium, so that I can choose the appropriate version to meet my organization’s security and performance requirements.
1110
---
1211

1312
# Azure Firewall performance
1413

15-
Reliable firewall performance is essential to operate and protect your virtual networks in Azure. More advanced features (like those found in Azure Firewall Premium) require more processing complexity, and affect firewall performance and overall network performance.
14+
Reliable firewall performance is essential to operate and protect your virtual networks in Azure. More advanced features, like those found in Azure Firewall Premium, require more processing complexity and affect firewall performance and overall network performance.
1615

1716
Azure Firewall has three versions: Basic, Standard, and Premium.
1817

1918
- Azure Firewall Basic
20-
19+
2120
Azure Firewall Basic is intended for small and medium size (SMB) customers to secure their Azure cloud environments. It provides the essential protection SMB customers need at an affordable price point.
2221

2322
- Azure Firewall Standard
2423

25-
Azure Firewall Standard became generally available in September 2018. It's cloud native, highly available, with built-in auto scaling firewall-as-a-service. You can centrally govern and log all your traffic flows using a DevOps approach. The service supports both application and network level-filtering rules, and is integrated with the Microsoft Threat Intelligence feed for filtering known malicious IP addresses and domains.
24+
Azure Firewall Standard became generally available in September 2018. It's cloud native, highly available, with built-in auto scaling firewall-as-a-service. You can centrally govern and log all your traffic flows by using a DevOps approach. The service supports both application and network-level-filtering rules, and is integrated with the Microsoft Threat Intelligence feed for filtering known malicious IP addresses and domains.
2625
- Azure Firewall Premium
2726

28-
Azure Firewall Premium is a next generation firewall. It has capabilities that are required for highly sensitive and regulated environments. The features that might affect the performance of the Firewall are TLS (Transport Layer Security) inspection and IDPS (Intrusion Detection and Prevention).
27+
Azure Firewall Premium is a next generation firewall. It has capabilities that are required for highly sensitive and regulated environments. The features that might affect the performance of the firewall are TLS (Transport Layer Security) inspection and IDPS (Intrusion Detection and Prevention).
2928

3029
For more information about Azure Firewall, see [What is Azure Firewall?](overview.md)
3130

3231
## Performance testing
3332

34-
Before you deploy Azure Firewall, the performance needs to be tested and evaluated to ensure it meets your expectations. Not only should Azure Firewall handle the current traffic on a network, but it should also be ready for potential traffic growth. You should evaluate on a test network and not in a production environment. The testing should attempt to replicate the production environment as close as possible. You should account for the network topology, and emulate the actual characteristics of the expected traffic through the firewall.
33+
Before you deploy Azure Firewall, test and evaluate the performance to ensure it meets your expectations. Azure Firewall should handle the current traffic on a network and be ready for potential traffic growth. Evaluate the performance on a test network, not in a production environment. The testing should attempt to replicate the production environment as closely as possible. Account for the network topology, and emulate the actual characteristics of the expected traffic through the firewall.
3534

3635
## Performance data
3736

38-
The following set of performance results demonstrates the maximal Azure Firewall throughput in various use cases. All use cases were measured while Threat intelligence mode was set to alert/deny. Azure Firewall Premium performance boost feature is enabled on all Azure Firewall premium deployments by default. This feature includes enabling Accelerated Networking on the underlying firewall virtual machines.
37+
The following performance results demonstrate the maximum Azure Firewall throughput in various use cases. You measure all use cases while Threat intelligence mode is set to alert or deny. The Azure Firewall Premium performance boost feature is enabled by default on all Azure Firewall premium deployments. This feature includes enabling Accelerated Networking on the underlying firewall virtual machines.
3938

4039

41-
|Firewall type and use case |TCP/UDP bandwidth (Gbps) |HTTP/S bandwidth (Gbps) |
40+
| Firewall type and use case | TCP/UDP bandwidth (Gbps) | HTTP/S bandwidth (Gbps) |
4241
|---------|---------|---------|
43-
|Basic SKU |0.25|0.25|
44-
|Standard SKU |30|30|
45-
|Premium SKU with both TLS disabled and IDPS disabled |100|100|
46-
|Premium SKU with TLS inspection enabled and IDPS disabled |-|100|
47-
|Premium SKU with TLS enabled and IDPS enabled in Alert only mode |100|100|
48-
|Premium SKU with TLS enabled and IDPS enabled in Deny mode |10|10|
42+
| Basic SKU | 0.25 | 0.25 |
43+
| Standard SKU | 30 | 30 |
44+
| Premium SKU with both TLS disabled and IDPS disabled | 100 | 100 |
45+
| Premium SKU with TLS inspection enabled and IDPS disabled | - | 100 |
46+
| Premium SKU with TLS enabled and IDPS enabled in Alert only mode | 100 | 100 |
47+
| Premium SKU with TLS enabled and IDPS enabled in Deny mode | 10 | 10 |
4948

5049
### Throughput for single connections
5150

52-
|Firewall use case |Throughput (Gbps)|
51+
| Firewall use case | Throughput (Gbps) |
5352
|---------|---------|
54-
|Basic|up to 250 Mbps|
55-
|Standard<br>Max bandwidth for single TCP connection |up to 1.5|
56-
|Premium<br>Max bandwidth for single TCP connection |up to 9|
57-
|Premium single TCP connection with IDPS on *Alert and Deny* mode|up to 300 Mbps|
53+
| Basic | up to 250 Mbps |
54+
| Standard<br>Max bandwidth for single TCP connection | up to 1.5 |
55+
| Premium<br>Max bandwidth for single TCP connection | up to 9 |
56+
| Premium single TCP connection with IDPS on *Alert and Deny* mode | up to 300 Mbps |
5857

59-
### Total throughput for initial firewall deployment
58+
### Total throughput for initial firewall deployment
6059

61-
The following throughput numbers are for an Azure Firewall Standard and Premium deployments before autoscale (out of the box deployment). Azure Firewall gradually scales out when the average throughput and CPU consumption is at 60% or if the number of connections usage is at 80%. Scale out takes five to seven minutes. Azure Firewall gradually scales in when the average throughput, CPU consumption, or number of connections is below 20%.
60+
The following throughput numbers are for Azure Firewall Standard and Premium deployments before autoscale (out-of-the-box deployment). Azure Firewall gradually scales out when the average throughput and CPU consumption reach 60% or if the number of connections usage reaches 80%. Scale out takes five to seven minutes. Azure Firewall gradually scales in when the average throughput, CPU consumption, or number of connections drops below 20%.
6261

63-
When performance testing, make sure you test for at least 10 to 15 minutes, and start new connections to take advantage of newly created firewall nodes.
62+
When performance testing, test for at least 10 to 15 minutes, and start new connections to take advantage of newly created firewall nodes.
6463

6564

66-
|Firewall use case |Throughput (Gbps)|
65+
| Firewall use case | Throughput (Gbps) |
6766
|---------|---------|
68-
|Standard<br>Max bandwidth |up to 3 |
69-
|Premium<br>Max bandwidth |up to 18|
67+
| Standard<br>Max bandwidth | up to 3 |
68+
| Premium<br>Max bandwidth | up to 18 |
7069

7170
> [!NOTE]
7271
> Azure Firewall Basic doesn't autoscale.
7372
74-
## Next step
73+
## Next steps
7574

7675
> [!div class="nextstepaction"]
77-
> [deploy and configure an Azure Firewall](tutorial-firewall-deploy-portal.md)
76+
> [Deploy and configure an Azure Firewall](tutorial-firewall-deploy-portal.md)

0 commit comments

Comments
 (0)