Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into tsk544780-sfi-bastion

Author: asudbring

.openpublishing.redirection.json

@@ -1,5 +1,20 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/network-watcher/network-watcher-using-open-source-tools.md",
+      "redirect_url": "/previous-versions/azure/network-watcher/network-watcher-using-open-source-tools",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/network-watcher/network-watcher-intrusion-detection-open-source-tools.md",
+      "redirect_url": "/previous-versions/azure/network-watcher/network-watcher-intrusion-detection-open-source-tools",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/frontdoor/migrate-cdn-to-front-door.md",
+      "redirect_url": "/previous-versions/azure/frontdoor/migrate-cdn-to-front-door",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/synapse-analytics/data-explorer/data-explorer-compare.md",
       "redirect_url": "/previous-versions/azure/synapse-analytics/data-explorer/data-explorer-compare",
@@ -6430,6 +6445,11 @@
       "redirect_url": "/azure/iot-hub-device-update/",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/reliability/asm-retirement.md",
+      "redirect_url": "/azure/azure-resource-manager/management/asm-retirement",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/reliability/reliability-azure-container-apps.md",
       "redirect_url": "/azure/reliability/reliability-container-apps",

CODEOWNERS

@@ -2,19 +2,19 @@
 # Each line is a file pattern followed by one or more owners.
 
 # Folder paths in this list have been migrated to new repositories and content can no longer be created for these services in this repo.
-/articles/aks @tynevi @thomps23 @jasonwhowell
-/articles/defender-for-cloud  @tynevi @thomps23 @jasonwhowell
-/articles/attestation  @tynevi @thomps23 @jasonwhowell
-/articles/confidential-ledger  @tynevi @thomps23 @jasonwhowell
-/articles/dedicated-hsm  @tynevi @thomps23 @jasonwhowell
-/articles/key-vault  @tynevi @thomps23 @jasonwhowell
-/articles/payment-hsm  @tynevi @thomps23 @jasonwhowell
-/articles/postgresql @tynevi @thomps23 @jasonwhowell
-/articles/cosmos-db @tynevi @thomps23 @jasonwhowell
-/articles/dms @tynevi @thomps23 @jasonwhowell
-/articles/mariadb @tynevi @thomps23 @jasonwhowell
-/articles/mysql @tynevi @thomps23 @jasonwhowell
-/articles/managed-instance-apache-cassandra @tynevi @thomps23 @jasonwhowell
+/articles/aks @thomps23 @jasonwhowell
+/articles/defender-for-cloud @thomps23 @jasonwhowell
+/articles/attestation @thomps23 @jasonwhowell
+/articles/confidential-ledger @thomps23 @jasonwhowell
+/articles/dedicated-hsm @thomps23 @jasonwhowell
+/articles/key-vault @thomps23 @jasonwhowell
+/articles/payment-hsm @thomps23 @jasonwhowell
+/articles/postgresql @thomps23 @jasonwhowell
+/articles/cosmos-db @thomps23 @jasonwhowell
+/articles/dms @thomps23 @jasonwhowell
+/articles/mariadb @thomps23 @jasonwhowell
+/articles/mysql @thomps23 @jasonwhowell
+/articles/managed-instance-apache-cassandra @thomps23 @jasonwhowell
 /articles/virtual-machines @jasonwhowell @thomps23
 /articles/virtual-machines-scale-sets @jasonwhowell @thomps23
 /articles/container-instances @jasonwhowell @thomps23
@@ -37,3 +37,4 @@
 /articles/quotas @jasonwhowell @thomps23
 /articles/container-registry @jasonwhowell @thomps23
 /articles/kubernetes-fleet @MicrosoftDocs/azure-docs-codeowners
+/articles/reliability @thomps23

articles/active-directory-b2c/add-api-connector.md

