Skip to content

Commit a13a227

Browse files
Revise NAT Gateway region support and connection notes
Updated the list of regions that don't support StandardV2 NAT Gateway and clarified the impact on existing outbound connections.
1 parent edc8090 commit a13a227

1 file changed

Lines changed: 7 additions & 3 deletions

File tree

articles/nat-gateway/nat-gateway-v2-migrate.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -38,15 +38,19 @@ Before you migrate to StandardV2 NAT gateway, make sure that your specific scena
3838
* Azure Kubernetes Service (AKS) managed NAT gateway doesn't support StandardV2 NAT Gateway deployment. To use a StandardV2 NAT gateway with AKS, StandardV2 NAT Gateway must be deployed as user-assigned.
3939
* StandardV2 NAT Gateway and Basic SKU Load balancer or Basic SKU public IPs aren't supported.
4040
* StandardV2 NAT Gateway doesn't support the use of custom public IPs (BYOIP).
41-
* The following regions don't support StandardV2 NAT Gateway:
41+
* The following regions don't support StandardV2 NAT Gateway and StandardV2 public IPs:
42+
* Brazil Southeast
4243
* Canada East
4344
* Central India
4445
* Chile Central
4546
* Indonesia Central
4647
* Israel Northwest
4748
* Malaysia West
4849
* Qatar Central
49-
* UAE Central
50+
* Sweden South
51+
* UAE Central
52+
* West Central US
53+
* West India
5054

5155
## Known issues
5256

@@ -67,7 +71,7 @@ Before you migrate to StandardV2 NAT gateway, make sure that your specific scena
6771

6872
* Attaching a StandardV2 NAT Gateway to an empty subnet created before April 2025 without any virtual machines may cause the virtual network to go into a failed state. To return the virtual network to a successful state, remove StandardV2 NAT Gateway, create and add a virtual machine to the subnet and then reattach the StandardV2 NAT Gateway.
6973

70-
* Long running outbound connections using a Load balancer or an instance-level public IP on a VM instance may be disrupted by attaching a Standard SKU or StandardV2 NAT gateway to the subnet. New connections use the NAT gateway.
74+
* Existing outbound connections using a Load balancer or an instance-level public IP on a VM instance may be disrupted by attaching a Standard SKU or StandardV2 NAT gateway to the subnet. New connections use the NAT gateway.
7175

7276
## Guidance for manual migration
7377

0 commit comments

Comments
 (0)