Skip to content

Commit 0e17bd7

Browse files
Merge pull request #309593 from MicrosoftDocs/main
Auto Publish – main to live - 2025-12-15 23:00 UTC
2 parents 719f77c + 61c2be1 commit 0e17bd7

87 files changed

Lines changed: 545 additions & 601 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

articles/api-management/api-management-howto-aad.md

Lines changed: 71 additions & 109 deletions
Large diffs are not rendered by default.

articles/api-management/api-management-howto-entra-external-id.md

Lines changed: 23 additions & 59 deletions
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,29 @@
11
---
22
title: Authorize Access to API Management Developer Portal by using Microsoft Entra External ID
33
titleSuffix: Azure API Management
4-
description: Learn how to authorize users of the developer portal in Azure API Management by using Microsoft Entra External ID
4+
description: Learn how to authorize external users of the developer portal in Azure API Management by using Microsoft Entra External ID
55
services: api-management
66
author: dlepow
77

88
ms.service: azure-api-management
99
ms.topic: how-to
10-
ms.date: 09/30/2025
10+
ms.date: 12/08/2025
1111
ms.author: danlep
1212
ms.custom:
1313

1414
---
1515

16-
# How to authorize developer accounts by using Microsoft Entra External ID
16+
# How to authorize developer accounts by using external identity providers in Microsoft Entra External ID
1717

1818
[!INCLUDE [premium-dev-standard-premiumv2-standardv2-basicv2.md](../../includes/api-management-availability-premium-dev-standard-premiumv2-standardv2-basicv2.md)]
1919

2020
[Microsoft Entra External ID](/entra/external-id/external-identities-overview) is a cloud identity management solution that allows external identities to securely access your apps and resources. You can use it to manage access to your API Management developer portal by external identities.
2121

22-
In this article, you learn the configuration of the Microsoft Entra ID identity provider for the following scenario:
22+
For an overview of options to secure access to the developer portal, see [Secure access to the API Management developer portal](secure-developer-portal-access.md).
2323

24-
* Integration with Microsoft Entra External ID in your *workforce tenant*. For example, if your workforce tenant is for the Contoso organization, you might want to configure Google or Facebook as an external identity provider so that these external users can also sign in using their accounts.
24+
Currently, API Management supports external identity providers in Microsoft Entra External ID when configured in a Microsoft Entra ID *workforce tenant*. For example, if you're enabling access to the developer portal by users in your workforce tenant, such as the Contoso organization, you might want to configure Google or Facebook as an external identity provider so that these external users can also sign in using their accounts. [Learn more about workforce and external tenant configurations in Microsoft External ID](/entra/external-id/tenant-configurations).
2525

26-
For an overview of options to secure access to the developer portal, see [Secure access to the API Management developer portal](secure-developer-portal-access.md).
26+
[!INCLUDE [api-management-developer-portal-entra-tenants.md](../../includes/api-management-developer-portal-entra-tenants.md)]
2727

2828
[!INCLUDE [api-management-active-directory-b2c-support](../../includes/api-management-active-directory-b2c-support.md)]
2929

