Fwrd logoFwrdDownload on the App Store

Microsoft Is Retiring SMS MFA: What Shared Admins Do Now

By Fwrd ·

Microsoft will stop sending its own SMS and voice sign-in codes for Microsoft Entra ID, the sign-in behind Microsoft 365 work and school accounts, on February 1, 2027, and on July 1, 2027 for Global Administrators and external users. After that date, anyone whose only second step is a text or a call has to register a passkey before they can sign in, unless the organization pays a telephony provider through Microsoft Security Store to keep SMS. For IT teams and MSPs that read Microsoft codes off one shared phone, that means moving those logins to their own methods, while the other vendors that still text one number can stay on it.

What you need: admin access to your Microsoft Entra tenant, and a list of the logins your team still gets a code for by text or call.

What is Microsoft retiring, and when?

Microsoft’s Learn article sets out the dates (Microsoft, read November 15, 2026):

Date What happens
September 1, 2026 Passkeys are switched on for everyone enabled for SMS or voice, and they’re nudged to register one when they next complete MFA. They can still snooze the nudge.
February 1, 2027 Microsoft stops sending SMS and voice codes for all users except Global Administrators and external users. Internal guests are in this group too.
July 1, 2027 The same happens for Global Administrators and external users.

The later date only covers an active Global Administrator role. Microsoft’s FAQ says someone who is eligible for the role through Privileged Identity Management but hasn’t activated it follows the February date (Microsoft, read November 15, 2026).

What happens when the date passes?

A user whose only MFA method is SMS or voice gets a passkey registration prompt at sign-in, and it can’t be skipped. Microsoft says there’s no opt-out from this, and that it isn’t a lockout: the user registers a passkey and carries on.

  • Password reset is included. The FAQ says the retirement applies across Entra, including self-service password reset by text or call.
  • Authenticator codes stay. Time-based codes from Microsoft Authenticator or another authenticator app are still supported after February 1, 2027, and users who use them don’t get the blocking prompt.
  • SMS can continue, for a fee. From October 30, 2026, a tenant can set up a telephony provider through Microsoft Security Store, starting with Soprano and Telesign. Users moved to it keep getting codes by text. Microsoft says pricing depends on the provider, the region and use.
  • A temporary delay exists for the nudges only. A Microsoft Graph setting holds back the September 1 passkey nudges until February 1, 2027. It doesn’t move the retirement date.

Which accounts does it cover?

Microsoft Entra ID in the public cloud, including GCC. Microsoft’s FAQ says Azure AD B2C isn’t affected, that Entra External ID gets the change next year, with its own announcement to follow, and that other cloud environments follow later. The notice is about work and school sign-ins, so check each login against it rather than assuming every Microsoft account is in scope.

How to get ready before February 1, 2027

  1. Find who still uses SMS or voice. Microsoft publishes a PowerShell script that lists them; run it with the Global Reader, Authentication Policy Administrator or Security Reader role.
  2. Move each person to a passkey in Microsoft Authenticator, a synced passkey, a security key or Windows Hello for Business. Microsoft also offers a registration campaign that prompts people at their next sign-in.
  3. Plan the shared admin logins first. A Global Administrator or client-tenant login that several technicians reached through one phone’s texts needs a new method before its date, and a passkey lives on one person’s device or credential store.
  4. Decide whether anyone truly needs SMS. If so, set up a Security Store telephony provider and move those users to it before their date.
  5. Tell people before the prompt appears. Microsoft links ready-made email and Teams announcements from its retirement article.

What it means for a shared code phone

Many IT teams and MSPs keep one office number on admin logins and choose a text code whenever someone needs in. For Microsoft 365 that ends on the dates above. Plan to have those logins off the shared number before February 1, 2027, or July 1, 2027 for an active Global Administrator.

Two things stay the same:

  • Codes from a Security Store telephony provider are still texts. If your tenant keeps SMS that way, the code still arrives on the office iPhone, and Fwrd can keep posting it to the team’s private channel.
  • Other vendors still text one number. Apple Business Manager sends admins a six-digit code by text, and many bank, carrier and vendor portals offer nothing but a text. Keep those on the office iPhone, and a shared phone number for 2FA shows the whole setup, with each code posted to a private Microsoft Teams or Slack channel.

What this change doesn’t do

  • It doesn’t stop other companies’ texts. Apple, Google, banks and other vendors set their own rules for SMS codes.
  • It doesn’t remove authenticator app codes from Microsoft Entra ID.
  • It doesn’t change Azure AD B2C tenants.
  • A forwarder can’t carry a passkey or a push approval. Fwrd forwards the words of a text message, and passkeys and Authenticator approvals aren’t texts. It can’t hear a voice call either.

Questions about Microsoft retiring SMS MFA

When does Microsoft stop sending SMS sign-in codes?

On February 1, 2027 for most Microsoft Entra ID users, including internal guests. Active Global Administrators and external users follow on July 1, 2027.

Can we keep SMS codes for Microsoft 365 after February 2027?

Yes, by paying a telephony provider through Microsoft Security Store. Setup opened on October 30, 2026, and users must be moved to the provider before their date.

Will users be locked out on the retirement date?

Microsoft says no. A user whose only method is SMS or voice must register a passkey at the prompt before signing in, and anyone with an authenticator app code or a passkey carries on as before.

Can Fwrd still forward Microsoft sign-in codes?

Only while they arrive as text messages: before the retirement date, or later through a Security Store telephony provider. Fwrd can’t forward passkeys or Authenticator approvals.

Keep the codes that still come by text in your team’s channel

Fwrd posts each new code text from an office iPhone to a private Microsoft Teams or Slack channel, with no account and no Fwrd server. Start with 15 free forwards each month.

Free for 15 forwards a month. Pro removes the limits on forwards and filters and adds a Never Forward list, with a free trial on the yearly plan for eligible customers.

Download on the App Store

iPhone · iOS 26 or later