Skip to content

Commit c12b261

Browse files
committed
tech feedback
1 parent 7c9ce3e commit c12b261

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/firewall/snat-private-range.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,15 +5,15 @@ services: firewall
55
author: vhorne
66
ms.service: firewall
77
ms.topic: article
8-
ms.date: 03/16/2020
8+
ms.date: 03/20/2020
99
ms.author: victorh
1010
---
1111

1212
# Azure Firewall SNAT private IP address ranges
1313

14-
Azure Firewall doesn't SNAT with Network rules when the destination IP address is in a private IP address range per [IANA RFC 1918](https://tools.ietf.org/html/rfc1918). Application rules are always applied regardless of the destination IP address.
14+
Azure Firewall doesn't SNAT with Network rules when the destination IP address is in a private IP address range per [IANA RFC 1918](https://tools.ietf.org/html/rfc1918). Application rules are always applied using a [transparent proxy](https://wikipedia.org/wiki/Proxy_server#Transparent_proxy) regardless of the destination IP address.
1515

16-
If your organization uses a public IP address range for private networks, Azure Firewall will SNAT the traffic to one of the firewall private IP addresses in AzureFirewallSubnet. However, you can configure Azure Firewall to **not** SNAT your public IP address range.
16+
If your organization uses a public IP address range for private networks, Azure Firewall SNATs the traffic to one of the firewall private IP addresses in AzureFirewallSubnet. However, you can configure Azure Firewall to **not** SNAT your public IP address range.
1717

1818
## Configure SNAT private IP address ranges
1919

0 commit comments

Comments
 (0)