You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/api-management/credentials-configure-common-providers.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: api-management
5
5
author: dlepow
6
6
ms.service: azure-api-management
7
7
ms.topic: how-to
8
-
ms.date: 12/01/2025
8
+
ms.date: 12/05/2025
9
9
ms.author: danlep
10
10
ms.custom: sfi-image-nochange
11
11
# 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
81
81
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.
82
82
83
83
> [!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.
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.
18
18
19
19
You learn how to:
20
20
@@ -55,11 +55,11 @@ Create a Microsoft Entra application for the API and give it the appropriate per
55
55
56
56
:::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.":::
57
57
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.
60
60
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.":::
63
63
64
64
1. Select **Microsoft Graph**, and then select **Delegated permissions**.
65
65
1. Type **Team**, expand the **Team** options, and then select **Team.ReadBasic.All**. Select **Add permissions**.
Copy file name to clipboardExpand all lines: articles/api-management/credentials-how-to-user-delegated.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: dlepow
6
6
ms.service: azure-api-management
7
7
ms.custom: devx-track-azurepowershell
8
8
ms.topic: how-to
9
-
ms.date: 12/02/2025
9
+
ms.date: 12/05/2025
10
10
ms.author: danlep
11
11
---
12
12
@@ -82,7 +82,7 @@ Create a Microsoft Entra ID application for user delegation and give it the appr
82
82
1. Set the **Redirect URI** to **Web** and enter `https://www.postman-echo.com/get`.
83
83
1. Select **Register**.
84
84
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.
86
86
1. Under **Permissions**, select **Authorizations.Read**, and then select **Add permissions**.
87
87
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.
88
88
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
93
93
94
94
## Step 3: Configure a credential provider in API Management
95
95
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:
97
97
98
98
1. Create an OAuth app in GitHub for the API and give it the appropriate permissions for the requests that you want to call.
99
99
1. Sign into the [Azure portal](https://portal.azure.com) and go to your API Management instance.
0 commit comments