Merge branch 'release-ignite-container-apps' of https://github.com/MicrosoftDocs/azure-docs-pr into aca/ignite/rule-based-routing

Author: craigshoemaker

articles/api-management/TOC.yml

@@ -370,7 +370,7 @@
       href: credentials-process-flow.md
     - name: Configure common credential providers
       href: credentials-configure-common-providers.md
-    - name: Configure credential manager - Microsoft Entra ID
+    - name: Configure credential manager - Microsoft Graph API
       href: credentials-how-to-azure-ad.md
     - name: Configure credential manager - GitHub
       href: credentials-how-to-github.md

articles/api-management/automate-portal-deployments.md

@@ -1,10 +1,10 @@
 ---
-title: Automate developer portal deployments
+title: Automate Developer Portal Deployments
 titleSuffix: Azure API Management
 description: Learn how to automatically migrate self-hosted developer portal content between two API Management services.
 author: dlepow
 ms.author: danlep
-ms.date: 04/15/2021
+ms.date: 10/01/2025
 ms.service: azure-api-management
 ms.topic: how-to
 ---
@@ -13,36 +13,34 @@ ms.topic: how-to
 
 [!INCLUDE [api-management-availability-premium-dev-standard-basic](../../includes/api-management-availability-premium-dev-standard-basic.md)]
 
-The API Management developer portal supports programmatic access to content. It allows you to import data to or export from an API Management service through the [content management REST API](/rest/api/apimanagement/). The REST API access works for both managed and self-hosted portals.
+The developer portal in Azure API Management supports programmatic access to content. The developer portal allows you to import data to, or export from, an API Management service through the [content management REST API](/rest/api/apimanagement/). The REST API access works for both managed and self-hosted developer portals.
 
 ## Automated migration script
 
