Skip to content

Commit 586e969

Browse files
Merge pull request #221159 from aimee-littleton/patch-116
hub and spoke update
2 parents 649bc79 + 6aaeee9 commit 586e969

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/virtual-network/nat-gateway/nat-overview.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -86,6 +86,8 @@ Virtual appliance UDR / ExpressRoute >> NAT gateway >> Instance-level public IP
8686

8787
* NAT gateway can’t be associated to an IPv6 public IP address or IPv6 public IP prefix. It can be associated to a dual stack subnet, but will only be able to direct outbound traffic with an IPv4 address.
8888

89+
* NAT gateway can be used to provide outbound connectivity in a hub and spoke model when associated with Azure Firewall. NAT gateway can be associated to an Azure Firewall subnet in a hub virtual network and provide outbound connectivity from spoke virtual networks peered to the hub. To learn more, see [Azure Firewall integration with NAT gateway](/azure/firewall/integrate-with-nat-gateway).
90+
8991
### Availability zones
9092

9193
* A NAT gateway can be created in a specific availability zone or placed in 'no zone'.

0 commit comments

Comments
 (0)