Skip to content

Commit edb540b

Browse files
committed
appi management and health apis
1 parent 9969b32 commit edb540b

File tree

5 files changed

+21
-11
lines changed

5 files changed

+21
-11
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: dlepow
77

88
ms.service: azure-api-management
99
ms.topic: how-to
10-
ms.date: 01/07/2025
10+
ms.date: 05/20/2025
1111
ms.author: danlep
1212
ms.custom: engagement-fy23
1313
---
@@ -16,6 +16,8 @@ ms.custom: engagement-fy23
1616

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

19+
[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
20+
1921
Azure Active Directory B2C is a cloud identity management solution for consumer-facing web and mobile applications. You can use it to manage access to your API Management developer portal.
2022

2123
In this tutorial, you'll learn the configuration required in your API Management service to integrate with Azure Active Directory B2C.

articles/api-management/breaking-changes/identity-provider-adal-retirement-sep-2025.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,14 +5,16 @@ services: api-management
55
author: mikebudzynski
66
ms.service: azure-api-management
77
ms.topic: reference
8-
ms.date: 09/06/2022
8+
ms.date: 05/21/2025
99
ms.author: mibudz
1010
---
1111

1212
# ADAL-based Microsoft Entra ID or Azure AD B2C identity provider retirement (September 2025)
1313

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

16+
[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
17+
1618
On 30 September, 2025 as part of our continuing work to increase the resiliency of API Management services, we're removing the support for the previous library for user authentication and authorization in the developer portal (AD Authentication Library, or ADAL). You need to migrate your Microsoft Entra ID or Azure AD B2C applications, change identity provider configuration to use the Microsoft Authentication Library (MSAL), and republish your developer portal.
1719

1820
This change will have no effect on the availability of your API Management service. However, you have to take steps described below to configure your API Management service if you wish to continue using Microsoft Entra ID or Azure AD B2C identity providers beyond 30 September, 2025.
@@ -68,4 +70,4 @@ If you have questions, get answers from community experts in [Microsoft Q&A](htt
6870

6971
## Next steps
7072

71-
See all [upcoming breaking changes and feature retirements](overview.md).
73+
See all [upcoming breaking changes and feature retirements](overview.md).

articles/api-management/howto-protect-backend-frontend-azure-ad-b2c.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: WillEastbury
77
manager: alberts
88
ms.service: azure-api-management
99
ms.topic: how-to
10-
ms.date: 02/18/2021
10+
ms.date: 05/20/2025
1111
ms.author: wieastbu
1212
ms.custom: fasttrack-new, fasttrack-update, devx-track-js
1313
---
@@ -16,6 +16,8 @@ ms.custom: fasttrack-new, fasttrack-update, devx-track-js
1616

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

19+
[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
20+
1921
This scenario shows you how to configure your Azure API Management instance to protect an API.
2022
We'll use the Azure AD B2C SPA (Auth Code + PKCE) flow to acquire a token, alongside API Management to secure an Azure Functions backend using EasyAuth.
2123

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

Lines changed: 8 additions & 6 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: 09/12/2023
9+
ms.date: 05/21/2025
1010
ms.author: danlep
1111
---
1212

@@ -21,13 +21,15 @@ API Management has a fully customizable, standalone, managed [developer portal](
2121
2222
## Authentication options
2323

24-
* **External users** - The preferred option when the developer portal is consumed externally is to enable business-to-consumer access control through Azure Active Directory B2C (Azure AD B2C).
25-
* Azure AD B2C provides the option of using Azure AD B2C native accounts: users sign up to Azure AD B2C and use that identity to access the developer portal.
26-
* Azure AD B2C is also useful if you want users to access the developer portal using existing social media or federated organizational accounts.
27-
* Azure AD B2C provides many features to improve the end user sign-up and sign-in experience, including conditional access and MFA.
24+
* **External users** - The preferred option when the developer portal is consumed externally is to enable business-to-consumer access control through Azure Active Directory B2C (Azure AD B2C) or [Microsoft Entra External ID](/entra/external-id/customers/overview-customers-ciam).
25+
* Both Azure AD B2C and Microsoft Entra External ID provides the option of using native accounts: users sign up and use that identity to access the developer portal.
26+
* Both services are also useful if you want users to access the developer portal using existing social media or federated organizational accounts.
27+
* Both services provide many features to improve the end user sign-up and sign-in experience, including conditional access and MFA.
2828

2929
For steps to enable Azure AD B2C authentication in the developer portal, see [How to authorize developer accounts by using Azure Active Directory B2C in Azure API Management](api-management-howto-aad-b2c.md).
3030

31+
[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
32+
3133

3234
* **Internal users** - The preferred option when the developer portal is consumed internally is to leverage your corporate Microsoft Entra ID. 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.
3335

@@ -116,4 +118,4 @@ Go a step further by delegating [user registration or product subscription](api-
116118

117119
## Related content
118120
* Learn more about [authentication and authorization](../active-directory/develop/authentication-vs-authorization.md) in the Microsoft identity platform.
119-
* Learn how to [mitigate OWASP API security threats](mitigate-owasp-api-threats.md) using API Management.
121+
* Learn how to [mitigate OWASP API security threats](mitigate-owasp-api-threats.md) using API Management.

articles/healthcare-apis/fhir/azure-ad-b2c-setup.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,14 @@ author: namalu
66
ms.service: azure-health-data-services
77
ms.subservice: fhir
88
ms.topic: tutorial
9-
ms.date: 01/21/2024
9+
ms.date: 05/21/2025
1010
ms.author: namalu
1111
---
1212

1313
# Use Azure Active Directory B2C to grant access to the FHIR service
1414

15+
[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
16+
1517
Healthcare organizations can use [Azure Active Directory B2C](../../active-directory-b2c/overview.md) (Azure AD B2C) with the FHIR® service in Azure Health Data Services to grant access to their applications and users.
1618

1719
## Create an Azure AD B2C tenant for the FHIR service

0 commit comments

Comments
 (0)