Skip to content

Commit a37087e

Browse files
authored
Merge pull request #106930 from acasillas13/patch-2
Change "IMPORTANT NOTE" regarding SNAT
2 parents ab34b0c + 912f305 commit a37087e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/private-link/inspect-traffic-with-azure-firewall.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Azure Firewall filters traffic using either:
3535
* [FQDN in application rules](../firewall/features.md#application-fqdn-filtering-rules) for HTTP, HTTPS, and MSSQL.
3636

3737
> [!IMPORTANT]
38-
> The use of application rules over network rules is recommended when inspecting traffic destined to private endpoints in order to maintain flow symmetry. If network rules are used, or an NVA is used instead of Azure Firewall, SNAT must be configured for traffic destined to private endpoints.
38+
> The use of application rules over network rules is recommended when inspecting traffic destined to private endpoints in order to maintain flow symmetry. If network rules are used, or an NVA is used instead of Azure Firewall, SNAT must be configured for traffic destined to private endpoints in order to maintain flow symmetry.
3939
4040
> [!NOTE]
4141
> SQL FQDN filtering is supported in [proxy-mode](/azure/azure-sql/database/connectivity-architecture#connection-policy) only (port 1433). **Proxy** mode can result in more latency compared to *redirect*. If you want to continue using redirect mode, which is the default for clients connecting within Azure, you can filter access using FQDN in firewall network rules.

0 commit comments

Comments
 (0)