@@ -160,7 +160,7 @@ Content-type: application/json
 }
 ```
 
-The exact claims sent to the API depend on the information is provided by the identity provider. 'email' is always sent.
+The exact claims sent to the API depend on the information provided by the identity provider. 'email' is always sent.
 
 ### Expected response types from the web API at this step
 

articles/active-directory-b2c/partner-transmit-security.md

@@ -127,7 +127,7 @@ To integrating Transmit DRS into the B2C sign-in page, follow these steps:
 
 Azure AD B2C can obtain a risk recommendation from Transmit using a [API connector](./add-api-connector.md). Passing this request through an intermediate web API (such as using [Azure Functions](/azure/azure-functions/)) provides more flexibility in your implementation logic. 
 
-Follow these steps to create an Azure function that uses the action token from the frontend application to get a recommendation from the [Transmit DRS endpoint](https://developer.transmitsecurity.com/openapi/risk/recommendations/#operation/getRiskRecommendation).
+Follow these steps to create an Azure function that uses the action token from the frontend application to get a recommendation from the [Transmit DRS endpoint](https://developer.transmitsecurity.com/guides/risk/recommendations#operation/getRiskRecommendation).
 
 1. Create the entry point of your Azure Function, an HTTP-triggered function that processes incoming HTTP requests.
 

articles/active-directory-b2c/service-limits.md

@@ -8,7 +8,7 @@ manager: CelesteDG
 ms.service: azure-active-directory
 
 ms.topic: reference
-ms.date: 08/19/2025
+ms.date: 01/08/2026
 ms.subservice: b2c
 zone_pivot_groups: b2c-policy-type
 
@@ -186,7 +186,7 @@ The following table lists the administrative configuration limits in the Azure A
 
 ## Region specific service limits 
 
-As a protection for our customers, Microsoft places some restrictions on telephony verification for certain region codes. The following table lists the region codes and their corresponding limits.
+As a protection for our customers, Microsoft places some restrictions on telephony verification for certain region codes. The following table lists the region codes and their corresponding limits. These limits apply to both SMS and Voice verification.
 
 | Region Code | Region Name                                    | Limit per tenant per 60 minutes | Limit per tenant per 24 hours            |                         
 |:----------- |:---------------------------------------------- |:------------------------------- | :----------------------------------------|

articles/api-center/includes/api-center-portal-compare-apim-dev-portal.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-center
 ms.topic: include
-ms.date: 03/05/2025
+ms.date: 01/13/2026
 ms.author: danlep
 ms.custom: Include file
 ---
@@ -15,10 +15,10 @@ ms.custom: Include file
 
 The [Azure API Management](../../api-management/api-management-key-concepts.md) and [Azure API Center](../overview.md) services both provide portals for developers to discover and consume APIs:
 
-* The *API Management developer portal* allows users to find managed APIs, learn how to use them, request access, and test them.
-* The *API Center portal* (preview) is a multi-gateway portal where  users can discover and filter the organization's complete API inventory.
+* The *API Management developer portal* allows users to find managed APIs (including groups of APIs managed as products), learn how to use them, request access, and test them.
+* The *API Center portal* (preview) is a multigateway portal where users can discover and filter the organization's complete API inventory.
 
-While the two portals share some features, they also have distinct differences. The following table compares current capabilities to help determine which portal to use. Some organizations may prefer one portal, while others may need both.
+While the two portals share some features, they also have distinct differences. The following table compares current capabilities to help determine which portal to use. Some organizations might prefer one portal, while others might need both.
 
 | Feature | API Management developer portal | API Center portal (preview) |
 | --- | --- | --- |
@@ -30,7 +30,7 @@ While the two portals share some features, they also have distinct differences.
 | Add custom widgets | ✔️ | ❌ |
 | Customize with WordPress | ✔️ | ❌ |
 | Test APIs in test console | ✔️ | ✔️ |
-| Subscribe to APIs | ✔️ | ❌ |
+| Subscribe to APIs and products | ✔️ | ❌ |
 | View API usage analytics | ✔️ | ❌ |
 
 <sup>1</sup> The API Center portal can contain all APIs in your organization, including those managed in Azure API Management and other platforms, as well as unmanaged APIs and APIs under development.

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/"
       }
     }

articles/api-center/synchronize-api-management-apis.md

@@ -4,15 +4,15 @@ description: Integrate an API Management instance to Azure API Center for automa
 author: dlepow
 ms.service: azure-api-center
 ms.topic: how-to
-ms.date: 07/22/2025
+ms.date: 01/20/2026
 ms.author: danlep 
 ms.custom: devx-track-azurecli
 # Customer intent: As an API program manager, I want to integrate my Azure API Management instance with my API center and synchronize API Management APIs to my inventory.
 ---
 
 # Synchronize APIs from an API Management instance
 
-This article shows how to integrate an API Management instance so that the instances's APIs are continuously kept up to date in your [API center](overview.md) inventory. 
+This article shows how to integrate an API Management instance so that the instance's APIs are continuously kept up to date in your [API center](overview.md) inventory. 
 
 > [!TIP]
 > This article explains how to integrate an API Management instance from your API center. Alternatively, quickly set up integration directly from an API Management instance. In the left menu of your instance, under **APIs**, select **API Center**, and select a target API center in your subscription to synchronize APIs to.
@@ -31,7 +31,7 @@ API Management APIs automatically synchronize to the API center whenever existin
 
 > [!NOTE]
 > * There are [limits](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json#azure-api-center-limits) for the number of integrated API Management instances (API sources).
-> * An integrated API Management instance can be configured in a virtual network.
+> * You can configure an integrated API Management instance in a virtual network.
 > * API updates in API Management typically synchronize to your API center within minutes, but synchronization can take up to 24 hours.
 > * API definitions also synchronize to the API center if you select the option to include them during integration.
 
@@ -41,7 +41,7 @@ API Management APIs automatically synchronize to the API center whenever existin
 
 ## Prerequisites
 
-* An API center in your Azure subscription. If you haven't created one, see [Quickstart: Create your API center](set-up-api-center.md).
+* An API center in your Azure subscription. If you didn't create an API center, see [Quickstart: Create your API center](set-up-api-center.md).
 
 * An Azure API Management instance, in the same or a different subscription. The instance must be in the same directory. 
 
@@ -51,7 +51,7 @@ API Management APIs automatically synchronize to the API center whenever existin
     [!INCLUDE [install-apic-extension](includes/install-apic-extension.md)]
 
     > [!NOTE]
-    > Azure CLI command examples in this article can run in PowerShell or a bash shell. Where needed because of different variable syntax, separate command examples are provided for the two shells.
+    > You can run Azure CLI command examples in this article in PowerShell or a bash shell. Where different variable syntax is required, the article provides separate command examples for the two shells.
 
 [!INCLUDE [enable-managed-identity](includes/enable-managed-identity.md)]
 
@@ -61,14 +61,14 @@ API Management APIs automatically synchronize to the API center whenever existin
 
 ## Integrate an API Management instance 
 
-You can integrate an API Management instance using the portal or the Azure CLI.
+You can integrate an API Management instance by using the portal or the Azure CLI.
 
 #### [Portal](#tab/portal)
 
-1. In the [portal](https://portal.azure.com), navigate to your API center.
+1. In the [portal](https://portal.azure.com), go to your API center.
 1. Under **Platforms**, select **Integrations**.
 1. Select **+ New integration** > **From Azure API Management**.
-1. In the **Integrate your Azure API Management Service** page:
+1. In **Integrate your Azure API Management Service**:
     1. Select whether to synchronize all APIs from the API Management instance or only APIs that are in an API Management [workspace](../api-management/workspaces-overview.md). 
     1. Select the **Subscription**, **Resource group**, and **Azure API Management service** that you want to integrate. If you want to synchronize only APIs from a workspace, make a selection in **Choose a workspace**.
     1. In **Integration details**, enter an identifier.
@@ -85,9 +85,14 @@ You can integrate an API Management instance using the portal or the Azure CLI.
 
 Run the [az apic integration create apim](/cli/azure/apic/integration/create#az-apic-integration-create-apim) command to integrate an API Management instance to your API center. 
 
+> [!NOTE]
+>
+> * This command is only available in the preview version of the APIC extension.
+> * Install the new preview version before using this command.
+
 * Provide the names of the resource group, API center, and integration.  
 
-* If the API Management instance and the API center are in the same resource group, you can provide the API Management instance name as the value of `azure-apim`; otherwise, provide the Azure resource ID. 
+* If the API Management instance and the API center are in the same resource group, you can provide the API Management instance name as the value of `azure-apim`. Otherwise, provide the Azure resource ID. 
 
 ```azurecli
 az apic integration create apim \