MICROSOFT 365 · WINTER DEADLINES

Three changes that can stop sign-ins, scanner email and mailbox apps

3changesbetween late December 2026 and April 1, 2027
  • Late December 2026: password-based scanner email off by default
  • February 1, 2027: Microsoft text and call codes retire
  • April 1, 2027: Exchange Web Services shuts down
Sources: Microsoft Learn; Microsoft Exchange Team Blog

The short answer: beginning February 1, 2027, Microsoft stops sending its own text-message and voice-call sign-in codes for Microsoft 365 work accounts, so anyone whose only second step is a text or call must set up a passkey (a sign-in key on a phone or security key, explained below) to keep signing in. Use the same project to fix scanners and software that send email with a mailbox password, which Microsoft switches off by default at the end of December 2026, and programs that use Exchange Web Services, which shuts down for good on April 1, 2027.

“There is no opt out from this February 1 behavior for users in scope of the February 1 retirement.” Source: Microsoft Learn, SMS and voice retirement⁠ (opens in new tab)

The Dates on One Page

This article covers your firm’s Microsoft 365 business account (Microsoft calls it a tenant), not personal Microsoft accounts.

Microsoft 365 changes in date order
DateWhat changes
September 1, 2026Passkeys became the default; text and call users may see a setup prompt they can postpone
October 2026Microsoft began turning off Exchange Web Services tenant by tenant; administrators can turn it back on until April 2027
End of December 2026Password-based sending from scanners and apps (basic authentication for SMTP AUTH) off by default in existing tenants; devices that send mail with a password stop sending
February 1, 2027Microsoft’s text and call codes retire for everyone except Global Administrators and external users; no opt-out
April 1, 2027Exchange Web Services permanently disabled; no exceptions
July 1, 2027Text and call codes retire for Global Administrators and external users
Second half of 2027Microsoft to announce when basic SMTP AUTH is removed for good

Microsoft hasn’t yet named the exact December day, so watch your Message Center, the notices page in the Microsoft 365 admin center.

Change 1: Sign-In Codes by Text or Phone Call

What breaks. Many firms set up multi-factor authentication (MFA)—the second step after a password—with codes sent by text or phone call, methods Microsoft calls “among the most vulnerable authentication methods available today.” From February 1, 2027, Microsoft’s own codes no longer complete a sign-in. People with another method, such as the Microsoft Authenticator app, use that. People with only a text or call get a prompt they can’t skip: register a passkey, or go no further. Password resets by text are covered too.

A passkey is a sign-in key kept on a phone, a computer or a hardware security key and unlocked with a face, fingerprint or PIN; the Microsoft Authenticator app can hold one. Microsoft says passkeys resist phishing and SIM-swap attacks (a criminal moving your phone number to their own phone).

Who is affected at a TPA.

  • Staff who still get codes by text or call, especially part-time, seasonal and remote staff who sign in rarely
  • Shared logins with codes going to one phone. The Department of Labor (DOL) already lists “All employees use unique, strong passwords” among its best practices.
  • Global Administrators (top-level admin accounts) and external users (guests from other organizations), who have until July 1, 2027

What to do.

  1. Have your administrator run the script Microsoft provides to list everyone still set up for text or call codes.
  2. Move each person to a passkey, starting with anyone who processes distributions.
  3. Test it on every device they use, add a backup method, then remove text and call.

Change 2: Scanners, Copiers and Software That Send Email

What breaks. Many devices and programs send email by signing in to a Microsoft 365 mailbox with its username and password, which Microsoft calls basic authentication for SMTP AUTH (SMTP is how a device hands outgoing mail to a mail server). Microsoft’s updated timeline⁠ (opens in new tab) turns it off by default in existing tenants at the end of December 2026. Devices still using it stop sending unless an administrator switches it back on, which Microsoft allows for now.

Who is affected at a TPA.

  • Copiers and scanners that “scan to email”
  • Plan administration and document software that emails notices or portal alerts through your mailboxes
  • Website forms and server or backup alerts that send through Microsoft 365
  • Devices that sign in as a shared mailbox, such as scans@. Microsoft’s shared mailbox guidance⁠ (opens in new tab) says, “Always block sign-in for the shared mailbox account and keep it blocked.”

What to do.

  1. List every device, program and form that sends email, and the mailbox each one uses.
  2. Ask each vendor about modern sign-in (OAuth, the token-based method Microsoft recommends) and switch where it’s supported.
  3. Otherwise, have your IT provider use another route Microsoft documents⁠ (opens in new tab), such as a connector tied to your office’s fixed internet address, or replace the device.
  4. Test each one before the holidays and again in early January.

