HOW IT WORKS
Source CIAM → IdentityBridge → Target CIAM
IdentityBridge applies a governed lifecycle to migration changes. Approval gates protect production. Every stage produces evidence.
FLAGSHIP MIGRATION PATH
Azure AD B2C Classic → Microsoft Entra External ID
IdentityBridge sits between source and target CIAM, turning discovery into governed migration decisions and evidence.
SOURCE CIAM
Azure AD B2C Classic
Applications
Users / Identities
User Flows
Custom Policies
Identity Providers
Claims
REST Integrations
Auth Configuration
IDENTITYBRIDGE ENGINE
1Discover
2Assess
3Map
4Plan
5Review
6Execute
7Validate
8Evidence
DependenciesGraph of apps, policies, IdPs & claims
Risk (SDIAMR) Scored per construct
AutomationCandidates auto-mapped
Human ReviewCustom policies & sensitive claims
Approval gatebefore material changePlan → Review → Approved → Execute
TARGET CIAM
Microsoft Entra External ID
Applications
Customer Identities
External IdPs
Attributes / Claims
Supported Journeys
Integrations
Target Configuration
IBML · IDENTITYBRIDGE MIGRATION LIFECYCLE
End-to-end migration pipeline
A single, governed flow from connection to steady-state operation. State, gates and automation are visible at every stage.
01ConnectAuthorize source & targetAssisted
02DiscoverApps, identities, policies, IdPs, claimsAutomated
03AssessCompatibility, blockers, riskAutomated
04Map & PlanTarget mappings, waves, sequencingAssisted
05Review & ApproveHuman approval before changeManual
06ExecuteControlled migration activitiesAutomated
07ValidateFunctional config verificationAutomated
08Cutover & EvidenceReadiness, results, audit trailAssisted
09OperatePost-migration monitoringAutomated
AutomationHuman reviewEvidence