Merge pull request #310461 from MicrosoftDocs/main

learn-build-service-prod[bot] · web-flow · commit 589fc776d50b · 2026-01-14T06:06:53.000Z
Auto Publish – main to live - 2026-01-14 06:00 UTC
diff --git a/articles/api-center/self-host-api-center-portal.md b/articles/api-center/self-host-api-center-portal.md
@@ -4,7 +4,7 @@ description: How to self-host the API Center portal, a customer-managed website
 author: dlepow
 ms.service: azure-api-center
 ms.topic: how-to
-ms.date: 03/04/2025
+ms.date: 01/13/2026
 ms.author: danlep 
 ms.custom: 
 # Customer intent: As an API program manager, I want to self-host a portal for developers and other API stakeholders in my organization to discover the APIs in my organization's API center.
@@ -65,20 +65,20 @@ Follow these steps to build and test the API Center portal locally.
     ```bash
     git checkout main
     ```  
-1. To configure the service, copy or rename the `public/config.example` file to `public/config.json`.
-1. Then edit the `public/config.json` file to point to your service. Update the values in the file as follows:
-    1. Replace `<service name>` and `<location>` with the name of your API center and the location where it's deployed
+1. To configure the service, copy or rename the `config.example.json` file to `config.json`.
+1. Then edit the `config.json` file to point to your service. Update the values in the file as follows:
+    1. Replace `<service name>` and `<region>` with the name of your API center and the location where it's deployed
     1. Replace `<client ID>` and `<tenant ID>` with the **Application (client) ID** and **Directory (tenant) ID** of the app registration you created in the previous section.
     1. Update the value of `title` to a name that you want to appear in the top bar of the portal.
 
     ```json
     {
-      "dataApiHostName": "<service name>.data.<location>.azure-apicenter.ms/workspaces/default",
+      "dataApiHostName": "<service name>.data.<region>.azure-apicenter.ms",
       "title": "API portal",
       "authentication": {
           "clientId": "<client ID>",
           "tenantId": "<tenant ID>",
-          "scopes": ["https://azure-apicenter.net/user_impersonation"],
+          "scopes": ["https://azure-apicenter.net/Data.Read.All"],
           "authority": "https://login.microsoftonline.com/"
       }
     }
diff --git a/articles/artifact-signing/how-to-signing-integrations.md b/articles/artifact-signing/how-to-signing-integrations.md
@@ -146,21 +146,29 @@ To sign by using Artifact Signing, you need to provide the details of your Artif
      "CorrelationId": "<Optional CorrelationId value>"
    }
    ```
+  <sup>1</sup> The optional `"CorrelationId"` field is an opaque string value that you can provide to correlate sign requests with your own workflows, such as build identifiers or machine names.
 
   > [!IMPORTANT]
   > The `"Endpoint"` URI value must match the region where you created your Artifact Signing account **and** the certificate profile. Use one of the region-specific URIs in the table below. A region/endpoint mismatch commonly causes a 403 Forbidden error and an internal `SignerSign()` failure during signing.
 
    | Region       | Region class fields  | Endpoint URI value  |
    |--------------|-----------|------------|
+   | Brazil South | BrazilSouth | `https://brs.codesigning.azure.net` |
+   | Central US  | CentralUS  | `https://cus.codesigning.azure.net` |
    | East US  | EastUS  | `https://eus.codesigning.azure.net` |
-   | West US3 <sup>[1]</sup>   | WestUS3  | `https://wus3.codesigning.azure.net` |
+   | Japan East | JapanEast | `https://jpe.codesigning.azure.net` |
+   | Korea Central | KoreaCentral | `https://krc.codesigning.azure.net` |
+   | North Central US  | NorthCentralUS  | `https://ncus.codesigning.azure.net` |
+   | North Europe   | NorthEurope   | `https://neu.codesigning.azure.net`   |
+   | Poland Central | PolandCentral  | `https://plc.codesigning.azure.net` |
+   | South Central US  | SouthCentralUS  | `https://scus.codesigning.azure.net` |
+   | Switzerland North  | SwitzerlandNorth  | `https://swn.codesigning.azure.net` |
    | West Central US  | WestCentralUS  | `https://wcus.codesigning.azure.net` |
+   | West Europe  | WestEurope   | `https://weu.codesigning.azure.net`   |
+   | West US  | WestUS  | `https://wus.codesigning.azure.net` |
    | West US 2   | WestUS2   | `https://wus2.codesigning.azure.net` |
