Exchange Online SMTP AUTH basic auth switches off in December 2026
Exchange Online switches off SMTP AUTH basic authentication by default at the end of December 2026. Find affected senders and pick OAuth, HVE or relay.
Microsoft plans to switch off Basic authentication (username and password) for SMTP AUTH in Exchange Online by default at the end of December 2026. After that switch-off, admins of existing tenants will still be able to turn it back on, but any printer, scanner or script that logs in to smtp.office365.com with a plain password should be moved to OAuth or another sending method before then.
This page covers what Microsoft has said about the timeline, how to find out what still uses SMTP AUTH in your tenant, and which replacement fits which device. Dates here follow Microsoft's published timeline as of October 2026; Microsoft has changed this schedule before, so check the source links before acting.
What is changing and when
Microsoft first announced the retirement of Basic auth for client submission in an Exchange Team blog post and later issued an updated timeline in January 2026, which the Exchange Online docs now point to as the current reference. According to that update, the plan is:
- Until December 2026: no change to how SMTP AUTH with Basic authentication behaves.
- End of December 2026: Basic auth for SMTP AUTH is disabled by default for existing tenants. Admins can still re-enable it.
- New tenants (from January 2027, or end of December 2026 by some reports): Basic auth for SMTP AUTH is not available; OAuth is required.
- Final removal: Microsoft says it will announce the exact date in the second half of 2027.
Microsoft has not published an exact day within December for the default change. Treat 31 December 2026 as the latest safe assumption and plan to be finished earlier, since year-end change freezes are common.
Two things are not changing. SMTP AUTH itself stays, and it supports OAuth. And the clients most people use daily, such as Outlook and Outlook on the web, do not use SMTP AUTH to send mail, according to Microsoft's SMTP AUTH documentation.
Who is affected
The affected senders are the ones that log in with a mailbox password over SMTP:
- Multifunction printers and scanners using scan-to-email.
- Line-of-business apps, monitoring tools and backup software with an SMTP settings screen.
- Scripts using PowerShell's Send-MailMessage or similar libraries with stored credentials.
- POP3 or IMAP mail clients that send through Exchange Online.
Tenants that have security defaults turned on already have SMTP AUTH disabled, per Microsoft's documentation. Organisations created since January 2020 also start with SMTP AUTH off, with the option to enable it per mailbox.
Step 1: find what still uses SMTP AUTH
Before changing anything, build an inventory. Two places to start are the SMTP AUTH client activity report in the Exchange admin center and the Microsoft Entra sign-in logs, where legacy SMTP sign-ins show up. Note the mailbox used, the source device or server, and who owns it. Printers are the usual surprise: they are often configured once, years ago, and nobody remembers the account.
Then check how SMTP AUTH is set at each level. The organisation setting is controlled with PowerShell:
- Organisation: Set-TransportConfig -SmtpClientAuthenticationDisabled $true disables SMTP AUTH tenant-wide; $false enables it.
- Single mailbox: Set-CASMailbox -Identity user@contoso.com -SmtpClientAuthenticationDisabled $false enables it for that mailbox. A value of $null hands control back to the organisation setting.
The mailbox setting overrides the organisation setting. Microsoft recommends disabling SMTP AUTH organisation-wide and enabling it only for the mailboxes that still need it. Another cmdlet pair, Get-CASMailbox filtered on the same property, lists which mailboxes are enabled.
Step 2: pick a replacement for each sender
Microsoft's guide on sending email from devices and applications lists four methods. Which one fits depends on whether the sender needs to reach external recipients and whether it can do OAuth.
OAuth 2.0 with SMTP AUTH
If the application or library supports it, this is the smallest change: same server, same port, different login. Microsoft documents the delegated scope SMTP.Send and, for the client credentials flow, the application permission SMTP.SendAsApp. The app is registered in Microsoft Entra, an admin consents, the service principal is registered in Exchange with New-ServicePrincipal, and the mailbox is granted permission. The token is sent using the SASL XOAUTH2 format, and the OAuth guide notes the client credentials token must request the scope https://outlook.office365.com/.default. See the OAuth documentation for the exact steps.
Most printers cannot do this. Check the vendor's firmware notes before assuming.
High Volume Email (internal recipients only)
High Volume Email (HVE) is intended for devices and apps that send to people inside your own tenant. As of Microsoft's documentation dated April 2026, it uses a dedicated account without a mailbox or licence, the endpoint smtp.hve.mx.microsoft on port 587, and accepts either HVE account credentials or OAuth. Limits include 50 recipients per message, 10 MB per message and no external delivery. It is billed through Microsoft 365 pay-as-you-go, listed at $42 per million recipients, and an account cannot send until a billing policy is attached.
That Basic-auth option is the quick fix for a printer that only emails staff. Microsoft's documentation also states that HVE accounts can authenticate even when SMTP AUTH is disabled in the transport configuration, because HVE uses its own endpoint. Whether Microsoft later changes Basic auth rules for HVE is not covered in the pages reviewed, so verify before relying on it long term.
Azure Communication Services Email
For senders that must reach external recipients and cannot use OAuth, Microsoft's device guide recommends Azure Communication Services Email with its SMTP support. It sits in Azure rather than in Exchange, so it needs an Azure subscription and a verified sending domain.
SMTP relay with a connector
An inbound connector lets a device send to your tenant's MX endpoint on port 25, authenticated by a TLS certificate or a static public IP address. Microsoft describes it as an option for cases where the other methods do not work. It does not need a licensed mailbox, but it cannot be used for third-party hosted services, messages are not saved to Sent Items, and you should publish a matching SPF entry.
Direct Send
Direct Send needs no authentication and delivers only to recipients in your own tenant. Microsoft calls it suitable for advanced administrators only, and notes that it is working on an option to disable Direct Send by default. Anyone using it should check DKIM, DMARC and SPF first, because the mail is treated like anonymous internet mail.
A practical order of work
- List every sender using SMTP AUTH and assign an owner.
- Move senders that support OAuth first.
- Move internal-only senders to HVE or a connector.
- Move external-recipient senders to Azure Communication Services Email or an on-premises relay.
- Disable SMTP AUTH at the organisation level, keeping explicit per-mailbox exceptions for anything left, and write down an end date for each exception.
- Re-check after the December change, since tenant defaults may shift.
For related reading on this site, see our coverage of security, cloud infrastructure and DevOps tooling, and the dated reference on Patch Tuesday and vendor patch days.
Frequently asked questions
When does SMTP AUTH basic authentication stop working in Exchange Online?
Under Microsoft's updated timeline, it is disabled by default for existing tenants at the end of December 2026, and admins can still re-enable it. Microsoft says it will announce the final removal date in the second half of 2027.
Will Outlook stop sending email?
No. Microsoft's documentation says modern clients such as Outlook, Outlook on the web and Outlook for iOS and Android do not use SMTP AUTH to send mail. The change hits devices, apps and scripts that log in over SMTP with a password.
How do I enable SMTP AUTH for one mailbox?
Run Set-CASMailbox with the mailbox identity and -SmtpClientAuthenticationDisabled $false in Exchange Online PowerShell, or tick Authenticated SMTP under Manage email apps in the Microsoft 365 admin center. The mailbox setting overrides the organisation setting.
What can my scan-to-email printer use instead?
If it only emails internal staff, High Volume Email or an SMTP relay connector are the usual options. If it must email external addresses, Microsoft points to Azure Communication Services Email or an on-premises mail server.
Does High Volume Email cost money?
Yes. Microsoft's documentation lists pay-as-you-go billing at $42 per million delivered recipients as of its April 2026 update, and an account needs a billing policy before it can send.