
Printers that scan to email, backup jobs that send reports, monitoring alerts, old line-of-business apps: a lot of them still send mail through Exchange Online with SMTP AUTH and Basic authentication, meaning a plain username and password. Microsoft is switching that off. When it happens, those emails just stop, and nobody notices until an invoice or an alert goes missing.
Here is the current timeline, how to find what still depends on it in your tenant, and what to move each device to. This is the checklist I would work through.
Quick answer
Basic authentication for SMTP AUTH keeps working until the end of December 2026. Then Microsoft turns it off by default for existing tenants (admins can switch it back on for a while), and new tenants will not get it at all. A final removal date is due in the second half of 2027. Find your senders with the SMTP AUTH clients report, then move printers to a connector-based relay and apps to OAuth.
The timeline (updated January 2026)
| When | What happens |
|---|---|
| Now until December 2026 | No change. SMTP AUTH with Basic authentication works as before. |
| End of December 2026 | Disabled by default for all existing tenants. Admins can re-enable it temporarily. |
| Tenants created after December 2026 | No Basic SMTP AUTH by default. OAuth is the supported option. |
| Second half of 2027 | Microsoft announces the final retirement date. |
Microsoft originally planned to start in March 2026 and pushed it back, so if you read an older article with the earlier dates, this table is the current plan. SMTP AUTH itself is not going away, only the Basic authentication part. Apps that sign in to SMTP with OAuth keep working.
What usually breaks
- Multifunction printers and scanners with scan-to-email
- Backup software, NAS boxes and UPS units sending status emails
- Monitoring tools such as Zabbix, PRTG or Uptime Kuma
- Old business apps, ERP or accounting systems sending invoices
- PowerShell scripts using
Send-MailMessagewith a stored password
Step 1: Find everything that still uses it
The report: in the Exchange admin center, open Reports > Mail flow > SMTP AUTH clients report. It shows which accounts send through SMTP AUTH and how much. That list is your to-do list.
PowerShell: connect to Exchange Online and check where SMTP AUTH is allowed:
Connect-ExchangeOnline
# Organization-wide setting (True means SMTP AUTH is off for the tenant)
Get-TransportConfig | Format-List SmtpClientAuthenticationDisabled
# Mailboxes where SMTP AUTH is explicitly turned on
Get-CASMailbox -ResultSize Unlimited |
Where-Object { $_.SmtpClientAuthenticationDisabled -eq $false } |
Select-Object DisplayName, PrimarySmtpAddress
Sign-in logs: in the Microsoft Entra admin center, filter sign-in logs by Client app = Authenticated SMTP to see the devices and IP addresses behind each account.
Step 2: Pick a replacement for each sender
| Sender | Best replacement | Notes |
|---|---|---|
| Printers and scanners in the office | SMTP relay with a connector | Exchange Online accepts mail from your office public IP on port 25. No password stored on the device. |
| Apps that support modern auth | SMTP AUTH with OAuth | Register an app in Entra ID and use client credentials. Many current backup and monitoring tools support it. |
| Devices that only email staff | Direct Send | Sends to your MX record on port 25, internal recipients only. Check that Reject Direct Send is not enabled. |
| Apps sending to customers in bulk | Azure Communication Services Email | Built for application mail at volume. |
| PowerShell scripts | Microsoft Graph sendMail | Send-MailMessage is obsolete. Use Graph with an app registration. |
Step 3: Migrate in small batches
- Start with low-risk senders, such as one printer, and confirm mail still arrives.
- For each account you move, turn SMTP AUTH off on that mailbox:
Set-CASMailbox -Identity scanner@company.com -SmtpClientAuthenticationDisabled $true - Watch the SMTP AUTH clients report until it is empty.
- Then disable it for the whole tenant:
Set-TransportConfig -SmtpClientAuthenticationDisabled $true
Doing this before December means you choose the day things change, instead of Microsoft choosing it for you.
Why Microsoft is doing this
A username and password sent to SMTP cannot use MFA or Conditional Access, so a leaked password for a scanner mailbox is enough to send phishing from your domain. Password spray attacks against SMTP AUTH are common. Removing Basic authentication closes one of the last easy ways in.
Related: troubleshooting SSO authentication failures and running a self-hosted newsletter with proper SPF, DKIM and DMARC.
Frequently asked questions
When will SMTP AUTH Basic authentication stop working in Exchange Online?
Microsoft disables it by default for existing tenants at the end of December 2026. Admins can re-enable it temporarily after that, and the final removal date will be announced in the second half of 2027.
Is SMTP AUTH being removed completely?
No. Only Basic authentication, a plain username and password, is being retired. SMTP AUTH with OAuth tokens continues to work.
How do I find devices that use SMTP AUTH?
Use the SMTP AUTH clients report under Reports, Mail flow in the Exchange admin center, and filter Entra ID sign-in logs by the Authenticated SMTP client app.
What should printers use instead of SMTP AUTH?
An SMTP relay through an Exchange Online connector that trusts your office public IP address, or Direct Send if they only email internal staff. Neither needs a password on the printer.
Does Send-MailMessage still work?
It only works while Basic SMTP AUTH is allowed, and Microsoft has marked the cmdlet obsolete. Move scripts to Microsoft Graph sendMail with an app registration.