At the end of December 2026, Microsoft will switch off basic authentication for SMTP AUTH by default in existing Microsoft 365 tenants. Anything in your office that sends email by logging in with a plain username and password will start being rejected. That usually means multifunction scanners using scan-to-email, older printers, alarm and CCTV systems, accounting or practice software, and website contact forms. Your staff's Outlook won't be affected. The fix is to find those devices now and move each one to a supported sending method before the Christmas shutdown, not after.
What exactly is changing?
SMTP AUTH is the setting that lets a device or app connect to Microsoft 365 (usually smtp.office365.com on port 587), log in with a mailbox's username and password, and send a message. That username-and-password login is called "basic authentication". It has been on Microsoft's retirement list for years because a stolen password is all an attacker needs to use it, and it can't do multi-factor authentication.
Microsoft originally planned to retire it in early 2026, then put that on hold. Its updated timeline on the Exchange Team blog says:
- From now until December 2026: nothing changes.
- End of December 2026: basic auth for SMTP AUTH is disabled by default for existing tenants. An administrator can turn it back on.
- New tenants created after that won't have it available by default.
- Second half of 2027: Microsoft says it will announce the final removal date. At that point re-enabling it stops being an option.
So December isn't the end of the road, but it is when things start breaking. A device that worked on Friday will fail on Monday with an authentication error and no obvious explanation, and the person who set it up may be long gone.
Why this matters for a small Perth office
In most small businesses nobody keeps a list of what sends email. The scanner was set up by the copier company. The alarm panel was set up by the security installer. The accounting package was configured during a migration three years ago. Many of them were given a real staff member's mailbox and password, and sometimes that password hasn't changed since.
The timing is unhelpful too. Late December is when many Perth businesses run on a skeleton crew. If invoices, statements or scanned documents stop going out over the break, it may be mid-January before anyone notices.
Step 1: Find everything that sends email
Do this before you change any settings. Check:
- Multifunction printers and scanners. Look in the device's web admin page for SMTP settings. If it shows
smtp.office365.com, port 587 and a username and password, it is affected. - Line-of-business software. Accounting, payroll, practice management, booking systems and job-management tools that email invoices or reminders straight from the application.
- Building and security systems. Alarm panels, CCTV recorders, UPS units and NAS boxes that send alert emails.
- Websites and online forms. Plugins that send through a Microsoft 365 mailbox.
- Scripts and scheduled tasks. Anything an earlier IT provider set up to email reports.
If you have admin access, the Microsoft 365 admin and Exchange reporting tools can show which accounts are still signing in with SMTP AUTH. That catches the things nobody remembers. It's worth running a report early in December so you aren't relying on memory alone.
Step 2: Choose a fix for each device
There isn't one fix that suits everything. The right option depends on what the device supports.
Option A: Switch the device to modern authentication (OAuth)
Many newer printers and most current software can sign in to Microsoft 365 using OAuth, the same modern sign-in Outlook uses. This is the cleanest fix. Check for a firmware or software update first, because OAuth support is often added in an update rather than shipped from day one.
Option B: Use a connector or relay that doesn't need a password
For older devices that will never support OAuth, Microsoft 365 can accept mail through a connector tied to your office's static public IP address. Third-party SMTP relay services are another route: the device sends to the relay, and the relay delivers the mail. Either way the device no longer needs a mailbox password.
Option C: Direct send, for internal-only mail
If a scanner only ever emails your own staff, it may be able to deliver straight to your domain's mail server without logging in at all. This only works for internal recipients. Some organisations have also deliberately blocked direct send to stop spoofed messages, so check before relying on it.
Option D: Re-enable basic auth, as a stopgap only
An administrator can turn SMTP AUTH basic authentication back on after December. Treat that as buying time, not as a fix. You'd be leaving a password-only door open, and Microsoft has said this option will be removed for good once the final date is announced.
Step 3: Tidy up while you're in there
This is a good chance to remove a quiet security risk at the same time:
- Stop using real staff mailboxes for devices. Give devices their own dedicated account or connector, so a password change or resignation doesn't break the scanner.
- Change any password that was typed into a device. Assume it has been seen by everyone who has ever opened that admin page.
- Turn SMTP AUTH off for every mailbox that doesn't need it. Most of your staff never use it, and leaving it on is exactly what attackers look for.
- Write it down. A one-page list of what sends email, how and from which account will save hours next time.
If your mail security is due for a broader check, our email protection service covers filtering and spoofing protection alongside this kind of configuration work.
A realistic timeline for the rest of 2026
- This week: list every device and app that sends email.
- Late November to early December: apply firmware updates and switch whatever you can to OAuth. Set up a connector or relay for the rest.
- Mid-December: send a test email from every device. Check that scan-to-email, invoices and alerts all arrive.
- Before the Christmas shutdown: make sure someone knows where the list is and who to call if anything stops in January.
Need a hand?
This is fiddly work rather than hard work. Most of the time goes into tracking down admin passwords for devices nobody has logged into for years. If you'd rather not spend December on it, our Microsoft 365 support for Perth businesses includes exactly this kind of tenant clean-up, and it's part of what a managed IT service handles before it becomes a Monday-morning problem.
IT Support Perth is the managed IT division of Computer Mechanics, a Perth business that has supported local offices since 1997. Call us on (08) 9325 1196 if you'd like us to check what's still using basic auth in your tenant.
