Adding include and updating faq

garrodonnell · garrodonnell · commit 5619e55d2336 · 2025-04-30T18:43:39.000+01:00
diff --git a/articles/active-directory-b2c/overview.md b/articles/active-directory-b2c/overview.md
@@ -15,7 +15,7 @@ ms.subservice: b2c
 ---
 
 # What is Azure Active Directory B2C?
-[!INCLUDE [active-directory-b2c-end-of-sale-notice-a](../../includes/active-directory-b2c-end-of-sale-notice-a.md)]
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 Azure Active Directory B2C provides business-to-customer identity as a service. Your customers can use their preferred social, enterprise, or local account identities to get single sign-on access to your applications and APIs.
 
diff --git a/articles/active-directory-b2c/password-complexity.md b/articles/active-directory-b2c/password-complexity.md
@@ -19,6 +19,7 @@ zone_pivot_groups: b2c-policy-type
 ---
 
 # Configure complexity requirements for passwords in Azure Active Directory B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 [!INCLUDE [active-directory-b2c-choose-user-flow-or-custom-policy](../../includes/active-directory-b2c-choose-user-flow-or-custom-policy.md)]
 
diff --git a/articles/active-directory-b2c/phone-authentication-user-flows.md b/articles/active-directory-b2c/phone-authentication-user-flows.md
@@ -19,6 +19,7 @@ ms.subservice: b2c
 ---
 
 # Set up phone sign-up and sign-in for user flows
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 In addition to email and username, you can enable phone number as a sign-up option tenant-wide by adding phone sign-up and sign-in to your local account identity provider. After you enable phone sign-up and sign-in for local accounts, you can add phone sign-up to your user flows.
 
diff --git a/articles/active-directory-b2c/phone-based-mfa.md b/articles/active-directory-b2c/phone-based-mfa.md
@@ -17,6 +17,7 @@ ms.subservice: b2c
 
 ---
 # Securing phone-based multifactor authentication
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 With Microsoft Entra multifactor authentication, users can choose to receive an automated voice call at a phone number they register for verification. Malicious users could take advantage of this method by creating multiple accounts and placing phone calls without completing the MFA registration process. These numerous failed sign-ups could exhaust the allowed sign-up attempts, preventing other users from signing up for new accounts in your Azure AD B2C tenant. To help protect against these attacks, you can use Azure Monitor to monitor phone authentication failures and mitigate fraudulent sign-ups.
 
