Merge pull request #314815 from aimee-littleton/patch-769023

Update limitations for StandardV2 NAT Gateway

Author: prmerger-automator[bot]

articles/nat-gateway/faq.yml

@@ -275,7 +275,7 @@ sections:
       
       - question: Can I use a NAT gateway with Azure Kubernetes Service? 
         answer: |
-          Yes. StandardV2 and Standard NAT Gateway can be deployed with either a Managed NAT Gateway or user-assigned NAT Gateway. StandardV2 NAT Gateway can only be used as a user-assigned NAT Gateway. For more information about NAT gateway integration with Azure Kubernetes Service, see [Managed NAT Gateway](/azure/aks/nat-gateway).
+          Yes. StandardV2 and Standard NAT Gateway can be deployed with either a Managed NAT Gateway or user-assigned NAT Gateway. For more information about NAT gateway integration with Azure Kubernetes Service, see [Managed NAT Gateway](/azure/aks/nat-gateway).
 
       - question: When is NAT gateway used to connect from my AKS cluster to the AKS API server?
         answer: |

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

@@ -35,20 +35,16 @@ We recommend the following pre-migration steps to prepare for the migration.
 Before you migrate to StandardV2 NAT gateway, make sure that your specific scenario is supported. Review the following unsupported scenarios and [known issues](#known-issues) with StandardV2 NAT gateway.  
 
 * StandardV2 NAT Gateway must be used with StandardV2 SKU public IPs. Standard SKU public IPs aren't supported.
-* 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.
 * StandardV2 NAT Gateway and Basic SKU Load balancer or Basic SKU public IPs aren't supported.
 * StandardV2 NAT Gateway doesn't support the use of custom public IPs (BYOIP).
 * The following regions don't support StandardV2 NAT Gateway and StandardV2 public IPs:
-  * 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
 

articles/nat-gateway/nat-overview.md

@@ -48,19 +48,15 @@ To learn more about how to deploy StandardV2 NAT Gateway, see [Create a Standard
 * 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 
     * Azure Container Instances 

articles/nat-gateway/nat-sku.md

@@ -69,12 +69,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:
-    * Brazil Southeast
 
     * Canada East  
 
-    * Central India  
-
     * Chile Central  
 
     * Indonesia Central  
@@ -86,17 +83,13 @@ StandardV2 NAT Gateway supports flow logs through Azure Monitor. Flow logs provi
     * 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).
 
-* 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 
     * Azure Container Instances 

articles/nat-gateway/quickstart-create-nat-gateway-v2.md

@@ -15,9 +15,6 @@ ms.custom: template-quickstart, FY23 content-maintenance, linux-related-content
 
 In this quickstart, learn how to create a Standard V2 Azure NAT Gateway by using the Azure portal, and PowerShell. The NAT Gateway service provides scalable outbound connectivity for virtual machines in Azure.
 
-> [!NOTE]
-> Terraform is currently unavailable. Use the Azure portal, CLI, or Azure PowerShell to create a Standard V2 NAT Gateway.
-
 ## Prerequisites
 
 ### [Portal](#tab/portal)