Microsoft mfa5/27/2023 Later in 2024 we’ll be deprecating the ability to manage authentication methods in the legacy policies. The control lets you move and test methods individually, before having to disable methods in the legacy policies. We’ve also added a migration control to help you migrate methods from the legacy MFA and self-service password reset policies to the authentication methods policy. This means you can perform actions like trial methods with pilot groups and limit lower security methods like SMS and Voice to smaller groups of users. Methods can now be managed more granularly, with the option to enable them for specific groups of users instead of all users and the ability to exclude groups of users from being targeted. Newly added methods include SMS, Voice Calls, Third-party Software OATH, and Email OTP. Now, they can both be managed in one policy alongside passwordless methods like FIDO2 security keys and certificate-based authentication. Historically, methods had to be managed separately for MFA and self-service password reset. The Public Preview of modern MFA Fraud Alert brings the configuration into the authentication methods policy and integrates this user-reported signal of suspicious MFA prompts with Identity protection. The General Availability of Converged Authentication Methods allows all methods used for authentication and password reset to be centrally managed and with more control, providing the ability to target groups of users. We’re thrilled to announce two key updates to how you manage your authentication experiences! The General Availability of Converged Authentication Methods and Public Preview of a modernized version of multifactor authentication (MFA) Fraud Alert.
0 Comments
Leave a Reply. |