Merge pull request #310695 from aimee-littleton/patch-384955

Update NAT Gateway overview with limitations and issues

Author: prmerger-automator[bot]

articles/nat-gateway/faq.yml

@@ -63,7 +63,7 @@ sections:
     questions:
       - question: What is StandardV2 NAT Gateway?
         answer: |
-          StandardV2 NAT Gateway is a new SKU offering of the Azure NAT Gateway service that is currently in **Public Preview**. StandardV2 NAT Gateway offers zone-redundancy support, enhanced data processing limits, IPv6 support, Flow logs, and increased scalability compared to the original Standard NAT Gateway. For more information, see [NAT Gateway SKUs](nat-sku.md).
+          StandardV2 NAT Gateway is a new SKU offering of the Azure NAT Gateway service. StandardV2 NAT Gateway offers zone-redundancy support, enhanced data processing limits, IPv6 support, Flow logs, and increased scalability compared to the original Standard NAT Gateway. For more information, see [NAT Gateway SKUs](nat-sku.md).
 
       - question: Can I upgrade my existing Standard NAT Gateway to StandardV2 NAT Gateway?
         answer: |
@@ -91,7 +91,7 @@ sections:
 
       - question: Is StandardV2 NAT Gateway available in all public regions?
         answer: |
-          No, StandardV2 NAT Gateway is available in most public regions. StandardV2 NAT Gateway isn't available in: Canada East, Central India, Chile Central, Indonesia Central, Israel Northwest, Malaysia West, Qatar Central, UAE Central.
+          No, StandardV2 NAT Gateway is available in most public regions. To learn more about which regions are not supported yet for StandardV2 NAT Gateway, see [known limitations](./nat-sku.md#known-limitations).
 
   - name: NAT gateway metrics
     questions: 
@@ -120,6 +120,8 @@ sections:
       - question: Are connections disrupted after attaching a NAT gateway to a subnet where a different service is currently used for outbound connectivity?
         answer: |
           No, there's no disruption in connections. Existing connections with the previous outbound service (Load Balancer, Azure Firewall, instance-level public IP addresses) continues to work until those connections close. After a NAT gateway is added to the subnet of the virtual network, all new connections use a NAT gateway for making outbound connections. 
+
+          However, there is a known issue with StandardV2 NAT Gateway and existing connections using a Load balancer, Firewall, or a virtual machine instance level public IP. Existing connections with other outbound connectivity methods will be disrupted after adding StandardV2 NAT Gateway to a subnet. All net new connections will use the StandardV2 NAT Gateway. To learn more see [known issues](./nat-sku.md#known-issues).
      
       - question: Can a NAT gateway public IP connect directly to a private IP address over the internet?
         answer: |

articles/nat-gateway/nat-overview.md

@@ -55,14 +55,18 @@ To learn more on how to deploy StandardV2 NAT Gateway, see [Create a StandardV2
 * Requires StandardV2 SKU public IP addresses or prefixes. Standard SKU public IPs aren't supported with StandardV2 NAT Gateway.
 * Standard SKU NAT Gateway can't be upgraded to StandardV2 NAT Gateway. You must first create StandardV2 SKU NAT Gateway and replace Standard SKU NAT Gateway on your subnet. 
 * The following regions don't support StandardV2 NAT Gateway:
+    * Brazil Southeast
     * Canada East
     * Central India
     * Chile Central
     * Indonesia Central
     * Israel Northwest
     * Malaysia West
     * Qatar Central
+    * Sweden South
     * UAE Central
+    * West Central US
+    * West India
 * Terraform doesn't yet support StandardV2 NAT Gateway and StandardV2 Public IP deployments.
 * StandardV2 NAT Gateway doesn't support and can't be attached to delegated subnets for the following services: 
     * Azure SQL Managed Instance 
@@ -80,7 +84,9 @@ To learn more on how to deploy StandardV2 NAT Gateway, see [Create a StandardV2
 ### Known issues of StandardV2 NAT Gateway
 * IPv6 outbound traffic using Load balancer outbound rules is disrupted when StandardV2 NAT Gateway is associated to a subnet. If you require both IPv4 and IPv6 outbound connectivity, use either Load balancer outbound rules for both IPv4 and IPv6 traffic or use Standard NAT Gateway for IPv4 traffic and Load balancer outbound rules for IPv6 traffic.
 
-* 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. 
+* 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.
+
+* Outbound connections using Load balancer, Azure Firewall, or virtual machine instance level public IPs may be interrupted when adding StandardV2 NAT gateway to a subnet. All net new outbound connections will use the StandardV2 NAT gateway. 
 
 For more information about known issues and limitations of StandardV2 NAT Gateway, see [StandardV2 NAT Gateway known issues and limitations](./nat-sku.md#known-limitations).
 

articles/nat-gateway/nat-sku.md

@@ -72,7 +72,9 @@ StandardV2 NAT Gateway supports flow logs through Azure Monitor. Flow logs provi
 
 * Custom IP prefixes (BYOIP public IPs) aren't supported with StandardV2 NAT Gateway. Only StandardV2 SKU Azure public IPs are supported. 
 
-* The following regions don't support StandardV2 NAT Gateway:  
+* The following regions don't support StandardV2 NAT Gateway:
+    * Brazil Southeast
+      
     * Canada East  
 
     * Central India  
@@ -85,9 +87,15 @@ StandardV2 NAT Gateway supports flow logs through Azure Monitor. Flow logs provi
 
     * Malaysia West  
 
-    * Qatar Central   
+    * Qatar Central
+ 
+    * Sweden South   
 
     * UAE Central
+ 
+    * West Central US
+ 
+    * West India
 
 * StandardV2 NAT Gateway can’t be deployed as a managed NAT Gateway for Azure Kubernetes Service (AKS) workloads. It's only supported when configured as a user-assigned NAT Gateway. For more information, see [Create NAT Gateway for your AKS cluster](/azure/aks/nat-gateway).
 
@@ -109,7 +117,9 @@ StandardV2 NAT Gateway supports flow logs through Azure Monitor. Flow logs provi
 ## Known issues 
 * StandardV2 NAT Gateway disrupts outbound connections made with Load balancer outbound rules for IPv6 traffic only. Standard SKU NAT gateway can be used to provide outbound for IPv4 traffic while Load balancer outbound rules is used for IPv6 outbound traffic. If you see disruption to outbound connectivity for IPv6 outbound traffic with Load balancer outbound rules, remove the StandardV2 NAT Gateway from the subnet or virtual network. Use Load balancer outbound rules to provide outbound connectivity for both IPv4 and IPv6 traffic. Or use Standard SKU NAT Gateway to provide outbound connectivity for IPv4 traffic and Load balancer outbound rules for IPv6 traffic.
 
-* 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. 
+* 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.
+
+* Outbound connections using Load balancer, Azure Firewall, or virtual machine instance level public IPs may be interrupted when adding StandardV2 NAT gateway to a subnet. All net new outbound connections will use the StandardV2 NAT gateway.
 
 ## Standard NAT Gateway features
 

articles/nat-gateway/troubleshoot-nat.md

@@ -53,14 +53,18 @@ Check these settings to enable outbound traffic through a NAT gateway.
 ### StandardV2 NAT gateway availability
 
 StandardV2 NAT Gateway isn't available in the following Azure regions: 
+* Brazil Southeast
 * Canada East
 * Central India
 * Chile Central
 * Indonesia Central
 * Israel Northwest
 * Malaysia West
 * Qatar Central
+* Sweden South
 * UAE Central
+* West Central US
+* West India
 
 ### How to validate connectivity