Microsoft 365 turns off SMTP AUTH Basic authentication in December 2026: what to do about scanners, printers and apps

If a scanner, a website form, a backup tool or a script sends email through smtp.office365.com with a username and password, it is likely to stop at the end of December 2026. What Microsoft has actually announced, how to find every device that depends on it, and which replacement suits which device.

Published Facts checked 9 min read
Ways to keep a device or app sending email through Microsoft 365 after Basic authentication is turned off. OAuth for SMTP AUTH: same server, needs a device that supports OAuth. SMTP relay with a connector: port 25, a static IP address that is not shared, any recipient. Direct Send: port 25 to your MX, only your own organisation's mailboxes. High Volume Email: internal recipients only, paid per recipient, Basic auth allowed until September 2028. A third-party sending service: any recipient, needs SPF and DKIM for your domain. Re-enabling Basic authentication after December only delays the change until a final date Microsoft will announce in 2027.
Which option fits depends on two things: whether the device supports OAuth, and whether it emails people outside your organisation.

Many offices have at least one device that emails through Microsoft 365 by logging in with a mailbox’s username and password: a scanner with “scan to email”, a printer that sends alerts, accounting or backup software, a website contact form, a PowerShell script. They connect to smtp.office365.com on port 587 and authenticate with Basic authentication, Microsoft’s name for a plain username and password.

Microsoft has been trying to retire this for years. In short:

  • At the end of December 2026, Basic authentication for SMTP AUTH is turned off by default in existing Microsoft 365 organisations. Devices that use it stop sending.
  • Administrators can turn it back on, so it is not the final end.
  • The final removal date has not been set. Microsoft says it will announce it in the second half of 2027.

Most guides still give older dates, so here is the timeline from Microsoft’s own posts.

What Microsoft has announced

The Exchange Team blog post of 27 January 2026 sets out the current plan:

WhenWhat happens
Now to December 2026“SMTP AUTH Basic Authentication behavior remains unchanged.”
End of December 2026Basic authentication “will be disabled by default for existing tenants. Administrators will still be able to enable it if needed.”
New tenants created after December 2026Basic authentication “will be unavailable by default. OAuth will be the supported authentication method.”
Second half of 2027“Microsoft will announce the final removal date.”

This replaced earlier plans. The April 2024 announcement aimed for September 2025; a 2025 update moved it to a gradual rejection between March and April 2026, which was then put on hold in January 2026. Pages that say mail stopped in April 2026 are describing a plan that never happened.

So in practice: at the end of December, devices that log in with a password will start failing unless an administrator turns Basic authentication back on. Turning it back on buys time until a removal date Microsoft has not yet set. It is a delay, not a fix.

Microsoft’s 2024 post gives the error devices receive once Basic authentication is refused: 550 5.7.30 Basic authentication is not supported for Client Submission. Microsoft has not said whether the December default produces the same message, so treat any authentication failure from smtp.office365.com after that date as this change until proven otherwise.

What is affected, and what is not

Affected: devices and apps that send through smtp.office365.com (client submission, usually port 587) and sign in with a username and password.

Not affected:

  • The same server used with OAuth sign-in instead of a password.
  • SMTP relay through a connector on port 25.
  • Direct Send to your own domain’s MX record on port 25.
  • People reading and sending mail in Outlook, on the web or on phones. This change is about devices and apps that send mail on their own.

How to check whether a device uses Basic authentication

1. Run the SMTP AUTH clients report. In the Exchange admin center, go to Reports › Mail flow › SMTP AUTH clients report. It lists each sender address with the number of messages sent, over a date range of up to 90 days. Microsoft’s report documentation explains the Authentication Protocol column: “Basic Auth is TlsAuthLogin and Modern Auth is XOAUTH2.”

  • TlsAuthLogin: this sender signs in with a password. It needs a plan before the end of December.
  • XOAUTH2: this sender already uses OAuth and is not affected.

2. Look for mailboxes with SMTP AUTH switched on individually. Microsoft has an organisation-wide SMTP AUTH setting and “a per-mailbox setting that overrides the tenant-wide setting” (Microsoft Learn). Organisations that turned SMTP AUTH off usually re-enabled it only for the mailboxes their devices use, so this list is often a ready-made inventory. In Exchange Online PowerShell:

Get-CASMailbox -ResultSize Unlimited |
  Where-Object { $_.SmtpClientAuthenticationDisabled -eq $false } |
  Select-Object PrimarySmtpAddress

This only reads settings; it changes nothing.

3. Match each address to a device or app. The report shows which mailbox sent the mail, not which machine. Scanners and line-of-business apps are usually set up once and forgotten, so check the settings pages of multifunction printers (their SMTP or scan-to-email settings show the sender address), the outgoing mail settings of website plugins, and scheduled scripts on servers.

If a device is not in the report:

  • The report covers up to 90 days. A device that sends rarely (a quarterly report, an alert that has not fired) may not appear. Ask the people who rely on it.
  • It may not use SMTP AUTH at all: it could already send through a relay connector or Direct Send, or through another provider’s server. Check its SMTP server setting; only smtp.office365.com is affected.
  • If your organisation uses security defaults, Microsoft notes that “SMTP AUTH is already disabled”, so a device that works today is either using a per-mailbox exception or not using SMTP AUTH.

Scan to email stopped working? A device that suddenly cannot send, with an authentication error from smtp.office365.com, after this change takes effect, is very likely affected by it. Check its sender address in the report: TlsAuthLogin confirms it.

The options, device by device

Microsoft’s guide to setting up a multifunction device or application to send email compares the methods. Three questions narrow the choice:

