Changing user authentication methods for Microsoft Entra Multi-Factor Authentication MFA | Microsoft

In this video tutorial from Microsoft, you will receive an overview of the new Microsoft Entra authentication method policy and how it works with the legacy MFA and SSPR policies. You will also learn how to migrate from SMS and phone authentication methods to the Microsoft Authenticator method.

Azure Active Directory is now Microsoft Entra ID, all other Azure Active Directory branded products are now “Microsoft Entra”. Any reference to Azure Active Directory within this video should be replaced with Microsoft Entra or Microsoft Entra ID as applicable.

[LV]

Thank you for the informative guide.

Currently, in my organization, MFA is enabled only for specific privileged accounts via CA, while the vast majority of non-privileged accounts do not have it enabled.
Additionally, SSPR is disabled (never was enabled)

If I do this migration from legacy MFA to the Authentication Methods policy, will it impact non-privileged accounts who never had MFA enabled? Moreover, will this migration mandate/enforce MFA for users on whom CA isn't applying it onto?

[NicoPost]

Thank you for sharing this video, but for me it does not work.
All is disabled in legacy MFA and SSPR and I did all my settings in the new "Authentication methods" pages even completed the migration to "Migration complete".
But when I test it my user will login without a MFA and is able to open webmail and SharePoint.

The crazy thing is, after logging in and you go to ''view account'' and choose "security info", then the MFA is needed to be configured.
(And even then a new incognito login will not ask for MFA)

Can you tell me why?

[nonesuchtofu]

what about using a speaker that is actually understandable??

[argetlam]

Volume is way to low and voice is clipping.