diff --git a/articles/active-directory-b2c/phone-factor-technical-profile.md b/articles/active-directory-b2c/phone-factor-technical-profile.md
@@ -20,6 +20,7 @@ ms.subservice: b2c
 ---
 
 # Define a phone factor technical profile in an Azure Active Directory B2C custom policy
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 [!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
 
diff --git a/articles/active-directory-b2c/phone-number-claims-transformations.md b/articles/active-directory-b2c/phone-number-claims-transformations.md
@@ -19,6 +19,7 @@ ms.subservice: b2c
 ---
 
 # Define phone number claims transformations in Azure AD B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 This article provides reference and examples for using the phone number claims transformations in Azure Active Directory B2C (Azure AD B2C) custom policy. For more information about claims transformations in general, see [ClaimsTransformations](claimstransformations.md).
 
diff --git a/articles/active-directory-b2c/policy-keys-overview.md b/articles/active-directory-b2c/policy-keys-overview.md
@@ -19,6 +19,7 @@ zone_pivot_groups: b2c-policy-type
 ---
 
 # Overview of policy keys in Azure Active Directory B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 [!INCLUDE [active-directory-b2c-choose-user-flow-or-custom-policy](../../includes/active-directory-b2c-choose-user-flow-or-custom-policy.md)]
 
diff --git a/articles/active-directory-b2c/predicates.md b/articles/active-directory-b2c/predicates.md
@@ -19,6 +19,7 @@ ms.subservice: b2c
 ---
 
 # Predicates and PredicateValidations
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 [!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
 
diff --git a/articles/active-directory-b2c/protocols-overview.md b/articles/active-directory-b2c/protocols-overview.md
@@ -18,6 +18,7 @@ ms.subservice: b2c
 ---
 
 # Azure AD B2C: Authentication protocols
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 Azure Active Directory B2C (Azure AD B2C) provides identity as a service for your apps by supporting two industry standard protocols: OpenID Connect and OAuth 2.0. The service is standards-compliant, but any two implementations of these protocols can have subtle differences.
 
diff --git a/articles/active-directory-b2c/publish-app-to-azure-ad-app-gallery.md b/articles/active-directory-b2c/publish-app-to-azure-ad-app-gallery.md
@@ -19,6 +19,7 @@ ms.subservice: b2c
 ---
 
 # Publish your Azure Active Directory B2C app to the Microsoft Entra app gallery
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 The Microsoft Entra app gallery is a catalog of thousands of apps. The app gallery makes it easy to deploy and configure single sign-on (SSO) and automate user setup. You can find popular cloud apps in the gallery, such as Workday, ServiceNow, and Zoom.
 
diff --git a/articles/active-directory-b2c/quickstart-native-app-desktop.md b/articles/active-directory-b2c/quickstart-native-app-desktop.md
@@ -18,8 +18,7 @@ ms.subservice: b2c
 ---
 
 # Quickstart: Set up sign in for a desktop app using Azure Active Directory B2C
-
-[!INCLUDE [active-directory-b2c-end-of-sale-notice-a](../../includes/active-directory-b2c-end-of-sale-notice-a.md)]
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 Azure Active Directory B2C (Azure AD B2C) provides cloud identity management to keep your application, business, and customers protected. Azure AD B2C enables your applications to authenticate to social accounts and enterprise accounts using open standard protocols. In this quickstart, you use a Windows Presentation Foundation (WPF) desktop application to sign in using a social identity provider and call an Azure AD B2C protected web API.
 
diff --git a/articles/active-directory-b2c/quickstart-single-page-app.md b/articles/active-directory-b2c/quickstart-single-page-app.md
@@ -19,7 +19,7 @@ ms.custom: mode-other
 
 # Quickstart: Set up sign in for a single-page app using Azure Active Directory B2C
 
-[!INCLUDE [active-directory-b2c-end-of-sale-notice-a](../../includes/active-directory-b2c-end-of-sale-notice-a.md)]
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 Azure Active Directory B2C (Azure AD B2C) provides cloud identity management to keep your application, business, and customers protected. Azure AD B2C enables your applications to authenticate to social accounts, and enterprise accounts using open standard protocols. 
 
diff --git a/articles/active-directory-b2c/quickstart-web-app-dotnet.md b/articles/active-directory-b2c/quickstart-web-app-dotnet.md
@@ -18,7 +18,7 @@ ms.subservice: b2c
 
 # Quickstart: Set up sign in for an ASP.NET application using Azure Active Directory B2C
 
-[!INCLUDE [active-directory-b2c-end-of-sale-notice-a](../../includes/active-directory-b2c-end-of-sale-notice-a.md)]
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 Azure Active Directory B2C (Azure AD B2C) provides cloud identity management to keep your application, business, and customers protected. Azure AD B2C enables your applications to authenticate to social accounts and enterprise accounts using open standard protocols. 
 
diff --git a/articles/active-directory-b2c/register-apps.md b/articles/active-directory-b2c/register-apps.md
@@ -19,6 +19,7 @@ ms.subservice: b2c
 ---
 
 # Register apps in Azure Active Directory B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 Before your [applications](application-types.md) can interact with Azure Active Directory B2C (Azure AD B2C), you must register them in a tenant that you manage.
 
diff --git a/articles/active-directory-b2c/relyingparty.md b/articles/active-directory-b2c/relyingparty.md
@@ -17,6 +17,7 @@ ms.subservice: b2c
 ---
 
 # RelyingParty
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 [!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
 
diff --git a/articles/active-directory-b2c/restful-technical-profile.md b/articles/active-directory-b2c/restful-technical-profile.md
@@ -19,6 +19,7 @@ ms.subservice: b2c
 ---
 
 # Define a RESTful technical profile in an Azure Active Directory B2C custom policy
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 [!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
 
diff --git a/articles/active-directory-b2c/roles-resource-access-control.md b/articles/active-directory-b2c/roles-resource-access-control.md
@@ -17,6 +17,7 @@ ms.subservice: b2c
 
 ---
 # Roles and resource access control
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 When planning your access control strategy, it's best to assign users the least privileged role required to access resources. The following table describes the primary resources in your Azure AD B2C tenant and the most suitable administrative roles for the users who manage them.
 
diff --git a/articles/active-directory-b2c/saml-identity-provider-technical-profile.md b/articles/active-directory-b2c/saml-identity-provider-technical-profile.md
@@ -19,6 +19,7 @@ ms.subservice: b2c
 ---
 
 # Define a SAML identity provider technical profile in an Azure Active Directory B2C custom policy
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 [!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
 
diff --git a/articles/active-directory-b2c/saml-issuer-technical-profile.md b/articles/active-directory-b2c/saml-issuer-technical-profile.md
@@ -19,6 +19,7 @@ ms.subservice: b2c
 ---
 
 # Define a technical profile for a SAML token issuer in an Azure Active Directory B2C custom policy
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 [!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
 
diff --git a/articles/active-directory-b2c/saml-service-provider-options.md b/articles/active-directory-b2c/saml-service-provider-options.md
@@ -21,6 +21,7 @@ zone_pivot_groups: b2c-policy-type
 ---
 
 # Options for registering a SAML application in Azure AD B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 This article describes the configuration options that are available when you're connecting Azure Active Directory B2C (Azure AD B2C) with your Security Assertion Markup Language (SAML) application.
 
diff --git a/articles/active-directory-b2c/saml-service-provider.md b/articles/active-directory-b2c/saml-service-provider.md
@@ -21,6 +21,7 @@ zone_pivot_groups: b2c-policy-type
 ---
 
 # Register a SAML application in Azure AD B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 In this article, learn how to connect your Security Assertion Markup Language (SAML) applications (service providers) to Azure Active Directory B2C (Azure AD B2C) for authentication.
 
diff --git a/articles/active-directory-b2c/secure-api-management.md b/articles/active-directory-b2c/secure-api-management.md
@@ -18,6 +18,7 @@ ms.subservice: b2c
 ---
 
 # Secure an Azure API Management API with Azure AD B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 Learn how to restrict access to your Azure API Management API to clients that have authenticated with Azure Active Directory B2C (Azure AD B2C). Follow the instructions in this article to create and test an inbound policy in Azure API Management that restricts access to only those requests that include a valid Azure AD B2C-issued access token.
 
diff --git a/articles/active-directory-b2c/secure-rest-api.md b/articles/active-directory-b2c/secure-rest-api.md
@@ -17,6 +17,7 @@ zone_pivot_groups: b2c-policy-type
 ---
 
 # Secure APIs used for API connectors in Azure AD B2C 
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 When integrating a REST API within an Azure AD B2C user flow, you must protect your REST API endpoint with authentication. The REST API authentication ensures that only services that have proper credentials, such as Azure AD B2C, can make calls to your endpoint. This article explores how to secure REST API. 
 
