Skip to content

Commit 003cae6

Browse files
committed
add IDPS private address range feature
1 parent 7737c38 commit 003cae6

File tree

2 files changed

+8
-2
lines changed

2 files changed

+8
-2
lines changed

articles/firewall/firewall-preview.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: firewall
55
author: vhorne
66
ms.service: firewall
77
ms.topic: conceptual
8-
ms.date: 03/04/2022
8+
ms.date: 05/25/2022
99
ms.author: victorh
1010
---
1111

@@ -61,7 +61,7 @@ Unregister-AzProviderFeature -FeatureName AFWEnableNetworkRuleNameLogging -Provi
6161

6262
As more applications move to the cloud, the performance of the network elements can become a bottleneck. As the central piece of any network design, the firewall needs to support all the workloads. The Azure Firewall Premium performance boost feature allows more scalability for these deployments.
6363

64-
This feature significantly increases the throughput of Azure Firewall Premium. For more details, see [Azure Firewall performance](firewall-performance.md).
64+
This feature significantly increases the throughput of Azure Firewall Premium. For more information, see [Azure Firewall performance](firewall-performance.md).
6565

6666
To enable the Azure Firewall Premium Performance boost feature, run the following commands in Azure PowerShell. Stop and start the firewall for the feature to take effect immediately. Otherwise, the firewall/s is updated with the feature within several days.
6767

@@ -82,6 +82,12 @@ Run the following Azure PowerShell command to turn off this feature:
8282
Unregister-AzProviderFeature -FeatureName AFWEnableAccelnet -ProviderNamespace Microsoft.Network
8383
```
8484

85+
### IDPS Private IP ranges (preview)
86+
87+
In Azure Firewall Premium IDPS, private IP address ranges are used to identify if traffic is inbound, outbound, or internal (East-West). Each signature is applied on specific traffic direction, as indicated in the signature rules table. By default, only ranges defined by IANA RFC 1918 are considered private IP addresses. So traffic sent from a private IP address range to a private IP address range is considered internal. To modify your private IP addresses, you can now easily edit, remove, or add ranges as needed.
88+
89+
:::image type="content" source="media/firewall-preview/idps-private-ip.png" alt-text="Screenshot showing I D P S private IP address ranges.":::
90+
8591
## Next steps
8692

8793
To learn more about Azure Firewall, see [What is Azure Firewall?](overview.md).
73.5 KB
Loading

0 commit comments

Comments
 (0)