Migrate a B2B SaaS email-change flow only when the replacement preserves proof of the new address, notification to the old address, and a separate path for containing a stolen session. An account update alone does not establish that boundary.
TL;DR: Start the change, send confirmation to the new address, notify the old address, and complete the change on confirmation. Then re-verify the account state before refreshing downstream caches. Keep refresh-token rotation and session revocation as explicit security decisions; a successful email change is not evidence that either occurred.
This architecture decision record evaluates migration off a managed identity provider through the evidence the application must retain. Infrai offers a single key and one bill through a unified REST API, with no SDK required. For an identity-and-notification handoff, that means fewer credentials and integration contracts to operate; public discovery schemas also help review the adapter.…