AI Phishing Changed the Rules for Your Employeesour Employees Were Trained to Spot Bad Phishing Emails. AI Just Changed the Rules.
If Your Business Got Hacked, What Would Still Work?If Your Business Got Hacked Tomorrow, What Would Still Work?
Your MFA Might Be Outdated. Microsoft Is Moving On

Your MFA Might Be Outdated. Microsoft Is Already Moving On.

You turned on MFA like everyone told you to. Now the type of MFA matters.

For years, one of the most common pieces of cybersecurity advice for businesses has been simple:

Turn on multi-factor authentication.

And that was good advice.

If an attacker steals an employee’s password, MFA puts another barrier between that attacker and the account.

But cybersecurity doesn’t stand still.

Attackers have become better at stealing authentication codes, tricking users into approving fraudulent login attempts, and building convincing phishing pages designed specifically to get around older forms of MFA.

Now Microsoft is making a significant change.

As of September 1, 2026, Microsoft Entra ID has begun moving eligible users who rely on SMS or voice authentication toward passkeys.

And another important deadline is coming.

For most affected users, Microsoft-provided SMS and voice authentication will be retired on February 1, 2027.

If your business uses Microsoft 365, this is something you should be looking at now.

Wait. Isn’t MFA Supposed to Be Secure?

Yes.

Using MFA is generally much safer than protecting an account with only a username and password.

But not every form of MFA provides the same level of protection.

Consider a typical text-message login.

You enter your password.

Microsoft sends a six-digit code to your phone.

You type the code into the website.

You now have two factors:

  1. Something you know, your password.
  2. Something you have, access to your phone number.

That’s significantly better than a password alone.

But there is still a problem.

That six-digit code can be stolen.

Attackers Learned How to Phish MFA Too

Imagine an employee receives an email that looks like a legitimate Microsoft 365 security notification.

They click a link.

The page looks exactly like Microsoft’s login page.

They enter their username and password.

Then Microsoft sends them an MFA code.

The fake website asks for that code too.

The employee enters it.

The attacker can potentially capture the credentials and authentication information needed to complete the fraudulent login.

From the employee’s perspective, everything looked normal.

They entered their password.

They received the expected security code.

They entered the code.

That’s why simply telling employees, “We have MFA, so we’re protected,” creates a false sense of security.

The method matters.

Why Microsoft Is Moving Toward Passkeys

Microsoft is making passkeys the default authentication experience in Entra ID because passkeys are designed to resist phishing.

Instead of relying on a password or a temporary code that someone can type into a fake website, passkeys use public-key cryptography.

Here’s the important part for a business owner:

There isn’t a reusable password or six-digit SMS code for an employee to accidentally hand to an attacker.

The passkey is also tied to the legitimate website or service.

That makes the fake-login-page trick much harder to pull off.

Microsoft describes passkeys as phishing-resistant by design and recommends organizations move users to passkeys or another phishing-resistant authentication method.

What Exactly Is Changing?

Microsoft’s transition is happening in stages.

September 1, 2026: The Transition Began

Starting September 1, users enabled for SMS or voice authentication in affected Microsoft Entra ID environments began being automatically enabled for passkeys.

Those users can be prompted to register a passkey when they perform an MFA sign-in.

So if employees have recently started seeing Microsoft prompts about setting up a passkey, those prompts may be part of this transition.

February 1, 2027: A Much Bigger Change

Beginning February 1, 2027, Microsoft-provided SMS and voice authentication will be retired for most affected Entra ID users.

This does not mean Microsoft 365 suddenly stops working for everyone who once used a text message for MFA.

But organizations need to make sure affected users have an appropriate authentication method configured.

If an affected user’s only available MFA method is Microsoft’s SMS or voice service after the retirement date, Microsoft says that user will be required to register a passkey before continuing to sign in.

That registration prompt becomes mandatory.

July 1, 2027: Global Administrators and External Users

Microsoft has provided a later deadline for Global Administrators and external users.

Microsoft-provided SMS and voice authentication for those users is scheduled to retire on July 1, 2027.

Internal guest users remain part of the February 1 timeline.

The important takeaway isn’t memorizing every exception.

It’s recognizing that Microsoft’s authentication strategy has changed.

Does This Mean SMS MFA Is Useless?

No.

This is where cybersecurity discussions can become misleading.

SMS MFA is still better than having no MFA at all.

If the choice today is between:

Password only

or

Password + SMS MFA

use the MFA.

But businesses shouldn’t confuse “better than nothing” with “best available protection.”

SMS and voice authentication have weaknesses that stronger authentication methods are designed to address.

Microsoft itself now describes SMS and voice as significantly weaker against phishing and account compromise than passkeys.

The goal should be to move toward stronger authentication rather than turning MFA off.

What Is Phishing-Resistant MFA?

The name sounds complicated.

The concept isn’t.

