Skip to content

Commit cfe789e

Browse files
Merge pull request #221862 from mbender-ms/patch-39
Azure Firewall - Update Performance Considerations - mbender
2 parents b48d514 + 156e891 commit cfe789e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/firewall/premium-migrate.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,9 +33,9 @@ If you use Terraform to deploy the Azure Firewall, you can use Terraform to migr
3333

3434
## Performance considerations
3535

36-
Performance is a consideration when migrating from the standard SKU. IDPS and TLS inspection are compute intensive operations. The premium SKU uses a more powerful VM SKU, which scales to a maximum throughput of 30 Gbps comparable with the standard SKU. The 30-Gbps throughput is supported when configured with IDPS in alert mode. Use of IDPS in deny mode and TLS inspection increases CPU consumption. Degradation in max throughput might occur.
36+
Performance is a consideration when migrating from the standard SKU. IDPS and TLS inspection are compute intensive operations. The premium SKU uses a more powerful VM SKU, which scales to a higher throughput comparable with the standard SKU. For more information about Azure Firewall Performance, see [Azure Firewall Performance](firewall-performance.md)
3737

38-
The firewall throughput might be lower than 30 Gbps when you’ve one or more signatures set to **Alert and Deny** or application rules with **TLS inspection** enabled. Microsoft recommends customers perform full-scale testing in their Azure deployment to ensure the firewall service performance meets your expectations.
38+
Microsoft recommends customers perform full-scale testing in their Azure deployment to ensure the firewall service performance meets your expectations.
3939

4040
## Downtime
4141

0 commit comments

Comments
 (0)