@@ -38,78 +38,42 @@ For an overview of options to secure access to the developer portal, see [Secure
3838

3939
## Add external identity provider to your tenant
4040

41-
An external identity provider must be enabled in your workforce tenant. Configuring the external identity provider is outside the scope of this article. For more information, see [Identity providers for External ID in workforce tenant](/entra/external-id/identity-providers).
42-
43-
## Create Microsoft Entra app registration
44-
45-
Create an app registration in your Microsoft Entra ID tenant. The app registration represents the developer portal application in Microsoft Entra and enables the portal to sign in users by using Microsoft Entra ID.
46-
47-
1. In the Azure portal, go to Microsoft Entra ID.
48-
1. In the sidebar menu, under **Manage**, select **App registrations** > **+ New registration**.
49-
1. In the **Register an application** page, enter your application's registration information.
50-
* In the **Name** section, enter an application name of your choosing.
51-
* In the **Supported account types** section, select **Accounts in this organizational directory only**.
52-
* In **Redirect URI**, select **Single-page application (SPA)** and enter the following URL: `https://{your-api-management-service-name}.developer.azure-api.net/signin`, where `{your-api-management-service-name}` is the name of your API Management instance.
53-
* Select **Register** to create the application.
54-
1.On the app **Overview** page, find the **Application (client) ID** and **Directory (tenant) ID** and copy these values to a safe location. You need them later.
55-
1. In the sidebar menu, under **Manage**, select **Certificates & secrets**.
56-
1. From the **Certificates & secrets** page, on the **Client secrets** tab, select **+ New client secret**.
57-
* Enter a **Description**.
58-
* Select any option for **Expires**.
59-
* Choose **Add**.
60-
1. Copy the client **Secret value** to a safe location before leaving the page. You need it later.
61-
1. In the sidebar menu, under **Manage**, select **Token configuration** > **+ Add optional claim**.
62-
1. In **Token type**, select **ID**.
63-
1. Select (check) the following claims: **email**, **family_name**, **given_name**.
64-
1. Select **Add**. If prompted, select **Turn on the Microsoft Graph email, profile permission**.
41+
For this scenario, you must enable an identity provider for External ID in your workforce tenant. Configuring the external identity provider depends on the specific provider and is outside the scope of this article. For options and links to steps, see [Identity providers for External ID in workforce tenants](/entra/external-id/identity-providers).
42+
43+
[!INCLUDE [api-management-developer-portal-entra-app.md](../../includes/api-management-developer-portal-entra-app.md)]
6544

6645
## Enable self-service sign-up for your tenant
6746

68-
For external users to sign up for access to the developer portal, you must complete these steps:
47+
To allow external users to register for access to the developer portal, complete the following steps:
6948

70-
* Enable self-service sign-up for your tenant.
49+
* Enable self-service sign-up for the external tenant.
7150
* Add your app to the self-service sign-up user flow.
7251

73-
For more information and detailed steps, see the following articles:
74-
75-
- Workforce tenant: [Add self-service sign-up user flows for B2B collaboration](/entra/external-id/self-service-sign-up-user-flow)
76-
77-
## Configure Microsoft Entra ID as an identity provider for developer portal
78-
79-
In your API Management instance, configure the Microsoft Entra ID identity provider. You need the values you copied from your app registration in a previous section.
52+
For more information and detailed steps, see [Add self-service sign-up user flows for B2B collaboration](/entra/external-id/self-service-sign-up-user-flow).
8053

81-
1. In the [Azure portal](https://portal.azure.com) tab, navigate to your API Management instance.
82-
1. In the sidebar menu, under **Developer portal**, select **Identities** > **+ Add**.
83-
1. In the **Add identity provider** page, select **Microsoft Entra ID**. Once selected, you're able to enter other necessary information.
84-
1. In **client id**, enter the **Application (client) ID** from your app registration.
85-
1. In **Client secret**, enter the **Secret value** from your app registration.
86-
1. In **Signin tenant**, enter the **Directory (tenant) ID** from your app registration.
87-
* In the **Client library** dropdown, select **MSAL**.
88-
1. Select **Add**.
8954

90-
:::image type="content" source="media/api-management-howto-external-id/entra-id-identity-provider.png" alt-text="Screenshot of the Microsoft Entra ID identity provider configuration in the portal.":::
91-
1. Republish the developer portal for the Microsoft Entra configuration to take effect. In the sidebar menu, under **Developer portal**, select **Portal overview** > **Publish**.
55+
## <a id="log_in_to_dev_portal"></a> Sign in to developer portal with Microsoft Entra External ID
9256

93-
> [!IMPORTANT]
94-
> You need to [republish the developer portal](developer-portal-overview.md#publish-the-portal) when you create or update the identity provider's configuration settings for the changes to take effect.
57+
In the developer portal, you can enable sign in with Microsoft Entra External ID by using the **Sign-in button: OAuth** widget. The widget is already included on the sign-in page of the default developer portal content.
9558

96-
## Sign in to developer portal with Microsoft Entra External ID
59+
A user can then sign in with Microsoft Entra External ID as follows:
9760

98-
In the developer portal, sign-in with Microsoft Entra External ID is possible with the **Sign-in button: OAuth** widget. The widget is already included on the sign-in page of the default developer portal content.
61+
1. Go to the developer portal. Select **Sign in**.
9962

100-
1. To sign in by using Microsoft Entra External ID, open a new browser window and go to the developer portal. Select **Sign in**.
63+
1. On the **Sign in** page, select **Microsoft Entra ID**.
10164

102-
1. On the **Sign in** page, select **Azure Active Directory**.
65+
:::image type="content" source="media/api-management-howto-external-id/developer-portal-sign-in.png" alt-text="Screenshot of selecting Microsoft Entra ID on Sign in page in developer portal.":::
10366

104-
:::image type="content" source="media/api-management-howto-external-id/developer-portal-sign-in.png" alt-text="Screenshot of select Azure Active Directory on Sign in page in developer portal.":::
67+
> [!TIP]
68+
> If you configure more than one Microsoft Entra tenant for access, more than one Microsoft Entra ID button appears on the sign-in page. Each button is labeled with the tenant name.
10569
106-
1. In the sign-in window for your Microsoft Entra tenant, select **Sign-in options**. Select the identity provider you configured in your Microsoft Entra tenant to sign in. For example, if you configured Google as an identity provider, select **Sign in with Google**.
70+
1. In the sign-in window for your Microsoft Entra tenant, select **Sign-in options**. Select the external identity provider configured in your Microsoft Entra tenant to sign in. For example, if you configured Google as an identity provider, select **Sign in with Google**.
10771

10872
:::image type="content" source="media/api-management-howto-external-id/sign-in-options.png" alt-text="Screenshot of select external identity provider in Microsoft Entra.":::
10973

110-
To continue sign-in, respond to the prompts. After sign-in is complete, you're redirected back to the developer portal.
74+
1. To continue sign-in, respond to the prompts. After sign-in is complete, the user is redirected back to the developer portal.
11175

112-
You're now signed in to the developer portal for your API Management service instance. You're added as a new API Management user identity in Users, and a new external tenant user in Microsoft Entra ID.
76+
The user is now signed in to the developer portal, added as a new API Management user identity in **Users**, and added as a new external tenant user in Microsoft Entra ID.
11377

11478
## Related content
11579

-16.9 KB
Loading
931 Bytes
Loading

0 commit comments

Comments
 (0)