Skip to content

Commit a5b69e5

Browse files
committed
Update preview for IDPS and sku upgrade
1 parent 011b2ac commit a5b69e5

File tree

4 files changed

+23
-7
lines changed

4 files changed

+23
-7
lines changed

articles/firewall/firewall-preview.md

Lines changed: 16 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -57,12 +57,6 @@ Run the following Azure PowerShell command to turn off this feature:
5757
Unregister-AzProviderFeature -FeatureName AFWEnableNetworkRuleNameLogging -ProviderNamespace Microsoft.Network
5858
```
5959

60-
### IDPS Private IP ranges (preview)
61-
62-
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.
63-
64-
:::image type="content" source="media/firewall-preview/idps-private-ip.png" alt-text="Screenshot showing I D P S private IP address ranges.":::
65-
6660
### Structured firewall logs (preview)
6761

6862
Today, the following diagnostic log categories are available for Azure Firewall:
@@ -179,6 +173,22 @@ Policy analytics starts monitoring the flows in the DNAT, Network, and Applicati
179173
> [!TIP]
180174
> Policy Analytics has a dependency on both Log Analytics and Azure Firewall resource specific logging. Verify the Firewall is configured appropriately or follow the previous instructions. Be aware that logs take 60 minutes to appear after enabling them for the first time. This is because logs are aggregated in the backend every hour. You can check logs are configured appropriately by running a log analytics query on the resource specific tables such as **AZFWNetworkRuleAggregation**, **AZFWApplicationRuleAggregation**, and **AZFWNatRuleAggregation**.
181175
176+
### Single click upgrade/downgrade (preview)
177+
178+
You can now easily upgrade you existing Firewall Standard SKU to Premium SKU as well as downgrade from Premium to Standard SKU. The process is fully automated and has no service impact (zero service downtime).
179+
180+
In the upgrade process, you can select the policy to be attached to the upgraded Premium SKU. Either by using an existing Premium Policy or by using your existing Standard Policy. You can use your existing Standard policy and let the system automatically duplicate, upgrade to Premium Policy, and then attach it to the newly created Premium Firewall.
181+
182+
This new capability is available through the Azure portal as as shown here, as well as via PowerShell and Terraform simply by changing the sku_tier attribute.
183+
184+
:::image type="content" source="media/premium-features/upgrade.png" alt-text="Screenshot showing SKU upgrade" lightbox="media/premium-features/upgrade.png":::
185+
186+
<SCU Screenshot>
187+
188+
> [!NOTE]
189+
> This new upgrade/downgrade capability will also support the Basic SKU for GA.
190+
191+
182192
## Next steps
183193

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

articles/firewall/premium-features.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: vhorne
55
ms.service: firewall
66
services: firewall
77
ms.topic: conceptual
8-
ms.date: 10/12/2022
8+
ms.date: 11/07/2022
99
ms.author: victorh
1010
ms.custom: references_regions
1111
---
@@ -77,6 +77,12 @@ IDPS allows you to detect attacks in all ports and protocols for non-encrypted t
7777

7878
The IDPS Bypass List allows you to not filter traffic to any of the IP addresses, ranges, and subnets specified in the bypass list.
7979

80+
### IDPS Private IP ranges
81+
82+
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.
83+
84+
:::image type="content" source="media/premium-features/idps-private-ip.png" alt-text="Screenshot showing I D P S private IP address ranges.":::
85+
8086
### IDPS signature rules
8187

8288
IDPS signature rules allow you to:

0 commit comments

Comments
 (0)