Merge branch 'main' into release-migrate-agent-public-preview

Author: v-alje

.openpublishing.redirection.json

@@ -7288,6 +7288,11 @@
     {
       "source_path": "articles/virtual-network/virtual-network-troubleshoot-cannot-delete-vnet.md",
       "redirect_url": "/troubleshoot/azure/virtual-network/virtual-network-troubleshoot-cannot-delete-vnet"
-    }
+    },
+    {
+      "source_path": "articles/certification/edge-secured-core-get-certified.md",
+      "redirect_url": "/azure/certification/requirements-edge-secured-core",
+      "redirect_document_id": false
+    },
   ]
 }

articles/api-center/authorize-api-access.md

@@ -76,4 +76,5 @@ To allow import of APIs, assign your API center's managed identity the **Key Vau
         --assignee-object-id $apicObjID `
         --assignee-principal-type ServicePrincipal `
         --scope $scope 
+    ```
 ---

articles/api-center/includes/configure-managed-identity-kv-secret-user.md

@@ -11,8 +11,6 @@ ms.date: 12/20/2024
 ms.custom: Include file
 ---
 
-## Enable a managed identity in your API center
-
 For this scenario, your API center uses a [managed identity](/entra/identity/managed-identities-azure-resources/overview) to access Azure resources. Depending on your needs, enable either a system-assigned or one or more user-assigned managed identities. 
 
 The following examples show how to enable a system-assigned managed identity by using the Azure portal or the Azure CLI. At a high level, configuration steps are similar for a user-assigned managed identity. 

articles/api-center/includes/enable-managed-identity.md

@@ -14,27 +14,11 @@ ms.custom: Include file
 
 To store the API key as a secret in the key vault, see [Set and retrieve secret in Key Vault](/azure/key-vault/secrets/quick-create-portal).
 
-#### Enable a managed identity in your API center
 
-For this scenario, your API center uses a [managed identity](/entra/identity/managed-identities-azure-resources/overview) to access the key vault. Depending on your needs, enable either a system-assigned or one or more user-assigned managed identities. 
+### Enable a managed identity in your API center
 
-The following example shows how to enable a system-assigned managed identity by using the Azure portal. At a high level, configuration steps are similar for a user-assigned managed identity. 
+[!INCLUDE [enable-managed-identity](includes/enable-managed-identity.md)]
 
+### Assign the managed identity the Key Vault Secrets User role
 
-1. In the [portal](https://azure.microsoft.com), navigate to your API center.
-1. In the left menu, under **Security**, select **Managed identities**.
-1. Select **System assigned**, and set the status to **On**.
-1. Select **Save**.
-
-#### Assign the Key Vault Secrets User role to the managed identity
-
-Assign your API center's managed identity the **Key Vault Secrets User** role in your key vault. The following steps use the Azure portal.
-
-1. In the [portal](https://azure.microsoft.com), navigate to your key vault.
-1. In the left menu, select **Access control (IAM)**.
-1. Select **+ Add role assignment**.
-1. On the **Add role assignment** page, set the values as follows: 
-    1. On the **Role** tab, select **Key Vault Secrets User**.
-    1. On the **Members** tab, in **Assign access to**, select **Managed identity** > **+ Select members**.
-    1. On the **Select managed identities** page, select the system-assigned managed identity of your API center that you added in the previous section. Click **Select**.
-    1. Select **Review + assign** twice.
+[!INCLUDE [configure-managed-identity-kv-secret-user](includes/configure-managed-identity-kv-secret-user.md)]

articles/api-center/includes/store-secret-key-vault.md

@@ -55,9 +55,11 @@ API Management APIs automatically synchronize to the API center whenever existin
     > [!NOTE]
     > 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.
 
+## Enable a managed identity in your API center
+
 [!INCLUDE [enable-managed-identity](includes/enable-managed-identity.md)]
 
-## Assign the managed identity the API Management Service Reader role
+### Assign the managed identity the API Management Service Reader role
 
 [!INCLUDE [configure-managed-identity-apim-reader](includes/configure-managed-identity-apim-reader.md)]
 

articles/api-center/media/authorize-api-access/add-authentication-to-version.png

@@ -83,10 +83,11 @@ Manually upload and securely store the two IAM user access keys in Azure Key Vau
 
 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.
 
+## Configure a managed identity for your API center
 
 [!INCLUDE [enable-managed-identity](includes/enable-managed-identity.md)]
 
-## Assign the managed identity the Key Vault Secrets User role
+### Assign the managed identity the Key Vault Secrets User role
 
 [!INCLUDE [configure-managed-identity-kv-secret-user](includes/configure-managed-identity-kv-secret-user.md)]
 

articles/api-center/media/authorize-api-access/edit-access-policies.png

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 11/11/2025
+ms.date: 03/11/2026
 ms.author: danlep
 ms.custom:
   - references_regions
@@ -24,6 +24,8 @@ API Management [v2 tiers](v2-service-tiers-overview.md) and API Management [work
 
 Information in the following table is updated regularly. Capacity availability in Azure regions may vary.
 
+> [!IMPORTANT]
+> **Temporary capacity limitation:** Creation of new Basic v2 and Standard v2 instances in **UK South** is currently unavailable due to capacity constraints. We're actively working to restore availability in this region. In the meantime, consider deploying to an alternative region such as **UK West** or **North Europe**. Existing instances in UK South are not affected.
 
 | Region | Basic v2 | Standard v2 | Premium v2 | Workspace gateway (Premium) | 
 |-----|:---:|:---:|:---:|:---:|
@@ -52,12 +54,14 @@ Information in the following table is updated regularly. Capacity availability i
 | South India | ✅ | ✅ |  |  |
 | Switzerland North | ✅ |✅ |  | |
 | UAE North | ✅ | ✅ | |  |
-| UK South | ✅  | ✅ | ✅ | ✅ |
+| UK South | ✅ ¹ | ✅ ¹ | ✅ | ✅ |
 | UK West | ✅  | ✅ | | |
 | West Europe  | ✅ | ✅ | | ✅ |
 | West US | ✅ | ✅ |  | ✅ |
 | West US 2 | ✅ | ✅ |  | |
 
+¹ New instance creation temporarily unavailable. See the capacity limitation note above.
+
 ## Related content
 
 Learn more about: