Azure AD B2C

TEST - tenant.onmicrosoft.com - custom policy files

Template listing the custom policy files that make up the User Journeys in the TEST environment.

On this page

Introduction

The Identity Experience Framework uses custom policies, which are very flexible and configurable building blocks. Current User Journeys were designed, developed and implemented with custom policies and they are the foundation of the Identity platform.

All User Journeys have been configured for tenant-wide Single Sign-On support.

Tip

All implementations use the custom domain functionality.

When using custom domain, {tenantName}.b2clogin.com, in the examples, can be replaced with the domain name.

Both domains are active and functioning, but use one at a time as Single Sign-On does not work across different domains.

v1 policies

Policies in the v1 file set are the ones recommended to use for application integration.

Policy fileUser JourneyDescriptionMetadata endpointUser Journey test linkCustom domain
b2c_1a_v1_signupsigninSign inThe primary (default) User Journey, sign in with email and password resethttps://custom.domain.com/tenantname.onmicrosoft.com/v2.0/.well-known/openid-configuration?p=b2c_1a_v1_signupsignin https://tenantname.b2clogin.com/tenantname.onmicrosoft.com/v2.0/.well-known/openid-configuration?p=b2c_1a_v1_signupsigninSign Incustom.domain.com tenantname.b2clogin.com
------

v2 policies?

Policies deployed through Managed B2C pipelines.

Policy fileUser JourneyDescriptionMetadata endpointUser Journey test linkCustom domain

| | | | | | |

Foundational policy files

Policy fileDescription
b2c_1a_v1_baseTrust Framework Policy base containing all building blocks and definitions necessary for the User Journeys
b2c_1a_v1_base_extensionsTrust Framework Policy base extensions holding all the User Journeys
Last updated 2 November 2026 Edit this page on GitHub
Esc