-You can use the API to automate migration of content between two API Management services - for example, a service in the test environment and a service in the production environment. The `scripts.v3/migrate.js` script in the API Management developer portal [GitHub repo](https://github.com/Azure/api-management-developer-portal/blob/master/scripts.v3/migrate.js) simplifies this automation process.
+You can automate the migration of content between two API Management services, for example, a service in the test environment and a service in the production environment. The `scripts.v3/migrate.js` script in the [developer portal GitHub repo](https://github.com/Azure/api-management-developer-portal/blob/master/scripts.v3/migrate.js) simplifies this automation process.
 
 > [!WARNING]
-> The script removes contents of the developer portal in your destination API Management service. If you're concerned about it, make sure you perform a backup.
+> The script removes the contents of the developer portal in your destination API Management service. If you're concerned about it, make sure you perform a backup.
 
 > [!NOTE]
 > Using the script to migrate developer portal content between an API Management instance in a classic tier (for example, Standard) and an instance in a v2 tier (for example, Standard v2) isn't currently supported. Migration of portal content between instances in the v2 tiers is also not supported.
 
 > [!NOTE]
-> If you're using a self-hosted portal with an explicitly defined custom storage account to host media files (i.e., you define the `blobStorageUrl` setting in the `config.design.json` configuration file), you need to use the original `scripts/migrate.js` [script](https://github.com/Azure/api-management-developer-portal/blob/master/scripts.v2/migrate.js). The original script doesn't work for managed or self-hosted portals with the media storage account managed by API Management. In that case, use the script from the `/scripts.v3` folder instead.
+> If you're using a self-hosted developer portal with an explicitly defined custom storage account to host media files (that is, you define the `blobStorageUrl` setting in the `config.design.json` configuration file), you need to use the [original `scripts.v2/migrate.js` script](https://github.com/Azure/api-management-developer-portal/blob/master/scripts.v2/migrate.js). The original script doesn't work for managed or self-hosted portals with the media storage account managed by API Management. In that case, use the script from the `/scripts.v3` folder instead.
 
 The script performs the following steps:
 
-1. Capture the portal content and media from the source API Management service.
-1. Remove the portal content and media from the destination API Management service.
-1. Upload the portal content and media to the destination API Management service.
-1. Optionally and for managed portals only - automatically publish the portal.
+1. Captures the portal content and media from the source API Management service.
+1. Removes the portal content and media from the destination API Management service.
+1. Uploads the portal content and media to the destination API Management service.
+1. Optionally and for managed portals only: automatically publishes the portal.
 
-After the script is successfully executed, the target API Management service should contain the same portal content as the source service and you'll be able to see it as an administrator.
+After the script runs successfully, the target API Management service should contain the same portal content as the source service and you'll be able to see it as an administrator.
 
-* If you're using a managed portal, you can set the script to auto-publish the destination portal to make the migrated version automatically available to the visitors. 
-* If you're using a self-hosted portal, you need to publish the destination portal manually. Follow the publishing and hosting instructions in the tutorial to [set up a self-hosted developer portal](developer-portal-self-host.md).
+* If you're using a managed portal, you can set the script to autopublish the destination portal to make the migrated version automatically available to visitors.
+* If you're using a self-hosted portal, you need to publish the destination portal manually. Follow the publishing and hosting instructions in the tutorial to set up a [self-hosted developer portal](developer-portal-self-host.md).
 
 ## Related content
 
-Learn more about the developer portal:
-
-- [Azure API Management developer portal overview](api-management-howto-developer-portal.md)
-- [Self-host the developer portal](developer-portal-self-host.md)
+- [Overview of the developer portal](api-management-howto-developer-portal.md)
+- [Self-host the API Management developer portal](developer-portal-self-host.md)

articles/api-management/configure-credential-connection.md

@@ -1,11 +1,12 @@
 ---
-title: Set up multiple connections - Azure API Management 
+title: Set up Multiple Connections
+titleSuffix: Azure API Management
 description: Learn how to set up multiple connections to a configured API credential provider using the portal. 
 services: api-management
 author: dlepow
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 11/08/2023
+ms.date: 10/01/2025
 ms.author: danlep
 ms.custom: sfi-image-nochange
 ---
@@ -16,34 +17,33 @@ ms.custom: sfi-image-nochange
 
 You can configure multiple connections to a credential provider in your API Management instance. For example, if you configured Microsoft Entra ID as a credential provider, you might need to create multiple connections for different scenarios and users.
 
-In this article, you learn how to add a connection to an existing provider, using credential manager in the portal. For an overview of credential manager, see [About API credentials and credential manager](credentials-overview.md).
+In this article, you learn how to add a connection to an existing provider by using credential manager in the Azure portal. For an overview of credential manager, see [About API credentials and credential manager](credentials-overview.md).
 
 ## Prerequisites
 
-* An API Management instance. If you need to, [create one](get-started-create-service-instance.md).
+* An API Management instance. If you don't have one, see [Create a new Azure API Management instance](get-started-create-service-instance.md).
 * A configured credential provider. For example, see the steps to create a provider for [GitHub](credentials-how-to-github.md) or [Microsoft Entra ID](credentials-how-to-azure-ad.md).
 
-## Create a connection - portal
+## Create a connection
 
-1. Sign into the [portal](https://portal.azure.com) and go to your API Management instance.
-1. In the left menu, select **Credential manager**.
-1. Select the credential provider that you want to create multiple connections for (for example, *mygithub*).
-1. In the provider window, select **Overview** > **+ Create connection**.
+1. Sign in to the [Azure portal](https://portal.azure.com) and go to your API Management instance.
+1. Under **APIs** in the sidebar menu, select **Credential manager**.
+1. Select the credential provider that you want to create multiple connections for.
+1. In the credential provider window, select **Overview**, then choose **+ Create connection**.
 
     :::image type="content" source="media/configure-credential-connection/create-credential.png" alt-text="Screenshot of creating a connection in the portal.":::
 
 1. On the **Connection** tab, complete the steps for your connection. 
 
     [!INCLUDE [api-management-credential-create-connection](../../includes/api-management-credential-create-connection.md)]
 
-## Manage credentials - portal
+## Manage credentials
 
 You can manage credential provider settings and connections in the portal. For example, you might need to update a client secret for a credential provider.
 
 To update provider settings:
 
-1. Sign into [portal](https://portal.azure.com) and go to your API Management instance.
-1. In the left menu, select **Credential manager**.
+1. Under **APIs** in the sidebar menu, select **Credential manager**.
 1. Select the credential provider that you want to manage.
 1. In the provider window, select **Settings**.
 1. In the provider settings, make updates, and select **Save**.
@@ -52,8 +52,7 @@ To update provider settings:
 
 To update a connection:
 
-1. Sign into [portal](https://portal.azure.com) and go to your API Management instance.
-1. In the left menu, select **Credential manager**.
+1. Under **APIs** in the sidebar menu, select **Credential manager**.
 1. Select the credential provider whose connection you want to update.
 1. In the provider window, select **Connections**.
 1. In the row for the connection you want to update, select the context (...) menu, and select from the options. For example, to manage access policies, select **Edit access policies**.