User and attribute mapping
Clean and map accounts, custom attributes, identifiers, consent and reconciliation rules into the target external tenant.
Azure AD B2C migration
Move to Entra External ID
without gambling the customer journey.
Azure AD B2C is no longer available to purchase for new customers. Existing estates need a deliberate transition that protects sign-in, identity data and application continuity.
A platform move and an identity migration
Custom policies, user stores, credentials, federation, application dependencies and customer communications all affect the cutover.
Migration architecture
One destination. Several interdependent transitions.
The migration plan must keep identity data, authentication and relying applications aligned at every stage.
CURRENT STATEAzure AD B2CUsers · credentials · policies · applications
01Assess
02Design
03Pilot
04Migrate
05Cut over
06Retire
TARGET STATEMicrosoft Entra External IDExternal tenant · user flows · extensions · applications
What makes it difficult
The visible login page is only the surface.
Password and sign-in continuity
Choose a credential strategy such as just-in-time or staged migration, then design fallback and recovery paths.
Custom journeys and extensions
Translate existing user flows and custom policy behaviour into supported External ID patterns and custom authentication extensions.
Protocol and integration change
Reconfigure applications, redirect URIs, claims, tokens, APIs, secrets and environments without uncontrolled downtime.
Customer identity architecture
Preserve the full customer journey, not only the account.
Registration & profile
Sign-up, progressive attributes, consent, identity verification and privacy-aware customer data.
Sign-in & recovery
Password, MFA, passkey readiness, social identity, enterprise federation and safe account recovery.
Applications & APIs
Tokens, claims, scopes, application roles, consent and downstream customer access decisions.
Credentials & relationships
Keep account identity distinct from verified evidence, delegated relationships and DiligenceID use cases.
MAITS migration method
A sequence designed for evidence, rehearsal and rollback.
Discover
Inventory tenants, policies, identity data, providers, applications, APIs and support processes.
Map
Compare B2C capability with External ID and expose unsupported or redesigned patterns.
Design
Define target journeys, data and credential migration, coexistence, telemetry and cutover.
Build
Configure the external tenant, extensions, branding, applications and migration services.
Pilot
Validate representative users, edge cases, recovery, support and operational evidence.
Migrate
Move cohorts with reconciliation, communication and controlled fallbacks.
Cut over
Shift applications and journeys using rehearsed decision points and rollback criteria.
Retire
Confirm dependencies, retention and support before decommissioning legacy components.
Decisions to make early
Avoid discovering the migration strategy during cutover.
Establish how users are matched, when credentials move, whether systems coexist, how application sessions behave and what happens when identity reconciliation fails.
MAITS brings identity architecture and delivery assurance together so customer experience, security and operational readiness are treated as one problem.
Microsoft migration guidanceMigration inventory
Expose every dependency before choosing a cutover pattern.
- Users, identifiers and credentials
- Custom and extension attributes
- User flows and custom policies
- Social and enterprise identity providers
- Applications, APIs and environments
- Token, claim and session behaviour
- Branding, consent and communications
- MFA, registration and recovery
- Bulk, staged or just-in-time migration options
- Coexistence and routing
- Rollback and reconciliation
- Legacy retirement
Start a conversation
Turn the B2C deadline into a controlled programme.
Start with an estate assessment and a migration architecture grounded in your actual policies, users and applications.