Multi-Factor Sign-In Needs a Backup Plan in 2026

Multi-factor sign-in stops many stolen-password attacks, but modern fake login pages can steal an active session. Here is what adds another layer of protection.

Reviewed by Joey Garcia · CompTIA Security+ · USAF Veteran · May 10, 2026

For years the cybersecurity advice for small business owners was simple: turn on multi-factor authentication, or MFA. That is the extra code or approval after your password. Microsoft's published research showed that it blocks roughly 99% of automated password attacks.

That number is still true. The problem is the other 1%.

The attacks that bypass MFA in 2026 are no longer rare or experimental. They're commodity tools, sold as a service, run against small and mid-sized businesses every day. If you think turning on MFA in M365 four years ago is the end of your credential-security story, this post is for you.

How Basic Multi-Step Sign-In Used to Work

The classic MFA flow: you type your password, then approve a push notification on your phone or type a 6-digit code from an authenticator app. The premise is that even if an attacker steals your password, they can't approve the second factor because they don't have your phone.

For automated attacks (password-spray, credential-stuffing, brute force), this still works great. The attacker has your password from a leaked database somewhere, but the second factor stops them cold. That's the 99% Microsoft is talking about.

What an AiTM Attack Looks Like

Adversary-in-the-Middle (AiTM) phishing changes the equation. Here's the flow:

  1. You get an email. It looks legitimate. Maybe it's a "shared document" notification from a vendor, a Microsoft Teams message, or a DocuSign-style request.
  2. You click the link. It takes you to what appears to be the real Microsoft 365 login page. The URL is close enough to look right at a glance, and the page is a pixel-perfect copy.
  3. Except the page is a proxy. Behind the scenes, the attacker's server is sitting between you and the real Microsoft login page, relaying everything in real time.
  4. You enter your password. The proxy passes it to Microsoft. Microsoft prompts for MFA.
  5. You approve MFA. You typed your real password, you got a real prompt, you approved it. The proxy passes the approval to Microsoft.
  6. Microsoft issues a session token. This is the cookie that proves you're logged in. The proxy intercepts it.
  7. The attacker now has your session. They can drop your token into their own browser and they're logged in as you. No password or MFA prompt is needed, because the session is already authenticated.

The whole exchange takes seconds. You think you successfully logged in (and you did). The attacker now has access to your mailbox, files, Teams chats, and anything else your account can touch.

Why This Is Cheap and Easy Now

The technical hurdle for an attacker used to be high. You had to build a working proxy that could relay traffic without breaking the authentication flow. That's no longer true.

Open-source toolkits like Evilginx2 do all the heavy lifting. CISA's published advisories and the Microsoft Threat Intelligence team have been tracking AiTM phishing kits sold as commercial services to attackers for a few hundred dollars or less. The barrier to entry is gone.

What used to be a nation-state-level technique is now a script-kiddie capability. And small businesses are exactly the target profile: high enough value to be worth the effort, low enough sophistication to lack the defenses.

What Defenses Actually Stop AiTM

The good news: the defenses exist, they're proven, and most are within reach for a small business that's already paying for M365 Business Premium. They just have to be deployed.

1. Use Passkeys or Security Keys for Important Accounts

This is the single most effective defense, and it's not optional anymore for high-value accounts.

A FIDO2 security key (YubiKey, Feitian, etc.) or a platform passkey (built into Windows Hello, macOS, iOS, Android) does more than confirm you're approving a login. It cryptographically verifies the exact domain you're logging into. If the page is a proxy at microsoft365-login.help instead of login.microsoftonline.com , the key refuses to authenticate. Period.

This is what "phishing-resistant" actually means. Push-based MFA can be tricked. SMS codes can be tricked. Authenticator-app codes can be tricked. FIDO2 cannot, because the verification is bound to the domain.

For most small businesses, the cost is $50 to $80 for a hardware key per user, or zero if you're using platform passkeys on modern devices.

2. Conditional Access Policies

If you're on M365 Business Premium, you have Microsoft Entra ID P1 (formerly Azure AD Premium P1), and that means you have conditional access . Use it.

