MFA related data migration best practice?

We have a database contains MFA related user-data (phone number, verified phone number, email1, email2, …)

In the following case, please tell me how to setup using custom database with MFA enabled

  • User can choose to use phone or email for MFA
  • Phone number and verified phone number can be different

We want to modify the least possible so we’re exploring as many options as we can

Hello @quanlm,

Thank you for reaching out to us!
Just wanted to emphasize that Email is not considered a high security MFA factor, but if this scenario suits your use case, you can enable the required factors on your tenant and toggle on Show Multi-factor Authentication options as described in the doc. This should work on it’s own if you do not require a more customize behavior for user login.

Regarding your mention of using both phone number and verified phone number, I am not entirely sure regarding the use case for these two distinctly, but this separation could be implemented using Actions to determine the MFA behavior.

Best regards,
Gerald

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.