Hello @Anonymous ,
It seems that you have implemented a password reset policy in Azure B2C, but after the password reset flow is completed, it auto logs in the user. If the user has MFA enabled, it skips the MFA <sup>12</sup>. You want the policy to not bypass MFA after the password reset is complete and before it logs in the user <sup>2</sup>.
The default behavior of the password reset flow using SignUp-SignIn policies is that it will enter the email and password and confirm the new password <sup>2</sup>. If you have MFA enabled, this is the default behavior and a known issue <sup>2</sup>. However, you can try disabling the MFA enforcement on the Password reset user flow in your Azure AD B2C directory <sup>3</sup>.
If you want to enforce MFA after the password reset is complete, you can try adding a new step to the user flow that requires MFA authentication before logging in the user <sup>2</sup>. You can also try configuring the self-service password reset experience for the Sign in (Recommended) or Sign up and sign in (Recommended) user flows <sup>1</sup>. When the user selects the Forgot your password? link, they are immediately sent to the Forgot Password experience. Your application no longer needs to handle the AADB2C90118 error code, and you don’t need a separate policy for password reset <sup>1</sup>.
I recommend checking out this Microsoft Learn article for more information on setting up a password reset flow in Azure Active Directory B2C <sup>1</sup>. It provides a detailed flow chart that goes through all the possible scenarios when the logic app is giving TLS error and provides solutions for each scenario.
I hope this helps you resolve your issue!