Change 3: Programs That Connect to Mailboxes and Calendars

What breaks. Exchange Web Services (EWS) is an older connection programs use to read mailboxes and calendars; its replacement is Microsoft Graph. Since October 2026, Microsoft has been turning EWS off tenant by tenant after a seven-day warning in the Message Center. Your administrator (not Microsoft support) can turn it back on until April 1, 2027, when Microsoft disables it permanently; its Exchange Team Blog⁠ (opens in new tab) says there will be “no exceptions past April 2027.” Programs that depend on EWS may keep asking for a password or show an error.

Who is affected at a TPA. Microsoft lists Apple Mail and Calendar on Macs, classic Outlook for Mac, some Outlook add-ins, out-of-date Outlook for Windows and other programs such as backup software. Also check tools that file email into client folders or sync calendars. EWS on Exchange servers in your own office isn’t being retired.

What to do.

  1. Search your Message Center for “EWS has been disabled in your tenant,” and review the EWS usage report in the Microsoft 365 admin center.
  2. Ask each vendor, in writing, how its product will connect after April 1, 2027.
  3. Keep Outlook current, and move Mac users to the new Outlook for Mac.

A Short Checklist

  • Former text and call users have passkeys, tested on each device
  • Everyone has a backup sign-in and a password reset that doesn’t rely on a text
  • Every device and program that sends email is on a supported method and tested
  • No device signs in as a shared mailbox
  • EWS notices and usage are checked, and vendors have answered in writing

What We Recommend

This is TPAIT’s advice, not a Microsoft or DOL requirement.

  • Run all three as one project, with one owner and one inventory of people, devices and programs.
  • Finish passkeys by mid-January. February 1 falls in year-end work, when a blocked sign-in costs the most.
  • Choose passkeys over app codes. Microsoft says authenticator-app codes aren’t phishing-resistant.
  • Buy hardware security keys for anyone who won’t put a work app on a personal phone.
  • Treat any switch-back as a bridge, with a written reason and end date.
  • Write down each change with its date. Plan sponsor questionnaires ask about MFA, and Employee Benefits Security Administration (EBSA) investigators may ask how access is controlled. See How to Answer a Plan Sponsor Cybersecurity Questionnaire.

Why It Matters

EBSA wrote its Cybersecurity Program Best Practices⁠ (opens in new tab) “for use by recordkeepers and other service providers responsible for plan-related IT systems and data, and for plan fiduciaries making prudent decisions on the service providers they should hire.” They are best practices, not legal requirements, but EBSA investigators ask about them.

Practice 5 says “Multi-factor authentication is used wherever possible” and “Deploy phishing-resistant Multi-Factor Authentication (MFA) if possible.” Moving staff to passkeys before Microsoft forces the issue lets you show a plan sponsor what changed and when. Our DOL Cybersecurity Best Practices Guide for TPAs covers all 12 practices.

Frequently Asked Questions

Will staff be locked out on February 1, 2027?

No, but anyone whose only method is a Microsoft text or call must register a passkey before continuing; Microsoft says there is no opt-out. Staff who use the Microsoft Authenticator app or a passkey sign in as usual.

Can we keep text-message codes?

Only through a telephony provider contracted through Microsoft Security Store, an option Microsoft has offered since October 30, 2026, for organizations with a business, regulatory or technical need. It costs extra; passkeys don’t, and Microsoft recommends them.

Why might our scanner stop emailing in January?

Many scanners send mail by signing in with a mailbox password, which Microsoft turns off by default in existing tenants at the end of December 2026. An administrator can switch it back on for now, but Microsoft will announce a final removal date in the second half of 2027.

What is Exchange Web Services, and do we use it?

It’s an older connection programs use to read mailboxes and calendars. Microsoft began turning it off in October 2026 and disables it permanently on April 1, 2027. The EWS usage report in the Microsoft 365 admin center shows whether you rely on it.

Does the DOL require passkeys?

No. The DOL’s cybersecurity best practices are guidance, not legal requirements, and they don’t mention passkeys. They do say “Deploy phishing-resistant Multi-Factor Authentication (MFA) if possible,” and Microsoft describes passkeys as phishing-resistant.

Not Sure Where to Start?

In a free 30-minute assessment call, we talk through how your firm is set up today and point out what to look at first.

Book a Free Assessment Call⁠ (opens in new tab)