Azure NAT Gateway
Product
A fully managed network address translation service that gives all instances in a subnet private outbound internet access.
Opis
Azure NAT Gateway is a fully managed, highly resilient network address translation service. It lets all instances in a subnet make outbound connections to the internet while staying private. It does not allow unsolicited inbound connections. Only responses to outbound connections pass through.
A gateway is attached to one or more subnets and to public IP addresses or prefixes, and no routing changes are needed. SNAT ports are allocated dynamically, which lowers the risk of port exhaustion. TCP, UDP and ICMP echo are supported. There are two SKUs: Standard, which is zonal, and StandardV2, which is zone-redundant and supports IPv6. A subnet can have only one NAT gateway, and it takes precedence over load balancer outbound rules and other outbound methods such as Azure Firewall for new connections.
Typical uses are outbound access for virtual machines without public IPs, for back-end pools behind an internal load balancer, for App Service with virtual network integration and for hub-and-spoke designs. The page states that since March 31, 2026, new virtual networks use private subnets by default, so default outbound access is not provided and an explicit method such as NAT Gateway is needed.
| Typ | Product |
|---|---|
| Znane także jako | NAT Gateway |
| Dokumentacja | learn.microsoft.com/en-us/azure/nat-gateway/nat-overview |
Part of
- Microsoft Azure · Platform
Developed by
- Microsoft · Organization
Is a
- Microsoft tool · Category
- Cloud platform · Category
Related to
- Azure Virtual Network · Product
- Azure Load Balancer · Product
- Azure Firewall · Product
- Azure App Service · Product
- Azure Virtual Machines · Product
Latest update
Generally Available: Managed StandardV2 NAT Gateway for AKS
AKS will now provision and manage a StandardV2 NAT Gateway
for clusters using an AKS-managed virtual network.
StandardV2 is now the default managed NAT Gateway SKU for
new clusters in supported regions when using the managedNATGateway outbound
type. StandardV2 NAT Gateway provides zone redundancy by default, higher
bandwidth and throughput, and IPv6 support.
Existing AKS clusters can migrate from a managed Standard
NAT Gateway or load balancer to a managed StandardV2 NAT Gateway.
Learn more.
General Availability: October 2026
Older updates (1)
Generally Available: NAT64 on StandardV2 NAT Gateway
StandardV2 NAT Gateway now supports NAT64, enabling IPv6
workloads to communicate with IPv4-only internet destinations by translating synthesized
outbound IPv6 traffic into IPv4 traffic. NAT64 relies on a DNS64-capable
resolver to synthesize IPv6 addresses by embedding the IPv4 address within the NAT64
Well-Known Prefix 64:ff9b::/96 – so client traffic is naturally addressed to
NAT64 for translation.
Learn
more.
General Availability: July 2026
Summaries of official Microsoft release information, checked daily.
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Eksperci i firmy w tym temacie
Nikt jeszcze nie wskazał tego tematu. Dodaj go do swojego profilu.
Sources
- Documentation: learn.microsoft.com/en-us/azure/nat-gateway/nat-overview
Maintained by Mirko Peters (Microsoft MVP) · Last updated: