Adding include

garrodonnell · garrodonnell · commit aae798bbc035 · 2025-04-30T18:55:23.000+01:00
diff --git a/articles/active-directory-b2c/tenant-management-directory-quota.md b/articles/active-directory-b2c/tenant-management-directory-quota.md
@@ -20,6 +20,7 @@ ms.subservice: b2c
 ---
 
 # Manage directory size quota of your Azure Active Directory B2C tenant
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 It's important that you monitor how you use your Azure AD B2C directory quota. Directory quota has a size that's expressed in number of objects. These objects include user accounts, app registrations, groups, etc. When the number of objects in your tenant reach quota size, the directory will generate an error when trying to create a new object.
 
diff --git a/articles/active-directory-b2c/tenant-management-emergency-access-account.md b/articles/active-directory-b2c/tenant-management-emergency-access-account.md
@@ -19,6 +19,7 @@ ms.subservice: b2c
 ---
 
 # Manage emergency access accounts in Azure Active Directory B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 It's important that you prevent being accidentally locked out of your Azure Active Directory B2C (Azure AD B2C) organization because you can't sign in or activate another user's account as an administrator. You can mitigate the impact of accidental lack of administrative access by creating two or more *emergency access accounts* in your organization.
 
diff --git a/articles/active-directory-b2c/tenant-management-manage-administrator.md b/articles/active-directory-b2c/tenant-management-manage-administrator.md
@@ -17,6 +17,7 @@ ms.subservice: b2c
 ---
 
 # Manage administrator accounts in Azure Active Directory B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 In Azure Active Directory B2C (Azure AD B2C), a tenant represents your directory of consumer, work and guest accounts. With an administrator role, work and guest accounts can manage the tenant.  
 
diff --git a/articles/active-directory-b2c/tenant-management-read-tenant-name.md b/articles/active-directory-b2c/tenant-management-read-tenant-name.md
@@ -19,6 +19,7 @@ ms.subservice: b2c
 ---
 
 # Find tenant name and tenant ID in Azure Active Directory B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 When you create an Azure Active Directory B2C (Azure AD B2C) for your organization, it's assigned a default domain name (name) and a directory (tenant) ID. The tenant ID is same as the organization ID. 
 
diff --git a/articles/active-directory-b2c/threat-management.md b/articles/active-directory-b2c/threat-management.md
@@ -18,6 +18,7 @@ ms.subservice: b2c
 ---
 
 # Mitigate credential attacks in Azure AD B2C with smart lockout
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 Credential attacks lead to unauthorized access to resources. Passwords that are set by users are required to be reasonably complex. Azure AD B2C has mitigation techniques in place for credential attacks. Mitigation includes detection of brute-force credential attacks and dictionary credential attacks. By using various signals, Azure Active Directory B2C (Azure AD B2C) analyzes the integrity of requests. Azure AD B2C is designed to intelligently differentiate intended users from hackers and botnets.
 
diff --git a/articles/active-directory-b2c/tokens-overview.md b/articles/active-directory-b2c/tokens-overview.md
@@ -19,6 +19,7 @@ ms.custom: b2c-support
 ---
 
 # Overview of tokens in Azure Active Directory B2C
+[!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) emits different types of security tokens as it processes each [authentication flow](application-types.md). This article describes the format, security characteristics, and contents of each type of token.
 
diff --git a/articles/active-directory-b2c/troubleshoot-with-application-insights.md b/articles/active-directory-b2c/troubleshoot-with-application-insights.md
@@ -16,6 +16,7 @@ zone_pivot_groups: b2c-policy-type
 ---
 
 # Collect Azure Active Directory B2C logs with Application Insights
+[!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/troubleshoot.md b/articles/active-directory-b2c/troubleshoot.md
@@ -20,6 +20,7 @@ zone_pivot_groups: b2c-policy-type
 ---
 
 # Troubleshoot Azure AD B2C custom policies and user flows
+[!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/trustframeworkpolicy.md b/articles/active-directory-b2c/trustframeworkpolicy.md
@@ -18,6 +18,7 @@ ms.subservice: b2c
 ---
 
 # TrustFrameworkPolicy
+[!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/tutorial-create-user-flows.md b/articles/active-directory-b2c/tutorial-create-user-flows.md
@@ -15,6 +15,7 @@ zone_pivot_groups: b2c-policy-type
 ---
 
 # Tutorial: Create user flows and custom policies 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/tutorial-delete-tenant.md b/articles/active-directory-b2c/tutorial-delete-tenant.md
@@ -18,6 +18,7 @@ ms.subservice: b2c
 ---
 
 # Clean up resources and delete the tenant
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 When you've finished the Azure Active Directory B2C (Azure AD B2C) tutorials, you can delete the tenant you used for testing or training. To delete the tenant, you'll first need to delete all tenant resources. In this article, you'll:
 
diff --git a/articles/active-directory-b2c/tutorial-register-applications.md b/articles/active-directory-b2c/tutorial-register-applications.md
@@ -15,6 +15,7 @@ ms.subservice: b2c
 ---
 
 # Tutorial: Register a web application 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), they must be registered in a tenant that you manage. This tutorial shows you how to register a web application using the Azure portal. 
 
diff --git a/articles/active-directory-b2c/tutorial-register-spa.md b/articles/active-directory-b2c/tutorial-register-spa.md
@@ -20,6 +20,7 @@ ms.subservice: b2c
 ---
 
 # Register a single-page application 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), they must be registered in a tenant that you manage. This guide shows you how to register a single-page application ("SPA") using the Azure portal.
 
diff --git a/articles/active-directory-b2c/user-flow-overview.md b/articles/active-directory-b2c/user-flow-overview.md
@@ -15,6 +15,7 @@ ms.subservice: b2c
 ---
 
 # User flows and custom policies overview
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 In Azure AD B2C, you can define the business logic that users follow to gain access to your application. For example, you can determine the sequence of steps users follow when they sign in, sign up, edit a profile, or reset a password. After completing the sequence, the user acquires a token and gains access to your application. 
 
diff --git a/articles/active-directory-b2c/user-flow-versions-legacy.md b/articles/active-directory-b2c/user-flow-versions-legacy.md
@@ -18,6 +18,7 @@ ms.subservice: b2c
 ---
 
 # Legacy user flow versions in Azure Active Directory B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 > [!IMPORTANT]
 > This article describes the legacy versioning method for user flows, which offers V1 (production-ready) versions, and V1.1 and V2 (preview) versions of user flows. Environments other than the Azure public cloud will continue to use this legacy versioning method. In the Azure public cloud, this method being replaced by [new **Recommended** and **Preview** versions](user-flow-versions.md).
diff --git a/articles/active-directory-b2c/user-flow-versions.md b/articles/active-directory-b2c/user-flow-versions.md
@@ -18,6 +18,7 @@ ms.subservice: b2c
 ---
 
 # User flow versions in Azure Active Directory B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 User flows in Azure Active Directory B2C (Azure AD B2C) help you to set up common [policies](user-flow-overview.md) that fully describe customer identity experiences. These experiences include sign-up, sign-in, password reset, or profile editing. The tables below describe the user flows that are available in Azure AD B2C.
 
diff --git a/articles/active-directory-b2c/user-migration.md b/articles/active-directory-b2c/user-migration.md
@@ -17,6 +17,7 @@ ms.subservice: b2c
 
 ---
 # Migrate users to Azure AD B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 Migrating from another identity provider to Azure Active Directory B2C (Azure AD B2C) might also require migrating existing user accounts. Two migration methods are discussed here, *pre migration* and *seamless migration*. With either approach, you're required to write an application or script that uses the [Microsoft Graph API](microsoft-graph-operations.md) to create user accounts in Azure AD B2C.
 
diff --git a/articles/active-directory-b2c/user-overview.md b/articles/active-directory-b2c/user-overview.md
@@ -14,6 +14,7 @@ ms.custom: b2c-support
 ---
 
 # Overview of user accounts in Azure Active Directory B2C
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 In Azure Active Directory B2C (Azure AD B2C), there are several types of accounts that can be created. These account types are shared across Microsoft Entra ID, Microsoft Entra B2B, and Azure Active Directory B2C (Azure AD B2C).
 
diff --git a/articles/active-directory-b2c/user-profile-attributes.md b/articles/active-directory-b2c/user-profile-attributes.md
@@ -16,6 +16,7 @@ ms.custom: b2c-support
 ---
 
 # User profile attributes
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 Your Azure Active Directory B2C (Azure AD B2C) directory user profile comes with a set of built-in attributes, such as given name, surname, city, postal code, and phone number. You can extend the user profile with your own application data without requiring an external data store.
 
diff --git a/articles/active-directory-b2c/userinfo-endpoint.md b/articles/active-directory-b2c/userinfo-endpoint.md
@@ -20,6 +20,7 @@ zone_pivot_groups: b2c-policy-type
 ---
 
 # UserInfo endpoint
+[!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/userjourneys.md b/articles/active-directory-b2c/userjourneys.md
@@ -17,6 +17,7 @@ ms.subservice: b2c
 ---
 
 # UserJourneys
+[!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/validation-technical-profile.md b/articles/active-directory-b2c/validation-technical-profile.md
@@ -19,6 +19,7 @@ ms.subservice: b2c
 ---
 
 # Define a validation 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/view-audit-logs.md b/articles/active-directory-b2c/view-audit-logs.md
@@ -20,6 +20,7 @@ ms.custom: fasttrack-edit
 ---
 
 # Accessing Azure AD B2C audit logs
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 [!INCLUDE [active-directory-b2c-limited-to-custom-policy](../../includes/active-directory-b2c-public-preview.md)]
 
diff --git a/articles/active-directory-b2c/whats-new-docs.md b/articles/active-directory-b2c/whats-new-docs.md
@@ -14,6 +14,7 @@ manager: CelesteDG
 ---
 
 # Azure Active Directory B2C: What's new
+[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
 
 Welcome to what's new in Azure Active Directory B2C documentation. This article lists new and significantly updated docs from the past three months. To learn what's new with the B2C service, see [What's new in Microsoft Entra ID](../active-directory/fundamentals/whats-new.md), [Azure AD B2C developer release notes](custom-policy-developer-notes.md) and [What's new in Microsoft Entra External ID](/entra/external-id/whats-new-docs).
 