-   | North Europe   | NorthEurope   | `https://neu.codesigning.azure.net`   |
-   | West Europe   | WestEurope   | `https://weu.codesigning.azure.net`  |
-
-   <sup>1</sup> The optional `"CorrelationId"` field is an opaque string value that you can provide to correlate sign requests with your own workflows, such as build identifiers or machine names.
-
+   | West US 3   | WestUS3   | `https://wus3.codesigning.azure.net` |
+   
 ### Authentication
 
 This Task performs authentication using [DefaultAzureCredential](/dotnet/api/azure.identity.defaultazurecredential), which attempts a series of authentication methods in order. If one method fails, it attempts the next one until authentication is successful.
diff --git a/articles/migrate/migrate-support-matrix-vmware-migration.md b/articles/migrate/migrate-support-matrix-vmware-migration.md
@@ -50,7 +50,7 @@ This section summarizes requirements for agentless VMware vSphere VM migration t
 The VMware vSphere hypervisor requirements are:
 - **VMware vCenter Server** - Version 8.0 & subsequent updates in this version, Version 7.0, 6.7 or 6.5.
 - **VMware vSphere ESXi host** - Version 8.0 & subsequent updates in this version, Version 7.0, 6.7 or 6.5.
-- **Multiple vCenter Servers** - A single appliance can connect to up to 10 vCenter Servers.
+- **Multiple vCenter Servers** - A single appliance can connect to up to 10 vCenter Servers. Once a vCenter is added to Azure Migrate appliance using IP or FQDN, it cannot be edited/deleted.
 - **vCenter Server permissions** - The VMware account used to access the vCenter server from the Azure Migrate appliance must have the following permissions assigned at all required levels - datacenter, cluster, host, VM, and datastore. Ensure permissions are applied at each level to avoid replication errors.
 
     **Privilege Name in the vSphere Client** | **The purpose for the privilege** | **Required On** | **Privilege Name in the API**
diff --git a/articles/nat-gateway/faq.yml b/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: |
diff --git a/articles/nat-gateway/manage-nat-gateway-v2.md b/articles/nat-gateway/manage-nat-gateway-v2.md
@@ -15,10 +15,6 @@ ms.custom: template-how-to, devx-track-azurecli, devx-track-azurepowershell
 
 Learn how to create and remove a NAT gateway resource from a virtual network subnet. A NAT gateway enables outbound connectivity for resources in an Azure Virtual Network. You can change the public IP addresses and public IP address prefixes associated with the NAT gateway changed after deployment.
 
-> [!IMPORTANT]
-> Standard V2 SKU Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
-
 This article explains how to manage the following aspects of NAT gateway:
 
 - Create a NAT gateway and associate it with an existing subnet.
diff --git a/articles/nat-gateway/monitor-nat-gateway-flow-logs.md b/articles/nat-gateway/monitor-nat-gateway-flow-logs.md
@@ -20,10 +20,6 @@ In this article, you learn how to set up, monitor, and troubleshoot with Azure S
 - An Azure StandardV2 NAT Gateway resource. To learn how to create a StandardV2 NAT Gateway resource, see [Quickstart: Create a StandardV2 NAT Gateway](./quickstart-create-nat-gateway-v2.md).
 - An Azure Monitor Log Analytics workspace. To learn how to create a Log Analytics workspace, see [Quickstart: Create a Log Analytics workspace](/azure/azure-monitor/logs/quick-create-workspace).
 
-> [!IMPORTANT]
-> StandardV2 Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability. 
-
 ## Enable diagnostic settings to collect NAT gateway flow logs
 
 In this section, you learn how to set up StandardV2 NAT gateway flow logs and send it to the recommended destination – Log Analytics workspace, which enables you to manage data retention and access. To learn more about the other destinations, including Azure Storage account and Azure Event Hubs, see [Diagnostic settings in Azure Monitor - Azure Monitor | Microsoft Learn.](/azure/azure-monitor/platform/diagnostic-settings)
diff --git a/articles/nat-gateway/nat-gateway-design.md b/articles/nat-gateway/nat-gateway-design.md
@@ -14,10 +14,6 @@ ms.date: 11/04/2025
 
 Review this article to familiarize yourself with considerations for designing virtual networks with NAT gateway.
 
-> [!IMPORTANT]
-> Standard V2 SKU Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
-
 ## Connect to the internet with a NAT gateway
 
 NAT Gateway is recommended for all production workloads where you need to connect to a public endpoint over the internet. Outbound connectivity takes place right away upon deployment of a NAT gateway with a subnet and at least one public IP address. No routing configurations are required to start connecting outbound with the NAT gateway. The NAT gateway becomes the subnet’s default route to the internet.
