Skip to main content
Guide, 7 minute read

Exchange Online SMTP AUTH Change: Fixing Scan to Email and Apps

What Microsoft is changing for SMTP AUTH Basic authentication in Exchange Online at the end of December 2026, how to find the copiers, scanners, and applications it affects, and the sending options Microsoft documents for each.

Planning guidesOffice managers and IT leads at practices, schools, hotels, and manufacturers whose copiers, scanners, or applications send email through Microsoft 365By , Founder and CEO, Days Dynamics. Published November 13, 2026.

What changes for SMTP AUTH at the end of December 2026

Microsoft's Exchange Team states that at the end of December 2026, SMTP AUTH Basic Authentication will be disabled by default for existing Exchange Online tenants. A copier, scanner, or application that signs in to smtp.office365.com with a mailbox username and password can stop sending that way once the default changes, unless it moves to OAuth or another option Microsoft documents, or an administrator turns Basic authentication back on.

Microsoft's timeline, in Microsoft's words

Microsoft published this timeline on January 27, 2026, replacing the dates in its April 15, 2024 announcement. The quotes below are from the Exchange Team post, checked November 13, 2026. Microsoft has not yet given a final removal date.

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

Which devices and applications does it affect?

The change affects anything that sends mail through Exchange Online with SMTP AUTH client submission and a username and password. Microsoft's setup page for multifunction devices describes this as entering the sign-in credentials of a licensed mailbox, with the server set to smtp.office365.com on port 587 or 25.

Copiers and multifunction printers

Scan to email set up with a mailbox address and password is a common case. Some older models offer no OAuth option, while newer models or firmware may. Ask the device maker which models and firmware versions support OAuth for Microsoft 365.

Line-of-business applications

Practice management, property management, point of sale, ERP, and accounting software that emails statements, reminders, or reports through a Microsoft 365 mailbox. Check each product's mail settings, or ask the vendor.

Scripts, servers, and alerts

Scheduled tasks, backup and storage appliances, UPS units, and monitoring tools that send alert email with a stored password.

Senders this change does not touch

Senders already using OAuth, an SMTP relay connector, or direct send. Microsoft describes SMTP relay as authenticating with a TLS certificate or a static public IP address, and direct send as using no authentication, so neither signs in with a mailbox password.

How to tell if your organization is affected

Start with Microsoft's own report, then confirm device by device. The SMTP AUTH Clients report in the Exchange admin center shows which sender addresses submit mail with SMTP AUTH and whether each one uses Basic or Modern authentication.

  • Run the SMTP AUTH Clients report. In the new Exchange admin center, open Reports, then Mail flow. The Authentication Protocol column reads Basic Auth (TlsAuthLogin) or Modern Auth (XOAUTH2) for each sender address.
  • Widen the date range. The report shows the last 7 days by default and can cover up to 90 days, which catches monthly statements and quarterly jobs.
  • Check the tenant setting. In Exchange Online PowerShell, Get-TransportConfig shows the organization's SmtpClientAuthenticationDisabled value, and Get-CASMailbox shows any per-mailbox value, which Microsoft says takes precedence over the organization setting.
  • Check security defaults. Microsoft states that if security defaults are enabled in Microsoft Entra ID, SMTP AUTH is already disabled in Exchange Online.
  • Read each device's settings. Look for smtp.office365.com, port 587 or 25, and a stored mailbox username and password on the scan-to-email or SMTP screen.
  • Ask each software vendor. Ask whether the product supports OAuth (modern authentication) for sending through Microsoft 365, and which version adds it.
  • Write it down. For each sender, record the device or application, its location, the mailbox it uses, whether it emails people outside the organization, and whether the office has a static public IP address.

The sending options Microsoft documents, and what each needs

Microsoft points to OAuth first. For senders that cannot use OAuth, Microsoft Learn documents SMTP relay through a connector, direct send, High Volume Email, and Azure Communication Services Email, and Microsoft names the Microsoft Graph API as another way to send authenticated mail. Details below are from Microsoft Learn, checked November 13, 2026.