Traditional MFA often asks an employee to prove their identity by providing something that can potentially be copied, intercepted, or socially engineered.

Phishing-resistant authentication is designed so that the employee doesn’t have a secret code they can simply hand over to an attacker.

Examples supported by Microsoft’s ecosystem include:

  • Passkeys
  • Windows Hello for Business
  • FIDO2 security keys

These methods can provide substantially stronger protection against credential phishing than passwords combined with SMS codes.

The Guide to Better IT Service, Security, and Compliance

Get a clear, practical framework for evaluating IT providers. Learn the warning signs, security essentials, and key questions to ask before choosing a Managed IT partner.

What Does a Passkey Look Like for an Employee?

For the employee, passkeys can actually make signing in easier.

Depending on the device and configuration, an employee may authenticate using:

  • A fingerprint
  • Facial recognition
  • A device PIN
  • A hardware security key
  • Another supported passkey-enabled device

The complicated cryptography happens behind the scenes.

The employee doesn’t need to understand public and private keys.

They simply need to know how they’re expected to sign in.

That’s why planning the rollout matters.

Don’t Wait Until January to Figure This Out

A common mistake with Microsoft 365 security changes is waiting until employees start complaining that something changed.

That’s not a migration strategy.

Before the 2027 deadline, businesses using Microsoft Entra ID should know:

1. Who Is Still Using SMS or Voice?

Start with an inventory.

Which employees are currently configured to use SMS or voice authentication?

Which accounts have stronger methods already configured?

You can’t plan a transition if you don’t know who is affected.

2. Which Authentication Method Will Replace It?

For many businesses, passkeys will be the logical direction.

Other organizations may already use Windows Hello for Business, FIDO2 security keys, or another appropriate authentication strategy.

The right answer depends on your environment.

3. Are Your Employees Ready?

A technical change without employee communication creates support calls.

If employees suddenly see a new registration prompt and nobody has told them why, some will ignore it.

Others may assume it is phishing.

That’s particularly ironic when the purpose of the change is improving phishing protection.

Tell employees what’s changing before it changes.

4. Have You Tested the Process?

Don’t roll out a major authentication change to everyone at once without testing it.

Start with a smaller group.

Test registration.

Test normal sign-in.

Test new devices.

Test account recovery.

Find the problems while they affect five people instead of fifty.

5. What Happens When Someone Loses a Device?

Security isn’t just about keeping attackers out.

You also need to make sure legitimate employees can get back in.

What happens if an employee loses a phone?

Gets a new laptop?

Replaces a device?

Leaves the company?

Works remotely?

Your authentication policy needs an account recovery process that doesn’t undermine the stronger security you’re trying to implement.

What If Your Business Still Needs SMS?

Microsoft isn’t completely eliminating the possibility of SMS or voice authentication.

Organizations with legitimate regulatory, technical, or operational reasons to continue using those methods can use supported third-party telephony providers through the Microsoft Security Store.

But that should be a deliberate decision, not something that happens because nobody reviewed the Microsoft 365 configuration.

For most organizations, Microsoft’s recommended direction is clear:

Move users toward passkeys or another phishing-resistant authentication method.

MFA Was Step One. Identity Security Is the Bigger Picture.

This Microsoft change highlights something businesses often miss.

Cybersecurity isn’t a checklist you complete once.

A business may have turned on MFA three years ago and reasonably believed the job was finished.

It wasn’t.

Attackers adapted.

Technology improved.

Security recommendations changed.

Now the question isn’t simply:

“Do we have MFA?”

The better question is:

“Are we using the right authentication methods for the threats we’re facing today?”

That same thinking should apply throughout your Microsoft 365 environment.

Who has administrator privileges?

Are old employee accounts still active?

Are risky sign-ins being monitored?

Are employees using legacy authentication methods?

Are permissions appropriate?

Are account recovery procedures secure?

Authentication is one part of a much larger identity security strategy.

February 2027 Isn’t That Far Away

February can sound distant when you’re looking at the calendar in October.

It isn’t.

Authentication changes affect employees, devices, policies, account recovery, onboarding, offboarding, and help-desk procedures.

Businesses have time to prepare.

The key is using that time.

Start by identifying which authentication methods your organization currently uses.

Then determine which users need to transition and begin testing before the deadline gets close.

Because the worst time to discover that your company’s authentication strategy is outdated is when an employee can’t sign in.

Or when an attacker can.

Is Your Microsoft 365 Security Ready for What’s Next?

CNS can help review your Microsoft 365 and Entra ID environment, identify outdated authentication methods, evaluate MFA and passkey readiness, review account security, and build a practical transition plan for your organization.

You don’t need to wait until Microsoft’s deadline forces the conversation.

Contact CNS to review your Microsoft 365 security and make sure your authentication strategy is ready for 2027.

Let's Talk IT! (916) 866-9969