The office scanner emails a PDF to whoever pressed the button. The accounting system sends out invoices. A script on an old server emails a backup report every morning. In a lot of Microsoft 365 tenants, all three do it the same way: they sign in to Exchange Online with a mailbox username and password over SMTP, and send.
That method is called SMTP AUTH with Basic authentication, and Microsoft is retiring it. The date has moved several times, so here's where it stands, then what to do about it.
The current timeline
Microsoft first planned to remove Basic authentication for SMTP AUTH in September 2025, then moved it to a gradual rejection from March to April 2026. In January 2026 the Exchange Team published a revised timeline, which was unchanged when we last checked it in September 2026:
- Until December 2026: nothing changes.
- End of December 2026: SMTP AUTH Basic authentication is disabled by default for existing tenants. Administrators can still turn it back on if they need to.
- New tenants created after December 2026: Basic authentication for SMTP AUTH is unavailable by default, and OAuth is the supported method.
- Second half of 2027: Microsoft will announce the final removal date.
So the first real change lands at the end of December 2026. If something in your office stops emailing in early January, this is the first place to look. Re-enabling it is a stopgap, not a fix: Microsoft has been clear that the permanent removal is coming, and this is the last warning with an off switch.
Why Microsoft is doing this
Basic authentication sends a username and password with every connection. There's no multifactor authentication, no Conditional Access, and the password usually sits in a device's settings page or a config file for years. Microsoft finished turning off Basic authentication for the other Exchange Online protocols (POP, IMAP, ActiveSync, Exchange Web Services and others) from October 2022. SMTP AUTH was the one exception, because of all the devices that depend on it.
There's a second reason to care. A mailbox whose password lives in a printer is a mailbox nobody changes the password on, and it often gets excluded from security policies so the printer keeps working. That's a quiet gap in your MFA coverage, and fixing SMTP AUTH is a good excuse to close it.
Are you affected?
Probably, if you have any of these sending mail through smtp.office365.com:
- multifunction printers and scanners doing scan-to-email
- line-of-business applications: accounting, practice management, CRM, ERP
- website contact forms that send through a Microsoft 365 mailbox
- PowerShell scripts or scheduled tasks that use
Send-MailMessagewith a stored password - monitoring tools, UPS units and building systems that send alerts
To find them, open the Exchange admin centre and look at the SMTP AUTH clients submission report under Reports, Mail flow. It shows which accounts are sending via SMTP AUTH and whether they're using Basic authentication or OAuth. In the Microsoft Entra sign-in logs, you can also filter Client app to "Authenticated SMTP".
If security defaults are turned on in your tenant, Basic authentication for SMTP AUTH is already blocked, so anything still working is using another method.
Your options
There's no single right answer. It depends on whether the device can do modern sign-in, and whether it needs to email people outside your organisation.
1. Switch to OAuth
If the device or application supports OAuth (modern authentication) for SMTP, this is the cleanest fix. Nothing else changes: same server, same port 587, same mailbox. Newer printer firmware and current versions of most business software support it. For in-house apps and scripts, Microsoft documents how to register an app in Microsoft Entra ID and use the client credentials flow, so a script can send without a stored user password at all.
Check for a firmware or software update before assuming a device can't do it.
2. SMTP relay through a connector
If the device can't do OAuth but sits at your office on a static public IP address, you can set up an inbound connector in Exchange Online that trusts that IP address or, better, a TLS certificate. The device sends to your tenant's MX endpoint on port 25 without a username or password, and it can deliver to external recipients too. It won't work for services hosted by a third party, such as an app running in Azure, and it breaks if your office IP changes.
3. High Volume Email
High Volume Email (HVE) is Microsoft's service for applications sending a lot of mail to internal recipients. It became generally available on 31 March 2026 and is billed pay-as-you-go through an Azure subscription. It can only send to people inside your own tenant, and Microsoft has said it will keep supporting Basic authentication for HVE until September 2028. That makes it a reasonable landing spot for an old internal system that can't be updated, with a known end date.
4. Azure Communication Services Email
For applications that need to email customers or suppliers, Microsoft points to Azure Communication Services Email, which supports SMTP. It's built for application mail at volume and keeps that traffic separate from your staff mailboxes.
A word on Direct Send
Direct Send lets a device send to your own mailboxes with no authentication, straight to your MX endpoint. It works, but it is unauthenticated mail claiming to be from your domain, which is exactly what phishers imitate. Microsoft added a Reject Direct Send setting in 2025 so tenants that don't use it can block it. If you use Direct Send, make sure the sending IP is in your SPF record. If you don't, consider turning it off.
What to do before the end of December
- Run the SMTP AUTH clients submission report and list every account still using Basic authentication.
- For each one, find the device or app behind it and who owns it.
- Check for firmware or software updates that add OAuth. Apply them.
- Move what's left to a relay connector, HVE or Azure Communication Services, depending on where the mail goes.
- Once the list is empty, disable SMTP AUTH on the mailboxes that no longer need it.
If you're still running an on-premises Exchange server partly to relay this kind of mail, our article on Exchange Server end of support covers what to do with it.
Where Geidi fits
Our cloud and business systems service handles migration, licensing and day-to-day running of the platforms your people work in every day. If you're not sure what's sending through your tenant, get in touch.
Sources
- Exchange Team Blog: Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline (27 January 2026) (opens in a new tab)
- Exchange Team Blog: Exchange Online to retire Basic auth for Client Submission (SMTP AUTH) (opens in a new tab)
- Microsoft Learn: Deprecation of Basic authentication in Exchange Online (opens in a new tab)
- Microsoft Learn: How to set up a multifunction device or application to send email using Microsoft 365 (opens in a new tab)
- Microsoft Learn: Authenticate an IMAP, POP or SMTP connection using OAuth (opens in a new tab)
- Microsoft Learn: Manage High Volume Email for Microsoft 365 (opens in a new tab)
- Exchange Team Blog: High Volume Email, continued support for Basic Authentication and other important updates (opens in a new tab)
- Microsoft Learn: Email SMTP support in Azure Communication Services (opens in a new tab)
- Exchange Team Blog: Introducing more control over Direct Send in Exchange Online (opens in a new tab)




