Azure AD B2C end of sale docs update in azure-docs-pr - p1 #300077

Author: kengaderdus

articles/active-directory-b2c/index-desktop.yml

@@ -3,8 +3,6 @@
 title: Azure AD B2C desktop app authentication documentation
 summary: >
   Learn how to sign in users and access web APIs in your desktop application using our how-to guides.
-  
-  [!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 metadata:
   author: kengaderdus

articles/api-management/breaking-changes/overview.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: reference
-ms.date: 07/15/2024
+ms.date: 05/30/2025
 ms.author: danlep
 ---
 
@@ -30,7 +30,7 @@ The following table lists all the upcoming breaking changes and feature retireme
 | [Git repository retirement][git2025] | March 15, 2025 |
 | [Direct management API retirement][mgmtapi2025] | March 15, 2025 |
 | [Workspaces preview breaking changes, part 2][workspaces2025march] | March 31, 2025 |
-| [ADAL-based Microsoft Entra ID or Azure AD B2C identity provider retirement][msal2025] | September 30, 2025 |
+| [ADAL-based Microsoft Entra ID identity provider retirement][msal2025] | September 30, 2025 |
 | [CAPTCHA endpoint update][captcha2025] | September 30, 2025 |
 | [Built-in analytics dashboard retirement][analytics2027] | March 15, 2027 |
 

articles/api-management/front-door-api-management.md

@@ -7,7 +7,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 30/05/2025
+ms.date: 05/30/2025
 ms.author: danlep
 ---
 # Configure Front Door Standard/Premium in front of Azure API Management

articles/healthcare-apis/azure-api-for-fhir/fhir-faq.yml

@@ -6,7 +6,7 @@ metadata:
   ms.service: azure-health-data-services
   ms.subservice: fhir
   ms.topic: faq
-  ms.date: 03/21/2022
+  ms.date: 05/30/2025
   ms.author: kesheth
 title: Frequently asked questions about Azure API for FHIR
 summary: |
@@ -33,12 +33,6 @@ sections:
           What identity provider do you support?
         answer: |
           We support Microsoft Entra ID as the identity provider.
-
-      - question: |
-          Can I use Azure AD B2C with the Azure API for FHIR?
-        answer: |
-          No, we don't support B2C in the Azure API for FHIR. If you need more granular access controls, we recommend looking at the [open-source FHIR proxy](https://github.com/microsoft/fhir-proxy). 
-
       - question: |
           What is the backup and recovery policy for the Azure API for FHIR?
         answer: |

articles/healthcare-apis/release-notes-2024.md

@@ -222,21 +222,6 @@ Learn more:
 
 - [Selectable search parameters for the FHIR service](fhir/selectable-search-parameters.md)
 
-#### Integration of the FHIR service with Azure Active Directory B2C
-
-Healthcare organizations can use the FHIR service in Azure Health Data Services with Azure Active Directory B2C (Azure AD B2C). Organizations gain a secure and convenient way to grant access to the FHIR service with fine-grained access control for different users or groups, without creating or comingling user accounts in their organization’s Microsoft Entra ID tenant. With this integration, organizations can:
-
-- Use additional identity providers to authenticate and access FHIR resources with SMART on FHIR scopes. 
-- Manage and customize user access rights or permissions with SMART on FHIR scopes that support fine-grained access control, FHIR resource types and interactions, and a user’s underlying privileges.
-
-Related content:
-
-- [Use Azure Active Directory B2C to grant access to the FHIR service](fhir/azure-ad-b2c-setup.md)
-- [Configure multiple service identity providers for the FHIR service](fhir/configure-identity-providers.md)
-- [Troubleshoot identity provider configuration for the FHIR service](fhir/troubleshoot-identity-provider-configuration.md)
-- [Enable SMART on FHIR for the FHIR service](fhir/smart-on-fhir.md)
-- [Sample: Azure ONC (g)(10) SMART on FHIR](https://github.com/Azure-Samples/azure-health-data-and-ai-samples/tree/main/samples/patientandpopulationservices-smartonfhir-oncg10)
-
 #### Request up to 100 TB of storage
 
 The FHIR service can store and exchange large amounts of health data, and each FHIR service instance has a storage limit of 4 TB by default. If you have more data, you can ask Microsoft to increase storage up to 100 TB for your FHIR service.
@@ -258,4 +243,4 @@ To request storage greater than 4 TB, [create a support request](https://portal.
 
 [Known issues](known-issues.md)
 
-[!INCLUDE [FHIR and DICOM trademark statement](includes/healthcare-apis-fhir-dicom-trademark.md)]
+[!INCLUDE [FHIR and DICOM trademark statement](includes/healthcare-apis-fhir-dicom-trademark.md)]