SMTP AUTH Basic Auth Is Disabled by Default in December 2026: A Readiness Checklist
At the end of December 2026, Microsoft disables Basic authentication for SMTP AUTH by default in every existing Exchange Online tenant. Printers, scanners and applications that send through smtp.office365.com with a username and password will be rejected until an admin re-enables Basic auth or moves them to another method.
If you want the full story of how Microsoft got here, read Basic Auth for SMTP Didn't End in April. This post is the practical part: how to find what will break, what each sender can move to, and how to get through the last week of December.
What Changes, and When
When Basic auth is refused, Microsoft documents this response to the sender:
550 5.7.30 Basic authentication is not supported for Client Submission
If that line shows up in a device log in January, this change is the reason.
Who Is Affected, and Who Is Not
Any device, script or application that submits mail to smtp.office365.com (port 587, or 25) and signs in with a mailbox username and password is affected. In Microsoft's reports this shows up as Basic Auth (TlsAuthLogin).
This change does not affect:
- SMTP AUTH with OAuth (
XOAUTH2). Microsoft is retiring Basic auth, not the SMTP AUTH protocol. - Mail relayed through an inbound connector to your MX endpoint, identified by IP address or certificate.
- Applications that send through Microsoft Graph.
- High Volume Email accounts, which keep accepting Basic auth until September 2028.
Tenants with Microsoft Entra ID Security Defaults turned on, or with an authentication policy that disables Basic auth for SMTP, are already blocked today. If that's you, the December change adds nothing new.
If a tenant migration or a carve-out is on the list for 2027, keep in mind that the new tenant will not accept the Basic auth logins the old one did.
The Checklist
- Run the SMTP AUTH clients report. In the Exchange admin center, go to Reports > Mail flow > SMTP AUTH clients. Widen the date range from the default 7 days to the maximum of 90 days, and export the list of senders marked Basic Auth.
- Find the source of each login. In the Microsoft Entra sign-in logs, filter on the client app Authenticated SMTP to see which IP addresses the logins come from. That usually leads you to the actual device.
- Write down each sender: the device or application, its owner, the sender address, whether it mails only internal or also external recipients, whether its vendor supports OAuth, and whether it has a static public IP address.
- Choose a path per sender. Use the comparison below. Scripts and in-house applications are usually the quickest to move.
- Plan the December bridge. For senders you cannot move in time, plan to re-enable Basic auth as narrowly as the setting allows, with a written removal date. Microsoft has not yet documented which setting this will be, so watch the Microsoft 365 Message center.
- Test and watch. After each change, send a test message and check the device log for
550 5.7.30. Re-run the report weekly until no Basic Auth senders are left.
Choosing a Path for Each Sender
| Option | Best for | Authentication | Limitations |
|---|---|---|---|
| SMTP AUTH with OAuth | Devices and apps with OAuth support; internal & external email | OAuth 2.0 token from Microsoft Entra ID | Needs firmware or software support, which many older devices will never get |
| Microsoft Graph | Scripts and in-house apps; internal & external email | OAuth 2.0 app permissions | Requires code changes; not an option for devices |
| SMTP relay with an inbound connector | Devices on your network with a static public IP, or able to present a certificate; internal & external email | Source IP address or TLS certificate | Needs outbound port 25; cannot be used from third-party hosted services such as Azure; no per-device identity or sender control |
| High Volume Email | Line-of-business apps and devices that only mail colleagues | Basic auth until September 2028, or OAuth | Internal email only, external recipients are not supported; a separate, paid service |
| Azure Communication Services Email | Applications that mail customers or suppliers; internal & external email | An Entra app registration, with its client secret as the password | Client secrets expire, so every device needs a new password on a schedule |
| On-premises Exchange Server | Organizations that still relay through one; internal & external email | Anonymous or authenticated relay on the server | Keeps a server alive just for relaying; Exchange 2016 and 2019 have been out of support since October 2025 (why that matters now) |
| Third-party SMTP relay or sending service | Devices that need any working smart host quickly; internal & external email | Usually one shared password or API key per service | Little control over who sends as whom; SPF and DKIM must be set up for the provider |
| Sendman | Devices and apps that only speak username and password, NTLM, or nothing at all; internal & external email, per policy | Existing logins validated against Microsoft Entra ID, or a Sendman credential | In private preview; devices send to Sendman instead of their old smart host |
Where Sendman Fits
In most buildings, a group of senders lands in none of the first five rows: copiers without an OAuth firmware, alarm panels, ERP exports configured years ago. Until now, the answer was the last on-premises Exchange Server.
Sendman is the SMTP relay for Microsoft 365, built for exactly those senders. If your devices send to a hostname of your own, such as the old Exchange relay, you point that hostname at Sendman, which in most cases is a single DNS record; a device set to smtp.office365.com gets Sendman's address in its settings instead. Devices that send with TLS on port 465 or 587 need nothing else, and a device that only speaks plain SMTP sends on port 25 through LNC, the Sendman tunnel.
Devices keep their logins. LOGIN and PLAIN are validated against Microsoft Entra ID: no app registration, no consent, nothing to change in your tenant. NTLM devices get a credential from Sendman's encrypted vault. Sendman then hands the mail to Exchange Online without SMTP AUTH, or to another SMTP transport service. It keeps no queue and no copy of the message.
Isn't that just Basic auth with extra steps?
No. The password never reaches the SMTP AUTH endpoint of Exchange Online, so the Basic auth retirement does not touch this path. Every connection is checked against an IP allow list before the greeting. Every identity is restricted by policy to the sender addresses and recipients you allow, and every rejection lands in a searchable event log.
Why not just any SMTP relay or sending service?
Many services will accept a device's mail. Few limit a sender to its designated from-address: with one password or API key, devices can send as anyone in your domain (support@, hr@, ...). Sendman gives each device its own identity, validated against Microsoft Entra ID or issued from its vault. That includes hybrid logins such as CONTOSO\svc-scan and NTLM, which hardly anything else in front of Microsoft 365 still speaks. With Exchange Online as the backend, Sendman doesn't rewrite the envelope or the headers; whether a message passes SPF, DKIM and DMARC is then up to Exchange Online and your domain's DNS.
Sendman is in private preview. If your senders need to keep working on January 1, use Microsoft's re-enable option as a short bridge and plan the move now.
Frequently Asked Questions
Is Microsoft removing Basic authentication for SMTP AUTH in December 2026?
Not completely. At the end of December 2026, it is disabled by default in existing Exchange Online tenants, and admins can still turn it back on. Microsoft will announce the final removal date in the second half of 2027.
Is SMTP AUTH itself being retired?
No. Only Basic authentication is being retired. SMTP AUTH with OAuth 2.0 on smtp.office365.com keeps working.
What error will a device get when Basic auth is refused?
Microsoft documents the response as:
550 5.7.30 Basic authentication is not supported for Client Submission
How do I find out which devices still use Basic auth?
Open Reports > Mail flow > SMTP AUTH clients in the Exchange admin center and set the range to 90 days. Senders marked Basic Auth (TlsAuthLogin) are affected. The Microsoft Entra sign-in logs, filtered on the client app Authenticated SMTP, show the IP addresses they connect from.
Can I turn Basic auth back on after December?
Yes, in existing tenants, until Microsoft's final removal date. As of November 2026, Microsoft has not documented which setting this will be. Tenants created after December 2026 do not have Basic auth for SMTP AUTH by default.
Can printers and scanners use OAuth instead?
Some can, usually after a firmware update. Many older printers, scanners and appliances never will, so ask the vendor for each model.
What are Microsoft's alternatives to SMTP Basic authentication?
SMTP AUTH with OAuth, Microsoft Graph, SMTP relay through an inbound connector, High Volume Email for internal recipients only, Azure Communication Services Email, and an on-premises Exchange Server in a hybrid setup. Which one fits depends on what the sender supports and whether it mails external recipients.
Does this change affect connector-based SMTP relay or Direct Send?
No. Neither uses SMTP AUTH. Direct Send has its own, separate change: Exchange Online can now reject it, which is covered in Closing Direct Send Without Silencing the Scanners.
How is Sendman different from re-enabling Basic auth?
Re-enabling Basic auth keeps passwords flowing to Exchange Online's SMTP AUTH endpoint until Microsoft's final date. With Sendman, devices keep their logins, but Exchange Online is reached without SMTP AUTH, and each identity is limited by IP range and by sender and recipient rules.
Sources
- Microsoft Exchange Team: Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline, January 27, 2026
- Microsoft Exchange Team: Exchange Online to retire Basic auth for Client Submission (SMTP AUTH), April 15, 2024, with later updates
- Microsoft Learn: Manage High Volume Email for Microsoft 365
- Microsoft Learn: Set up SMTP authentication for sending emails with Azure Communication Services
- Microsoft Learn: SMTP AUTH clients report in the new EAC in Exchange Online
- Microsoft Learn: How to set up a multifunction device or application to send email using Microsoft 365
Keep the Logins After December
Sendman is the SMTP relay for Microsoft 365, built for the senders on your list that will never learn OAuth. They keep the logins they have, validated against Microsoft Entra ID: no app registration, no consent, nothing to change in your tenant. Their mail goes into Exchange Online without SMTP AUTH, unaffected by Microsoft's Basic Authentication retirement.