Does depreciation of legacy MFA and SSPR affect B2C custom policy?

Question

I apologize in advance for this rudimentary question.

I am new to Azure AD and AAD B2C. I am given the task to migrate our homegrown authentication method, with the use of a third party MFA solution, to Microsoft's authentication solution. Our consumers are external users who access our varies web portals. We allow users to self-register online to create themselves their usernames and passwords. Due to the nature of our consumers and the fact that passwords in our current homegrown authentication solution are hashed, I believe AAD B2C Custom Policy with MFA is the solution, and I am working towards that direction. As a matter of fact I have downloaded the Starter Packer as well as some sample MFA policies from Github.

Recently I learned that Microsoft is going to sunset legacy MFA and SSPR and recommend migrating to Authentication Method Policy. Can someone explain to me exactly the differences between the legacy MFA and SSPR and the Authentication Method Policy. Also, does it affect, and how, what I am doing with AAD B2C Custom Policy?

Thanks,

Sam

Answer 1

Hello @Szeto, Sam , Entra ID MFA and SSPR are not being deprecated. What is being deprecated are the Legacy MFA and SSPR policies in favor of the new Authentication methods policy. AD B2C Custom Policies or User Flows do not depend on any of the aforementioned features so there won't be any impact.

Let us know if you need additional assistance. If the answer was helpful, please accept it and rate it so that others facing a similar issue can easily find a solution.