Skip to content

Commit 7e47732

Browse files
committed
line edits
1 parent 001bc19 commit 7e47732

4 files changed

Lines changed: 12 additions & 12 deletions

File tree

articles/api-management/credentials-configure-common-providers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: api-management
55
author: dlepow
66
ms.service: azure-api-management
77
ms.topic: how-to
8-
ms.date: 12/01/2025
8+
ms.date: 12/05/2025
99
ms.author: danlep
1010
ms.custom: sfi-image-nochange
1111
# Customer intent: As an Azure service administrator, I want to learn how to configure common credential providers in the API Management credential manager.
@@ -81,7 +81,7 @@ API Management supports several providers for popular SaaS offerings, including
8181
Required settings for these providers differ, depending on the provider, but are similar to those for the [generic OAuth providers](#generic-oauth-providers). Consult the developer documentation for each provider.
8282

8383
> [!NOTE]
84-
> Currently, the Salesforce provider doesn't include an expiry claim in its tokens. As a result, Credential Manager can't detect when these tokens expire and doesn't expose a mechanism to force refresh. You need custom refresh logic to manually reauthorize the connection to get a new token when the current token expires.
84+
> Currently, the Salesforce provider doesn't include an expiry claim in its tokens. As a result, Credential Manager can't detect when these tokens expire and doesn't expose a mechanism to force refresh. With the Salesforce provider, you need custom refresh logic to manually reauthorize the connection to get a new token when the current token expires.
8585
8686

8787
## Related content

articles/api-management/credentials-how-to-azure-ad.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: api-management
55
author: dlepow
66
ms.service: azure-api-management
77
ms.topic: how-to
8-
ms.date: 12/02/2025
8+
ms.date: 12/05/2025
99
ms.author: danlep
1010
ms.custom: sfi-image-nochange
1111
---
@@ -14,7 +14,7 @@ ms.custom: sfi-image-nochange
1414

1515
[!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
1616

17-
This article guides you through the steps required to create a [managed connection](credentials-overview.md) to the Microsoft Graph API within Azure API Management. The Microsoft Entra identity provider is used to call the Microsoft Graph API. The authorization code grant type ais used in this example.
17+
This article guides you through the steps required to create a [managed connection](credentials-overview.md) to the Microsoft Graph API within Azure API Management. The Microsoft Entra identity provider is used to call the Microsoft Graph API. The authorization code grant type is used in this example.
1818

1919
You learn how to:
2020

@@ -55,11 +55,11 @@ Create a Microsoft Entra application for the API and give it the appropriate per
5555

5656
:::image type="content" source="media/credentials-how-to-azure-ad/create-registration.png" alt-text="Screenshot of creating a Microsoft Entra app registration in the portal.":::
5757

58-
1. On the sidebar menu, select **Manage** > **API permissions**, and then select **+ Add a permission**.
59-
:::image type="content" source="./media/credentials-how-to-azure-ad/add-permission.png" alt-text="Screenshot of adding an API permission in the portal.":::
58+
1. On the sidebar menu, select **Manage** > **API permissions**.
59+
Make sure the permission **User.Read** with the type *Delegated* has already been added.
6060

61-
> [!NOTE]
62-
> Under **Configured permissions**, make sure the permission **User.Read** with the type *Delegated* has already been added.
61+
1. Select **+ Add a permission**.
62+
:::image type="content" source="./media/credentials-how-to-azure-ad/add-permission.png" alt-text="Screenshot of adding an API permission in the portal.":::
6363

6464
1. Select **Microsoft Graph**, and then select **Delegated permissions**.
6565
1. Type **Team**, expand the **Team** options, and then select **Team.ReadBasic.All**. Select **Add permissions**.

articles/api-management/credentials-how-to-github.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: api-management
55
author: dlepow
66
ms.service: azure-api-management
77
ms.topic: how-to
8-
ms.date: 12/02/2025
8+
ms.date: 12/05/2025
99
ms.author: danlep
1010
ms.custom: sfi-image-nochange
1111
---

articles/api-management/credentials-how-to-user-delegated.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: dlepow
66
ms.service: azure-api-management
77
ms.custom: devx-track-azurepowershell
88
ms.topic: how-to
9-
ms.date: 12/02/2025
9+
ms.date: 12/05/2025
1010
ms.author: danlep
1111
---
1212

@@ -82,7 +82,7 @@ Create a Microsoft Entra ID application for user delegation and give it the appr
8282
1. Set the **Redirect URI** to **Web** and enter `https://www.postman-echo.com/get`.
8383
1. Select **Register**.
8484
1. On the left menu, select **Manage** > **API permissions**, then select **+ Add a permission**.
85-
1. Select the **APIs my organization uses** tab, type *Azure API Management Data plane*, and select it.
85+
1. Select the **APIs my organization uses** tab, type *Azure API Management Data Plane*, and select it.
8686
1. Under **Permissions**, select **Authorizations.Read**, and then select **Add permissions**.
8787
1. On the left menu, select **Overview**. On the **Overview** page, find the **Application (client) ID** value and record it for use in a later step.
8888
1. On the left menu, select **Manage** > **Certificates & secrets**, and then select **+ New client secret**.
@@ -93,7 +93,7 @@ Create a Microsoft Entra ID application for user delegation and give it the appr
9393
9494
## Step 3: Configure a credential provider in API Management
9595
96-
In this step, create a credential provider for your backend OAuth 2.0 API that you want to access on behalf of the user or group. For example, follow the steps to create a credential provider for the [GitHub API](credentials-how-to-github.md). Brief steps follow:
96+
In this step, create a credential provider for your backend OAuth 2.0 API that you want to access on behalf of the user or group. For example, follow the steps to create a [credential provider for the GitHub API](credentials-how-to-github.md). Brief steps follow:
9797
9898
1. Create an OAuth app in GitHub for the API and give it the appropriate permissions for the requests that you want to call.
9999
1. Sign into the [Azure portal](https://portal.azure.com) and go to your API Management instance.

0 commit comments

Comments
 (0)