Skip to content

Commit 4156171

Browse files
committed
draft complete
1 parent aa944cf commit 4156171

2 files changed

Lines changed: 18 additions & 21 deletions

File tree

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

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -73,19 +73,21 @@ API Management supports external identity providers when you configure them in a
7373

7474
To optionally enable access to the developer portal by external users in your Microsoft Entra ID tenant, complete the following steps:
7575

76-
* Add an external identity provider to your Microsoft Entra ID tenant.
77-
* Enable self-service sign-up.
76+
1. Add an external identity provider to your Microsoft Entra ID tenant.
77+
1. Enable self-service sign-up.
7878

79-
### Add an external identity provider to your Microsoft Entra ID tenant
79+
### 1. Add an external identity provider to your Microsoft Entra ID tenant
8080

81-
For this scenario, you must enable an external identity provider 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).
81+
For this scenario, you must enable an external identity provider in your workforce tenant. Configuring the external identity provider depends on the specific provider and is outside the scope of this article. For example, for Google you must create a project in the Google Developers Console, then configure the project credentials in Microsoft Entra.
8282

83-
### Enable self-service sign-up
83+
For options and links to steps, see [Identity providers for External ID in workforce tenants](/entra/external-id/identity-providers).
84+
85+
### 2. Enable self-service sign-up
8486

8587
To allow external users to register for access to the developer portal, complete the following steps:
8688

87-
* Enable self-service sign-up for your tenant.
88-
* Add your app to the self-service sign-up user flow.
89+
a. Enable self-service sign-up for your tenant.
90+
b. Add your app to the self-service sign-up user flow.
8991

9092
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).
9193

@@ -96,17 +98,17 @@ For more information and detailed steps, see [Add self-service sign-up user flow
9698
9799
To optionally enable access to the developer portal by users from more than one Microsoft Entra ID tenant, complete the following steps:
98100

99-
* Configure app registration for multiple tenants.
100-
* Update the Microsoft Entra ID identity provider configuration for the developer portal to add another tenant.
101+
1. Configure app registration for multiple tenants.
102+
1. Update the Microsoft Entra ID identity provider configuration for the developer portal to add another tenant.
101103

102-
### Configure app registration for multiple tenants
104+
### 1. Configure app registration for multiple tenants
103105

104106
The app registration must support multiple tenants. You can configure this support in either of the following ways:
105107

106108
* When creating the app registration, set **Supported account types** to **Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant)**.
107109
* If you previously configured an app registration for a single tenant, update the **Supported account types** setting on the **Manage** > **Authentication** page of the app registration.
108110

109-
### Update Microsoft Entra ID identity provider configuration for multiple tenants
111+
### 2. Update Microsoft Entra ID identity provider configuration for multiple tenants
110112

111113
Update the identity provider configuration to add another tenant:
112114

articles/api-management/secure-developer-portal-access.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: dlepow
66

77
ms.service: azure-api-management
88
ms.topic: concept-article
9-
ms.date: 12/08/2025
9+
ms.date: 03/04/2026
1010
ms.author: danlep
1111
ms.custom: sfi-image-nochange
1212
---
@@ -22,21 +22,16 @@ API Management has a fully customizable, standalone, managed [developer portal](
2222
2323
## Authentication options
2424

25-
* **External users** - To enable access to the developer portal for external users, use external identity providers enabled through [Microsoft Entra External ID](/entra/external-id/external-identities-overview).
26-
* For example, you want users to access the developer portal by using existing social media accounts.
27-
* The service provides features to enable the end user sign-up and sign-in experience.
25+
* **Internal users** - To enable access to the developer portal for internal users, use your corporate (workforce) Microsoft Entra ID tenant. Microsoft Entra ID provides a seamless single sign-on (SSO) experience for corporate users who need to access and discover APIs through the developer portal.
26+
27+
For steps to enable Microsoft Entra authentication in the developer portal, see [How to authorize developer accounts by using Microsoft Entra ID in Azure API Management](api-management-howto-aad.md).
2828

29-
Currently, API Management supports external identity providers when configured in your Microsoft Entra ID workforce tenant, not in an external tenant. For more information, see [How to authorize developer accounts by using Microsoft Entra External ID](api-management-howto-entra-external-id.md).
29+
* **External users** - To enable access to the developer portal for external users, you can configure [external identity providers](/entra/external-id/identity-providers) in your Microsoft Entra ID workforce tenant. For example, you might want users to sign up and sign in to the developer portal by using existing social media accounts. For more information, see [Enable access by external users in your Microsoft Entra ID tenant](api-management-howto-aad.md#enable-access-by-external-users).
3030

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

3333
[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
3434

35-
* **Internal users** - To enable access to the developer portal for internal users, use your corporate (workforce) Microsoft Entra ID tenant. Microsoft Entra ID provides a seamless single sign-on (SSO) experience for corporate users who need to access and discover APIs through the developer portal.
36-
37-
For steps to enable Microsoft Entra authentication in the developer portal, see [How to authorize developer accounts by using Microsoft Entra ID in Azure API Management](api-management-howto-aad.md).
38-
39-
4035
* **Basic authentication** - Use the built-in developer portal [username and password](developer-portal-basic-authentication.md) provider. This option allows developers to register directly in API Management and sign in by using API Management user accounts. User registration through this option is protected by a CAPTCHA service.
4136

4237
> [!CAUTION]

0 commit comments

Comments
 (0)