Skip to content

Commit d3f7e5c

Browse files
Merge pull request #293904 from vhorne/fw-nat-gw
Freshness review - my last PR!
2 parents c127bd8 + d574920 commit d3f7e5c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/firewall/integrate-with-nat-gateway.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: firewall
55
author: vhorne
66
ms.service: azure-firewall
77
ms.topic: how-to
8-
ms.date: 10/25/2023
8+
ms.date: 01/31/2025
99
ms.author: victorh
1010
ms.custom: devx-track-azurepowershell, devx-track-azurecli
1111
---
@@ -23,9 +23,9 @@ When a NAT gateway resource is associated with an Azure Firewall subnet, all out
2323
There’s no double NAT with this architecture. Azure Firewall instances send the traffic to NAT gateway using their private IP address rather than Azure Firewall public IP address.
2424

2525
> [!NOTE]
26-
> Deploying NAT gateway with a [zone redundant firewall](deploy-availability-zone-powershell.md) is not recommended deployment option, as a single instance of NAT gateway does not support zonal redundant deployment at this time.
26+
> Deploying NAT gateway with a [zone redundant firewall](deploy-availability-zone-powershell.md) isn't recommended deployment option, as a single instance of NAT gateway doesn't support zonal redundant deployment at this time.
2727
>
28-
> In addition, Azure NAT Gateway integration is not currently supported in secured virtual hub network (vWAN) architectures. You must deploy using a hub virtual network architecture. For detailed guidance on integrating NAT gateway with Azure Firewall in a hub and spoke network architecture refer to the [NAT gateway and Azure Firewall integration tutorial](../virtual-network/nat-gateway/tutorial-hub-spoke-nat-firewall.md). For more information about Azure Firewall architecture options, see [What are the Azure Firewall Manager architecture options?](../firewall-manager/vhubs-and-vnets.md).
28+
> In addition, Azure NAT Gateway integration isn't currently supported in secured virtual hub network (vWAN) architectures. You must deploy using a hub virtual network architecture. For detailed guidance on integrating NAT gateway with Azure Firewall in a hub and spoke network architecture, refer to the [NAT gateway and Azure Firewall integration tutorial](../virtual-network/nat-gateway/tutorial-hub-spoke-nat-firewall.md). For more information about Azure Firewall architecture options, see [What are the Azure Firewall Manager architecture options?](../firewall-manager/vhubs-and-vnets.md).
2929
3030
## Associate a NAT gateway with an Azure Firewall subnet - Azure PowerShell
3131

@@ -67,6 +67,6 @@ az network vnet subnet update --name AzureFirewallSubnet --vnet-name nat-vnet --
6767

6868
## Next steps
6969

70-
- For more information, see [Scale Azure Firewall SNAT ports with NAT Gateway for large workloads](https://azure.microsoft.com/blog/scale-azure-firewall-snat-ports-with-nat-gateway-for-large-workloads/).
70+
- [Scale Azure Firewall SNAT ports with NAT Gateway for large workloads](https://azure.microsoft.com/blog/scale-azure-firewall-snat-ports-with-nat-gateway-for-large-workloads/).
7171
- [Design virtual networks with NAT gateway](../virtual-network/nat-gateway/nat-gateway-resource.md)
7272
- [Integrate NAT gateway with Azure Firewall in a hub and spoke network](../virtual-network/nat-gateway/tutorial-hub-spoke-nat-firewall.md)

0 commit comments

Comments
 (0)