Decision tree. Does the device or app support OAuth for SMTP? If yes, keep SMTP AUTH with OAuth. If no: does it email people outside your organisation? If no, use Direct Send, or High Volume Email for large internal volumes. If yes: does it send from an office with a static public IP address? If yes, use SMTP relay through a connector. If no, use a sending service such as Azure Communication Services or a third-party SMTP provider.

In more detail:

1. Keep SMTP AUTH, but with OAuth. If the device or app supports OAuth 2.0 for SMTP (newer scanners and many current apps do; check the manufacturer’s firmware notes), this is the smallest change: same server, same mailbox, and messages still appear in the mailbox’s Sent Items. Microsoft documents the setup for apps in Authenticate an IMAP, POP or SMTP application by using OAuth. Microsoft’s limit for this method is 10,000 recipients a day and 30 messages a minute.

2. SMTP relay through a connector. The device sends to your domain’s Microsoft 365 MX endpoint on port 25 without logging in, and Microsoft 365 recognises it by a certificate or by a static public IP address. Microsoft’s requirement is a certificate or “a static IP address that isn’t shared” with another organisation. It can send to anyone, inside or outside the organisation. It suits an office with a fixed internet address; it does not suit a home office or a device on a changing connection, and it cannot be used from shared hosting.

3. Direct Send. The device sends straight to your MX on port 25 with no login, but it can only deliver to mailboxes in your own Microsoft 365 organisation. Fine for scan-to-email to staff; useless for invoices to customers. Microsoft added a setting in 2025 that lets administrators reject Direct Send entirely (Exchange Team blog); if your organisation has turned it on, this option is closed.

4. High Volume Email (HVE). A Microsoft 365 service that Microsoft’s device guide describes as a way to “send large volumes of email to internal recipients”. Its documentation gives the price as the “equivalent to $42 per one million recipients” through pay-as-you-go billing, and Microsoft has said HVE keeps Basic authentication until September 2028. A route for a device that cannot do OAuth and only emails staff.

5. A separate sending service. For external recipients from a device without OAuth, Microsoft’s device guide points to Azure Communication Services Email, and many organisations use a third-party SMTP provider. Either way, the service sends as your domain from its own servers, so your domain’s records must allow it.

Do not forget your domain’s records

Options 2, 3 and 5 change which servers send mail with your domain in the From line. Receivers check that against your SPF, DKIM and DMARC records, and Gmail, Yahoo and Outlook.com now reject or junk mail that fails. Microsoft’s own comparison recommends an SPF entry for relay and Direct Send.

  • For relay or Direct Send, add your office’s static IP address to your SPF record (ip4:203.0.113.10).
  • For a sending service, add its SPF include and set up its DKIM records for your domain.
  • Keep the SPF record within 10 DNS lookups, or SPF fails for all your mail.

Mailtria’s SPF, DKIM and DMARC checker reads your domain’s public DNS, follows and counts every SPF include, and shows what to fix. Our article on the Gmail, Yahoo and Outlook.com sender rules explains what the records must say. After switching a device over, send a test to an outside address and paste the headers into the email header analyzer to confirm SPF, DKIM and DMARC pass.

A short plan for the next eight weeks

  1. Run the SMTP AUTH clients report and list every sender using TlsAuthLogin.
  2. For each one, find the device or app and check whether it supports OAuth.
  3. Move OAuth-capable devices first; they need no DNS changes.
  4. For the rest, choose relay, Direct Send, HVE or a sending service based on whether they email outside the organisation, and update SPF and DKIM before switching.
  5. Decide now whether you will temporarily re-enable Basic authentication in December for anything left over, and write down which devices that covers, so it does not quietly become permanent.

Frequently asked

Will SMTP AUTH Basic authentication stop working completely in December 2026? No. It is turned off by default in existing organisations, and administrators “will still be able to enable it if needed”. It stops completely on a final removal date that Microsoft says it will announce in the second half of 2027.

Does this affect Gmail, Yahoo or other providers’ SMTP servers? No. This change is to Microsoft’s Exchange Online (Microsoft 365) service and its smtp.office365.com server. Other providers set their own rules.

Does this affect Outlook on my computer? Not for Microsoft 365 mailboxes. Microsoft’s Basic authentication deprecation page says all “versions of Outlook for Windows since 2016 have Modern authentication enabled by default”, and Outlook connects to Microsoft 365 without SMTP AUTH. This change is about devices and apps that send through smtp.office365.com.

How do I check whether my printer or scanner uses Basic authentication? Find the sender address in its SMTP or scan-to-email settings and look it up in the SMTP AUTH clients report: TlsAuthLogin means Basic authentication. If the device is set to smtp.office365.com with only a username and password, and has no OAuth or Microsoft 365 sign-in option, it uses Basic authentication.

Can I keep using an app password? An app password is still a password sent with Basic authentication, so it is affected in the same way. Microsoft’s app password documentation also notes that “App passwords don’t work for accounts that are required to use modern authentication.”

Does SMTP support OAuth? Yes. Exchange Online accepts OAuth 2.0 for SMTP AUTH, shown as XOAUTH2 in the report. The device or app has to support it; many older scanners do not, and firmware updates sometimes add it.

What happens if I re-enable Basic authentication? Devices keep working as before, until the final removal date Microsoft has yet to announce. Use the time to move them, and keep a list of what still relies on Basic authentication so the exception does not quietly become permanent.

Sources

This article is general information, not legal, security or professional advice. Services change their rules and screens; check the official pages linked above before you act, and keep a backup before changing your mail.

SPF, DKIM and DMARC CheckerCheck a domain's email records and what to fix. Free, no sign-up; it only reads the domain's public DNS records.
Open SPF, DKIM and DMARC Checker