Merge branch 'MicrosoftDocs:main' into main

Author: MJyot

.openpublishing.redirection.json

@@ -1,5 +1,15 @@
 {
   "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",

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/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 \

articles/api-center/synchronize-aws-gateway-apis.md

@@ -4,7 +4,7 @@ description: Integrate an Amazon API Gateway to Azure API Center for automatic s
 author: dlepow
 ms.service: azure-api-center
 ms.topic: how-to
-ms.date: 06/02/2025
+ms.date: 01/21/2026
 ms.author: danlep 
 ms.custom: 
   - devx-track-azurecli
@@ -24,9 +24,9 @@ Integrating Amazon API Gateway as an API source for your API center enables cont
 
 When you integrate an Amazon API Gateway as an API source, the following happens:
 
-1. APIs, and optionally API definitions (specs), from the API Gateway are added to the API center inventory.
+1. The API center inventory adds APIs, and optionally API definitions (specs), from the API Gateway.
 1. You configure an [environment](key-concepts.md#environment) of type *Amazon API Gateway* in the API center. 
-1. An associated [deployment](key-concepts.md#deployment) is created for each synchronized API definition. 
+1. You create an associated [deployment](key-concepts.md#deployment) for each synchronized API definition. 
 
 Synchronization is one-way from Amazon API Gateway to your Azure API center, meaning API updates in the API center aren't synchronized back to Amazon API Gateway.
 
@@ -42,9 +42,9 @@ Synchronization is one-way from Amazon API Gateway to your Azure API center, mea
 
 ## 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 one, see [Quickstart: Create your API center](set-up-api-center.md).
 
-* An Azure key vault. If you need to create one, see [Quickstart: Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal). To add or manage secrets in the key vault, at least the **Key Vault Secrets Officer** role or equivalent permissions are required. 
+* An Azure key vault. If you need to create one, see [Quickstart: Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal). To add or manage secrets in the key vault, you need at least the **Key Vault Secrets Officer** role or equivalent permissions. 
 
 * An [Amazon API Gateway](https://docs.aws.amazon.com/apigateway/). 
 
@@ -56,22 +56,22 @@ Synchronization is one-way from Amazon API Gateway to your Azure API center, mea
     [!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 needed because of different variable syntax, separate command examples are provided for the two shells.
 
 ## Create IAM user access keys
 
 To authenticate your API center to Amazon API Gateway, you need access keys for an AWS IAM user. 
 
-To generate the required access key ID and secret key using the AWS Management Console, see [Create an access key for yourself](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-key-self-managed.html#Using_CreateAccessKey) in the AWS documentation. 
+To generate the required access key ID and secret key by using the AWS Management Console, see [Create an access key for yourself](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-key-self-managed.html#Using_CreateAccessKey) in the AWS documentation. 
 
 Save your access keys in a safe location. You'll store them in Azure Key Vault in the next steps.
 
 > [!CAUTION]
-> Access keys are long-term credentials, and you should manage them as securely as you would a password. Learn more about [securing access keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/securing_access-keys.html)
+> Access keys are long-term credentials. Manage them as securely as you would a password. Learn more about [securing access keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/securing_access-keys.html)
 
 ## Store IAM user access keys in Azure Key Vault
 
-Manually upload and securely store the two IAM user access keys in Azure Key Vault using the configuration recommended in the following table. For more information, see [Quickstart: Set and retrieve a secret from Azure Key Vault using the Azure portal](/azure/key-vault/secrets/quick-create-portal). 
+Manually upload and securely store the two IAM user access keys in Azure Key Vault by using the configuration recommended in the following table. For more information, see [Quickstart: Set and retrieve a secret from Azure Key Vault using the Azure portal](/azure/key-vault/secrets/quick-create-portal). 
 
 
 | AWS secret | Upload options | Name | Secret value | 
@@ -81,7 +81,7 @@ Manually upload and securely store the two IAM user access keys in Azure Key Vau
 
 :::image type="content" source="media/synchronize-aws-gateway-apis/key-vault-secrets.png" alt-text="Screenshot of secrets list in Azure Key Vault in the portal.":::
 
-Take note of the **Secret identifier** of each secret, a URI similar to `https://<key-vault-name>.vault.azure.net/secrets/<secret-name>`. You'll use these identifiers in the next steps.
+Take note of the **Secret identifier** of each secret, a URI similar to `https://<key-vault-name>.vault.azure.net/secrets/<secret-name>`. You use these identifiers in the next steps.
 
 
 [!INCLUDE [enable-managed-identity](includes/enable-managed-identity.md)]
@@ -93,19 +93,19 @@ Take note of the **Secret identifier** of each secret, a URI similar to `https:/
 
 ## Integrate an Amazon API Gateway 
 
-You can integrate an Amazon API Gateway using the portal or the Azure CLI.
+You can integrate an Amazon API Gateway 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 Amazon API Gateway**.
-1. In the **Integrate your Amazon API Gateway Service** page:
-    1. For the **AWS access key** and **AWS secret access key**, click **Select** and select the subscription, key vault, secret that you stored. 
-    1. Select the **AWS region** where the Amazon API Gateway is deployed.
+1. In **Integrate your Amazon API Gateway Service**:
+    1. For the **AWS access key** and **AWS secret access key**, select **Select** and choose the subscription, key vault, and secret that you stored. 
+    1. Select the **AWS region** where you deployed the Amazon API Gateway.
     1. In **Integration details**, enter an identifier.
     1. In **Environment details**, enter an **Environment title** (name), **Environment type**, and optional **Description**.
     1. In **API Details**:
-        1. Select a **Lifecycle** for the synchronized APIs. (You can update this value for the APIs after they're added to your API center.)
+        1. Select a **Lifecycle** for the synchronized APIs. (You can update this value for the APIs after you add them to your API center.)
         1. Optionally, select whether to include API definitions with the synchronized APIs.
 1. Select **Create**.
 
@@ -116,9 +116,14 @@ You can integrate an Amazon API Gateway using the portal or the Azure CLI.
 
 Run the [az apic integration create aws](/cli/azure/apic/integration/create#az-apic-integration-create-aws) (preview) command to integrate an Amazon API Gateway 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. 
 
-* Provide the Key Vault secret identifiers for the AWS access key and secret access key, and the AWS region where the Amazon API Gateway is deployed.
+* Provide the Key Vault secret identifiers for the AWS access key and secret access key, and the AWS region where you deployed the Amazon API Gateway.
 
 ```azurecli
 az apic integration create aws \
@@ -131,7 +136,7 @@ az apic integration create aws \
 ``` 
 ---
 
-The environment is added in your API center. The Amazon API Gateway APIs are imported to the API center inventory.
+The environment is added to your API center. The Amazon API Gateway APIs are imported to the API center inventory.
 
 [!INCLUDE [delete-api-integration](includes/delete-api-integration.md)]