Azure AD B2C User Flow migration: password hash handling and active sessions during cutover
Migration goal I am planning to migrate a small application to a new Azure AD B2C User Flow without downtime. The documented approach of on-the-fly user import via the Microsoft Graph API, combined with a staged cutover using a new User Flow and gradual traffic redirection, looks workable in principle. Open concerns Two behaviors remain unclear to me before
passport