OptionWhat it needsWho it can send toWatch for
OAuth with SMTP AUTHA device or app that supports OAuth (SASL XOAUTH2) and is registered in Microsoft Entra ID; smtp.office365.com on port 587 with TLS 1.2 or laterPeople inside and outside the organizationMicrosoft lists client submission limits of 10,000 recipients per day and 30 messages per minute
SMTP relay through a connectorAn inbound connector; a static public IP address or a TLS certificate for one of your accepted domains; port 25 to your MX endpoint; no licensed mailboxPeople inside and outside the organizationDynamic IP addresses are not supported, and it cannot relay from third-party hosted services such as Azure
Direct sendPort 25 to your MX endpoint with no sign-in; Microsoft recommends a static IP for SPF and correctly configured DKIM and DMARCMicrosoft 365 recipients in your own organization onlyCannot reach outside addresses such as Gmail; Microsoft says most customers do not need it
High Volume Email (HVE)An HVE account that signs in with a username and password or OAuth; port 587 with TLS; a Microsoft 365 pay-as-you-go billing policyInternal recipients onlyCannot be used for external email delivery
Azure Communication Services EmailAn Azure subscription, an Email Communication resource with a domain, and a Microsoft Entra application whose client secret is the SMTP password; smtp.azurecomm.net on port 587 with TLS 1.2 or laterInside and outside the organizationSeparate Azure resources to set up and manage
Turn Basic authentication back onAn administrator enables it again, which Microsoft says will remain possibleUnchangedA stopgap: Microsoft will announce a final removal date in the second half of 2027

How to choose an option for each sender

Work through each sender with these questions, in order. The first question that gets a yes points to the option to test first.

  • Does it support OAuth? Use OAuth. The device stays on smtp.office365.com, and OAuth is the method Microsoft names as supported for new tenants.
  • Does it only email your own staff? Direct send or SMTP relay can work, since neither signs in with a password. Direct send cannot reach outside addresses.
  • Does it email patients, guests, parents, or customers from your office network? SMTP relay through a connector fits when the office has a static public IP address or the device can present a certificate for your domain.
  • Is it a hosted or cloud application, or is there no static IP? Ask the vendor about OAuth first. For senders that cannot use OAuth, Microsoft lists Azure Communication Services Email for recipients inside and outside the organization.
  • Can the device do none of these? Plan to replace it. Turning Basic authentication back on buys time until Microsoft's final removal date, not a lasting fix.

See the Microsoft 365 licensing and migration and the Printer and workplace print planning.

Practical next steps for your team

  • Run the report now and again in December. New senders can appear whenever someone sets up a copier or an application.
  • List every sender and the option chosen for it, with an owner for each change.
  • Test one device first. Change one copier or application, send a test to an inside and an outside address, then roll out the rest.
  • Schedule changes outside business hours, so a failed scan-to-email setup does not stop the front desk.
  • Update your documentation. Record connector names, IP addresses, certificates, and which mailbox each device uses.
  • Budget for devices that cannot change. A copier with no OAuth or relay option may need replacing, so put it on the purchase plan early.
  • Watch for Microsoft's next announcement. Microsoft says it will announce the final removal date in the second half of 2027.

See the Start a quote request and the Microsoft 365 Security Baseline Review.

Frequently asked questions

Is Microsoft turning off SMTP AUTH completely?

Not at the end of December 2026. Microsoft says Basic authentication for SMTP AUTH will be disabled by default for existing tenants, and administrators will still be able to enable it if needed. SMTP AUTH itself supports OAuth. Microsoft will announce the final removal date for Basic authentication in the second half of 2027.

Can we turn Basic authentication back on after the change?

Microsoft states that administrators will still be able to enable it if needed. Treat that as time to finish the move, since Microsoft plans to announce a final removal date.

Will scan to email still work with direct send?

Only for your own Microsoft 365 recipients. Microsoft states that direct send cannot deliver email to external recipients, such as Gmail addresses.

Does each scanner need a licensed mailbox?

Not for SMTP relay. Microsoft states that SMTP relay does not require a licensed Microsoft 365 mailbox, and direct send does not sign in at all. Client SMTP submission signs in as a licensed mailbox.

What if security defaults are turned on?

Microsoft states that if security defaults are enabled, SMTP AUTH is already disabled in Exchange Online. Check the SMTP AUTH Clients report to see what is actually sending, and how.

Move your scanners and apps off Basic authentication

Send us a list of the copiers, scanners, and applications that send email, or a screenshot of the SMTP AUTH Clients report. We can help map each sender to an option Microsoft documents, plan the change order around your hours, and quote any device replacement separately. A planning call is planning support, not a quote, an audit, a technical diagnosis, or a commitment on pricing, availability, or delivery dates.

Sources

Primary sources checked when this guide was written. Dates and product status can change, so confirm on the source before you rely on them.

Planning this project now?

Turn the checklist into a plan

The 2-minute IT quiz turns this checklist into ranked priorities for your situation, before any contact details.