You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/firewall/overview.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.service: firewall
7
7
services: firewall
8
8
ms.topic: overview
9
9
ms.custom: mvc, contperf-fy21q1
10
-
ms.date: 01/20/2022
10
+
ms.date: 02/17/2022
11
11
12
12
# Customer intent: As an administrator, I want to evaluate Azure Firewall so I can determine if I want to use it.
13
13
---
@@ -118,7 +118,8 @@ Untrusted customer signed certificates|Customer signed certificates are not trus
118
118
|Certificate Propagation|After a CA certificate is applied on the firewall, it may take between 5-10 minutes for the certificate to take effect.|A fix is being investigated.|
119
119
|TLS 1.3 support|TLS 1.3 is partially supported. The TLS tunnel from client to the firewall is based on TLS 1.2, and from the firewall to the external Web server is based on TLS 1.3.|Updates are being investigated.|
120
120
|KeyVault Private Endpoint|KeyVault supports Private Endpoint access to limit its network exposure. Trusted Azure Services can bypass this limitation if an exception is configured as described in the [KeyVault documentation](../key-vault/general/overview-vnet-service-endpoints.md#trusted-services). Azure Firewall is not currently listed as a trusted service and can't access the Key Vault.|A fix is being investigated.|
121
-
|IDPS Bypass list|IDPS Bypass list doesn't support IP Groups.|A fix is being investigated.|
121
+
|IDPS Bypass list|If you enable IDPS (either ‘Alert’ or ‘Alert and Deny’ mode) and actively delete one or more existing rules in IDPS Bypass list, you may be subject to packet loss which is correlated to the deleted rules source/destination IP addresses. |A fix is being investigated.<br><br>You may respond to this issue by taking one of the following actions:<br><br>- Do a start/stop procedure as explained [here](firewall-faq.yml#how-can-i-stop-and-start-azure-firewall).<br>- Open a support ticket and we will re-image your effected firewall virtual machines.
0 commit comments