Specific policies that disrupt AiTM:

  • Require compliant device: If the login isn't coming from an Intune-managed device, block it or require step-up authentication. AiTM attacks usually come from an attacker's machine, which won't pass.
  • Geographic restrictions: Block sign-ins from countries you don't operate in. Most small businesses can safely block 190+ countries.
  • Risky sign-in policies (requires the Entra ID P2 add-on, which Business Premium doesn't include): Entra ID's risk engine flags impossible-travel scenarios (sign-in from Boise, then 30 minutes later from Lagos). Block or require additional verification on risk events.
  • Session controls: Set token lifetimes shorter than the default for sensitive applications, especially anything tied to financial or PII data.

3. Token Protection (Token Binding)

Microsoft offers a feature called Token Protection (sometimes called "token binding") in conditional access. When enabled, the sign-in token is cryptographically bound to the device that originally received it. If an attacker steals the token and tries to use it from their own machine, the token is rejected.

The catch: it covers supported Windows desktop apps, not browser sessions, so on its own it won't stop most browser-based AiTM cookie theft. Treat it as one layer of protection rather than a complete fix. If you're on Premium, ask your IT provider whether it makes sense for your setup.

4. Require People to Sign In Again After a Set Time

The longer a session lives, the more time an attacker has to use a stolen token. Default Microsoft session lifetimes are generous, often 90 days for refresh tokens. For sensitive applications, that's too long.

Tighten it:

  • Maximum 1 hour of inactivity before re-prompt for high-risk apps
  • Hard expiration after 8 to 12 hours regardless of activity
  • Force MFA re-verification for sensitive operations (mailbox rule changes, app consent grants, MFA method changes)

5. End-User Training That Reflects 2026 Reality

The old "look for misspellings in the URL" advice is obsolete. AiTM phishing pages are pixel-perfect. The training that matters now:

  • Always navigate to login pages directly. Never click a "log in to view this document" link. Type the URL yourself or use a saved bookmark.
  • Be suspicious of unexpected sharing notifications. A "Joey shared a document with you" message, when you don't know Joey or weren't expecting anything, is the modern click bait.
  • Report fast, even if it's messy. If someone clicks a link and types their password before they realize what happened, the next 10 minutes matter. They need to know how to report it immediately. Tokens can be revoked, sessions killed, but only if IT knows it happened.

The Cyber Insurance Connection

Cyber insurance carriers caught up to AiTM faster than most small businesses. In 2026, most renewals ask whether you have:

  • Phishing-resistant MFA on privileged accounts
  • Conditional access with risk-based policies
  • EDR with credential-theft detection

If the answers are "no" or "unsure," you're either getting denied, paying more, or excluded from coverage on credential-theft incidents. Read your policy carefully . The gap between what you think is covered and what actually pays out usually lives in the credential-theft and social-engineering exclusions.

What I'd Do Tomorrow

If you're a small business owner reading this and thinking "this might be us," here's the priority order:

  1. Enroll every admin and finance user in FIDO2 / passkey authentication. Today. The keys are $50.
  2. Audit your conditional access policies. If you've never written one beyond "require MFA," you have work to do.
  3. Shorten session token lifetimes. Default settings prioritize convenience over security.
  4. Run a phishing simulation. Specifically include AiTM-style links so your team sees what they look like.
  5. Document an incident response procedure for "user thinks they entered creds on a fake page": token revocation, session kill, password reset, mailbox rule audit.

If a token gets stolen, the cleanup gets ugly fast. Attackers usually create mailbox forwarding rules, send phishing internally to escalate, and stage data for exfiltration within minutes. Knowing how to respond is half the battle. If you're not sure where to start, I can help you respond to these incidents and harden against them.

The Honest Take

MFA is still one of the most important controls you can deploy. Don't read this post as "MFA doesn't work." It does work against the vast majority of attacks.

But the gap between "we have MFA" and "we're protected against modern credential theft" has widened. If your security posture stopped at turning on MFA in 2021, it's out of date in 2026.

The good news is the controls that close the gap are mostly already in your M365 license. You just have to deploy them.

Let's Get Your Tenant Locked Down

Want to know how exposed your business is to AiTM phishing right now? Request a free 15-minute call and we'll talk through your conditional access policies, MFA configuration, session settings, and admin-account hygiene, and where to start.

Request a Free 15-Minute Call →

You'll get a clear explanation of which protections are actually turned on in your Microsoft 365 account.

About Joey Garcia

USAF Veteran CompTIA Security+ Boise, ID

Joey Garcia is the founder of Idaho Proper IT, a Boise-area technology company serving trades, professional offices, and other small businesses. He served in the U.S. Air Force at Mountain Home AFB, holds a CompTIA Security+ certification, and has worked in IT support and administration roles since 2022. Idaho Proper IT is intentionally personal: Joey does the work himself, without handing you to a junior technician you have never met.

📞 (208) 918-0636 Free IT health check →

Share this article:

Need Help With This? Let's Talk.

Talk directly with Joey about your business technology. Start with a free 15-minute IT review.