Sending unique MFA verification codes is only one of the many ways that Azure B2C's user authentication procedures can be customized. It is easy to setup terms of usage and set up custom policies for local accounts sign-in. But a common problem is that during MFA, the custom tenant email gets delivered instead of the usual one from Microsoft. By setting up orchestration steps and claims transformations correctly and providing the verification codes via services like SendGrid, this can be fixed.

User security and flexibility are improved by integrating multiple authentication methods, such as phone, authenticator app (TOTP), and other multi-factor authentication (MFA) alternatives, into Azure AD B2C. Users can choose their preferred way thanks to the setting of bespoke XML policies and a sophisticated orchestration of user journeys that adjust dynamically based on the user's selection.