In this guide
MFA greatly reduces the risk of account compromise, but not all MFA methods are equally resistant to phishing. Passkeys/FIDO2 and other phishing-resistant methods, combined with Conditional Access, managed devices and token protection where supported, provide a stronger access model than a basic push notification or OTP.
Why conventional MFA can be bypassed
In adversary-in-the-middle attacks, a user may be directed to a fake sign-in page that relays a genuine authentication flow and attempts to steal credentials or session tokens. The attacker is trying to steal the result of successful authentication, rather than simply preventing MFA from working.
This is why modern security guidance emphasises phishing-resistant authentication and defence in depth.
What phishing-resistant MFA means
Methods such as FIDO2/passkeys and Windows Hello for Business use cryptographic credentials tied to the genuine website and/or device. They do not ask users to enter a one-time code on a page that may be fake.
Microsoft recommends phishing-resistant authentication particularly for privileged and administrator accounts, and supports a phased rollout through Authentication Strengths and Conditional Access.
Conditional Access decides when access is allowed
Identity is one signal. It can be combined with device status, location and risk signals, the application and the user’s role. A business can, for example, require a stronger method for administrators or access to sensitive resources.
A sound implementation starts in report-only or pilot mode and includes emergency or break-glass accounts so that an incorrect policy does not lock out all administrators.
After sign-in: protecting session tokens
Even with strong authentication, attackers target token theft. Microsoft offers Token Protection for supported scenarios to bind certain tokens to the device on which they were issued. It is not a universal solution and should be part of an overall endpoint and identity security policy.
A practical upgrade plan
- Start with administrators and other high-risk accounts.
- Record current MFA methods and legacy applications.
- Enable phishing-resistant methods for a pilot group.
- Test Conditional Access in report-only mode before enforcement.
- Maintain controlled emergency access accounts.
- Connect identity policy with endpoint compliance and monitoring.
Frequently asked questions
Is SMS MFA secure?
It is better than password-only access, but is not considered phishing-resistant. Stronger methods such as passkeys/FIDO2 or Windows Hello for Business are preferred for more critical accounts, depending on the environment.
What is a passkey?
It is a credential based on public-key cryptography. Users can sign in without a traditional password, and the credential is designed to resist use on a phishing site.
Should I enable Conditional Access for everyone immediately?
Not without a pilot. Access policies should be tested gradually, using report-only mode where available and an emergency access plan.
Related services and guides
Discuss your next step with UniLoud
Request a review of your current Microsoft 365 access. We will map MFA methods, privileged accounts, Conditional Access and devices before proposing gradual improvements.
