Skip to content

Commit 67e4a0d

Browse files
committed
Clarify article applies to network rules only
1 parent 0e12e2c commit 67e4a0d

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

articles/firewall/snat-private-range.md

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

1212
# Azure Firewall SNAT private IP address ranges
1313

14-
Azure Firewall doesn’t SNAT when the destination IP address is in a private IP address range per [IANA RFC 1918](https://tools.ietf.org/html/rfc1918).
14+
Azure Firewall doesn't SNAT using Network rules when the destination IP address is in a private IP address range per [IANA RFC 1918](https://tools.ietf.org/html/rfc1918).
15+
16+
Application rules are always applied regardless of the destination IP address.
1517

1618
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.
1719

@@ -36,7 +38,7 @@ To configure an existing firewall, use the following Azure PowerShell commands:
3638

3739
```azurepowershell
3840
$azfw = Get-AzFirewall -ResourceGroupName "Firewall Resource Group name"
39-
$azfw.PrivateRange = @(IANAPrivateRanges”,“IPRange1”, “IPRange2)
41+
$azfw.PrivateRange = @("IANAPrivateRanges","IPRange1", "IPRange2")
4042
Set-AzFirewall -AzureFirewall $azfw
4143
```
4244

0 commit comments

Comments
 (0)