diff --git a/articles/nat-gateway/nat-gateway-flow-logs.md b/articles/nat-gateway/nat-gateway-flow-logs.md
@@ -15,10 +15,6 @@ ms.custom:
 
 NAT Gateway Flow Logs provide IP information on the traffic flowing through your StandardV2 NAT gateway. Logs are captured through Azure Monitor resource log category `NatGatewayFlowLogsV1`, which you enable through Diagnostic Settings on your StandardV2 NAT gateway resource.
 
-> [!IMPORTANT]
-> Standard V2 SKU Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
-
 ## Why use flow logs?
 
 Flow logs provide visibility to the traffic flowing through your NAT gateway, which is critical to:
diff --git a/articles/nat-gateway/nat-gateway-resource.md b/articles/nat-gateway/nat-gateway-resource.md
@@ -14,10 +14,6 @@ ms.author: alittleton
 
 This article describes the key components of the NAT gateway resource that enable it to provide highly secure, scalable, and resilient outbound connectivity. NAT Gateway can be configured in your subscription through supported clients. These clients include Azure portal, Azure CLI, Azure PowerShell, Resource Manager templates, or appropriate alternatives.
 
-> [!IMPORTANT]
-> Standard V2 SKU Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
-
 ## NAT Gateway SKUs
 NAT Gateway is available in two SKUs: StandardV2 and Standard. 
 
diff --git a/articles/nat-gateway/nat-metrics.md b/articles/nat-gateway/nat-metrics.md
@@ -13,11 +13,7 @@ ms.author: alittleton
 
 This article provides an overview of all NAT gateway metrics and diagnostic capabilities. This article provides general guidance on how to use metrics and alerts to monitor, manage, and [troubleshoot](troubleshoot-nat.md) your NAT gateway resource. 
 
-All metrics are the same for Standard and StandardV2 NAT Gateway.  
-
-> [!IMPORTANT]
-> Standard V2 SKU Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.  
+All metrics are the same for Standard and StandardV2 NAT Gateway.
 
 Azure NAT Gateway provides the following diagnostic capabilities:  
 
diff --git a/articles/nat-gateway/nat-overview.md b/articles/nat-gateway/nat-overview.md
@@ -19,11 +19,7 @@ ms.customs: references_regions
 
 Azure NAT Gateway is a fully managed and highly resilient Network Address Translation (NAT) service. You can use Azure NAT Gateway to let all instances in a subnet connect outbound to the internet while remaining fully private. Unsolicited inbound connections from the internet aren't permitted through a NAT Gateway. Only packets arriving as response packets to an outbound connection can pass through a NAT Gateway.
 
-NAT Gateway dynamically allocates SNAT ports to automatically scale outbound connectivity and minimize the risk of SNAT port exhaustion. 
-
-> [!IMPORTANT]
-> Standard V2 SKU Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability. 
+NAT Gateway dynamically allocates SNAT ports to automatically scale outbound connectivity and minimize the risk of SNAT port exhaustion.
 
 :::image type="content" source="./media/nat-overview/flow-map.png" alt-text="Figure shows a NAT receiving traffic from internal subnets and directing it to a public IP address." lightbox="./media/nat-overview/flow-map.png":::
 
diff --git a/articles/nat-gateway/nat-sku.md b/articles/nat-gateway/nat-sku.md
@@ -12,10 +12,6 @@ ms.customs: references_regions
 # Azure NAT Gateway SKUs
 Azure Network Address Translation (NAT) Gateway has two stock-keeping units (SKUs). This article provides an overview of these different SKUs and their differences.
 
-> [!IMPORTANT]
-> Standard V2 SKU Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
-
 ## SKU comparison
 Azure Network Address Translation (NAT) Gateway has two stock-keeping units (SKUs) - Standard and StandardV2. To compare and understand the differences between Standard and StandardV2 SKU, see the following table.
 
diff --git a/articles/nat-gateway/quickstart-create-nat-gateway-v2-templates.md b/articles/nat-gateway/quickstart-create-nat-gateway-v2-templates.md
@@ -13,10 +13,6 @@ ms.custom: subject-armqs, mode-arm, devx-track-arm-template
 
 Get started with NAT Gateway V2 by using an Azure Resource Manager template (ARM template) or Bicep template. The templates deploy a NAT gateway, virtual network, subnet, and Ubuntu virtual machine for testing NAT gateway functionality. The NAT gateway is assigned to a subnet of the virtual network.
 
-> [!IMPORTANT]
-> Standard V2 SKU Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
-
 [!INCLUDE [About Azure Resource Manager](~/reusable-content/ce-skilling/azure/includes/resource-manager-quickstart-introduction.md)]
 
 If your environment meets the prerequisites and you're familiar with using ARM templates, select the **Deploy to Azure** button. The template opens in the Azure portal.
