MFA fatigue attacks, where users are bombarded with push notifications until they accidentally approve one, are on the rise. Microsoft Authenticator now offers two simple features that dramatically reduce this risk.
What Is It
Number Matching
- Users must enter a code shown on the login screen into their Authenticator app.
- Prevents blind approvals – if they didn’t initiate the login, they won’t know the code.
Additional Context
- Shows location and app info in the push notification.
- Helps users spot suspicious sign-in attempts.
How to Enable It
- Go to Azure AD > Security > Authentication Methods > Microsoft Authenticator
- Enable Number Matching and Additional Context for all users or targeted groups
- Test with a pilot group before rolling out org-wide
Bonus Tip
If you’re still migrating users from SMS or voice MFA, consider automated password resets for accounts flagged as high-risk. Azure AD Conditional Access can trigger this based on sign-in risk levels.
Impact
Microsoft found that enabling both features eliminated MFA fatigue attacks in live environments. It’s a low-effort, high-impact win, especially for orgs already using Microsoft 365.