diff --git a/articles/nat-gateway/quickstart-create-nat-gateway-v2.md b/articles/nat-gateway/quickstart-create-nat-gateway-v2.md
@@ -15,12 +15,8 @@ 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.
 
-> [!IMPORTANT]
-> Standard V2 SKU Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
-
 > [!NOTE]
-> Terraform is currently unavailable. Use the Azure preview portal, CLI, or Azure PowerShell to create a Standard V2 NAT Gateway.
+> Terraform is currently unavailable. Use the Azure portal, CLI, or Azure PowerShell to create a Standard V2 NAT Gateway.
 
 ## Prerequisites
 
diff --git a/articles/nat-gateway/quickstart-create-nat-gateway.md b/articles/nat-gateway/quickstart-create-nat-gateway.md
@@ -15,10 +15,6 @@ ms.custom: template-quickstart, FY23 content-maintenance, linux-related-content
 
 In this quickstart, learn how to create a NAT gateway by using the Azure portal, Azure CLI, PowerShell, Bicep, ARM template and Terraform. The NAT Gateway service provides scalable outbound connectivity for virtual machines in Azure.
 
-> [!IMPORTANT]
-> Standard V2 SKU Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
-
 :::image type="content" source="./media/quickstart-create-nat-gateway-portal/nat-gateway-qs-resources.png" alt-text="Diagram of resources created in nat gateway quickstart." lightbox="./media/quickstart-create-nat-gateway-portal/nat-gateway-qs-resources.png":::
 
 ## Prerequisites
diff --git a/articles/nat-gateway/region-move-nat-gateway.md b/articles/nat-gateway/region-move-nat-gateway.md
@@ -13,11 +13,7 @@ ms.custom: template-how-to
 
 # Create and configure NAT gateway after moving resources to another region
 
-In this article, you'll learn how to set up a NAT gateway after moving resources to a different region. You might want to move resources to a new Azure region that better suits your customers' location or meets your organization's needs and policies. 
-
-> [!IMPORTANT]
-> Standard V2 SKU Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability. 
+In this article, you'll learn how to set up a NAT gateway after moving resources to a different region. You might want to move resources to a new Azure region that better suits your customers' location or meets your organization's needs and policies.
 
 > [!NOTE]
 > NAT gateway instances can't directly be moved from one region to another. A workaround is to use Azure Resource Mover to move all the resources associated with the existing NAT gateway to the new region. You then create a new instance of NAT gateway in the new region and then associate the moved resources with the new instance. After the new NAT gateway is functional in the new region, you delete the old instance in the previous region.  
diff --git a/articles/nat-gateway/troubleshoot-nat-and-azure-services.md b/articles/nat-gateway/troubleshoot-nat-and-azure-services.md
@@ -22,10 +22,6 @@ This article provides guidance on how to troubleshoot connectivity issues when u
 
 * [Azure Databricks](#azure-databricks)
 
-> [!IMPORTANT]
-> Standard V2 SKU Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
-
 ## Known limitations with StandardV2 NAT Gateway and VNet injection scenarios
 
 * StandardV2 NAT Gateway doesn't support and can't be attached to delegated subnets for the following services: 
diff --git a/articles/nat-gateway/troubleshoot-nat-connectivity.md b/articles/nat-gateway/troubleshoot-nat-connectivity.md
@@ -16,10 +16,6 @@ ms.author: alittleton
 
 This article provides guidance on how to troubleshoot and resolve common outbound connectivity issues with your NAT gateway. This article also provides best practices on how to design applications to use outbound connections efficiently.
 
-> [!IMPORTANT]
-> Standard V2 SKU Azure NAT Gateway is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
-
 ## Datapath availability drop on NAT gateway with connection failures
 
 **Scenario**
diff --git a/articles/nat-gateway/troubleshoot-nat.md b/articles/nat-gateway/troubleshoot-nat.md
diff --git a/articles/nat-gateway/tutorial-hub-spoke-nat-firewall.md b/articles/nat-gateway/tutorial-hub-spoke-nat-firewall.md
diff --git a/articles/nat-gateway/tutorial-hub-spoke-route-nat.md b/articles/nat-gateway/tutorial-hub-spoke-route-nat.md
diff --git a/articles/reliability/reliability-nat-gateway.md b/articles/reliability/reliability-nat-gateway.md
diff --git a/articles/storage/files/nfs-root-squash.md b/articles/storage/files/nfs-root-squash.md
diff --git a/includes/backup-azure-agentless-multi-disk-crash-consistent-vm-backup-support-scenarios.md b/includes/backup-azure-agentless-multi-disk-crash-consistent-vm-backup-support-scenarios.md
