FolioQ9AnswerLast checked 22 Nov 2026
As at
Sun 22 Nov 2026
Entries
8
Not yet
9
Page seal 3D89, 069°08′. Drawn from the SHA 256 of this page’s source text3D89
Page seal3D89, 069°08′

Microsoft 365 is turning off SMTP AUTH. How do I keep scan to email working?

Short answer. At the end of December 2026, Microsoft switches basic authentication for SMTP AUTH off by default in existing Microsoft 365 tenants. Printers and apps that send through smtp.office365.com with a username and password will stop. Admins can switch it back on for now; removal is coming. The lasting fix is OAuth, a relay connector, or an app mail service.

What we have measured. Nothing yet; our own test tenant runs are not done.1

What Microsoft has said, as of 22 Nov 2026

  • End of December 2026: basic authentication for SMTP AUTH is "disabled by default for existing tenants". Microsoft's post says "Administrators will still be able to enable it if needed."
  • New tenants created after December 2026: basic authentication is not available by default. OAuth is the supported method.
  • Second half of 2027: Microsoft will announce the final removal date.
  • 19 Nov 2026: in the comments under the post, a Microsoft staff member said the exact date for existing tenants will be announced "soon", that admins would need to re enable it by hand after the change, that the procedure will be shared, and that no opt out is planned "as of now".

This is a moving date. We recheck the post before every update to this page.

Which devices are affected

Anything that sends mail through Microsoft 365 by typing a mailbox username and password into its settings, with server smtp.office365.com on port 587 or 25. That is often:

  • multifunction printers and scanners with scan to email;
  • accounting, booking, alarm and building systems that send alerts;
  • older line of business apps and website contact forms.

The four routes Microsoft documents

From Microsoft's guide for multifunction devices and applications, updated in 2026:

RouteSends outside your company?What it needsMain limit
Client SMTP submission with OAuthYesA licensed mailbox; the device must support OAuth and TLS 1.2 or 1.3; port 58710,000 recipients a day, 30 messages a minute
SMTP relay through a connectorYesA static public IP not shared with other organisations, or a certificate naming your domain; port 25; an inbound connector; your IP in SPFMail can be disrupted if the IP is blocklisted
Direct SendNo, internal onlyPort 25; SPF, DKIM and DMARC set correctlyMicrosoft says it is working on an option to switch Direct Send off by default
High Volume EmailNo, internal onlyAn HVE accountFor mail to your own staff

For mail to both staff and outside recipients, Microsoft also points to Azure Communication Services Email. If you already run an on premises mail server, Microsoft suggests relaying through it.

Steps you can do yourself, free

  1. Find every device and app that sends.

    Walk the office: printers, scanners, alarm panels, the accounts system. In each, look at the email or SMTP settings. Any that list smtp.office365.com with a username and password is on the list.

  2. Check whether SMTP AUTH is even on.

    Microsoft notes that SMTP AUTH is already off for organisations created after January 2020, and can be enabled per mailbox. If a device works today in such a tenant, someone enabled it.

  3. For each device, check OAuth support.

    Look in the device menu or the maker's support site for "OAuth" or "Modern Authentication" for Microsoft 365. A firmware update sometimes adds it. If it has it, switch to OAuth and keep port 587.

  4. If not, and the device sends only to your own staff,

    consider Direct Send or High Volume Email. Note Microsoft's warning on Direct Send above.

  5. If it must send outside, and your office has a static IP,

    set up an SMTP relay connector. In the Exchange admin center, go to Mail flow, then Connectors, then Add a connector, from "Your organization's email server", authenticated by your static IP. Point the device at your MX endpoint (it looks like yourdomain-com.mail.protection.outlook.com) on port 25, and add the IP to your SPF record.

  6. If there is no static IP and no OAuth,

    look at Azure Communication Services Email or a mail sending service the device supports.

  7. Test each device

    by sending to an outside address and reading the headers for spf=pass and dkim or dmarc=pass.

  8. Do not rely on the re enable switch.

    It buys time, but a final removal date is coming.

What it costs to have it done

The firm's source table holds no dated outside price for this exact job.2 For context, one white label managed service provider prints 22 USD per device a month, with a minimum of 15 devices or 330 USD (S55); that is general IT support, not this job.

Marsadel's own price. Microsoft 365 Password Sending Switch (SMTP AUTH). Firm's own price, Tier 1 list, US dollars.

  • 290 USD per tenant, up to 10 devices, at launch and after: this job is sold in runbook mode only, so its price is already the launch price. Through an IT firm (wholesale): 190 USD.
  • Runbook mode only. AI agents read your tenant's sign in and sending logs, from an export your IT person sends us or through read only consent you grant and can revoke, to find every device and app that sends with a username and password.3 They then write a per device runbook moving each to OAuth, a relay connector or a mail API, and test the result. Your IT person applies each device's settings on site. We make no changes in your tenant and hold no access inside your network. A second AI model and a named reviewer will check the work.4

Not on sale yet. This unit opens after its quality test (target Sat 12 Dec 2026), once our company and checkout are live.

Not yet: Unit 3 Bench passed and sealed on a test tenant; target Sat 12 Dec 2026, first sale Mon 14 Dec 2026. Until then this unit is not on sale.5, 6

Details: Microsoft 365 Password Sending Switch (SMTP AUTH).

How to check it worked

Each device sends a test to an outside mailbox and to an inside one. Both arrive. In the Microsoft 365 sign in logs, no device appears signing in to SMTP with basic authentication.

Facts on this page

FactSourceRead
Basic auth for SMTP AUTH disabled by default for existing tenants end of December 2026; admins can still enable it; new tenants after December 2026 without it by default; final removal date announced in second half of 2027; staff reply 19 Nov 2026techcommunity.microsoft.com/blog/Exchange/updated-exchange-online-smtp-auth-basic-authentication-deprecation-timeline/4489835 (S16)22 Nov 2026
Four sending methods, ports, TLS, limits, static IP or certificate for relay, Direct Send internal only and planned default off, HVE internal, Azure Communication Services Email for internal and external, SMTP AUTH off for tenants created after January 2020learn.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-36522 Nov 2026
White label MSP 22 USD per device, minimum 15 or 330 USDmedhacloud.com/white-label-msp-services/pricing-packages (S55)22 Nov 2026

Rows without an S number were read by the page writer and are not yet in the firm's source table.7

Questions people ask next

Will my printer stop on 1 January 2027? Microsoft has said "end of December 2026" without a day, and that the exact date will be announced. Plan for it to stop then, and recheck the post.

Can I just switch basic authentication back on? For now, Microsoft says administrators can. It also says a final removal date will be announced in 2027. Use the switch to buy time, not as the fix.

My printer only supports port 465. Is that a problem? Microsoft's guide says a device that recommends or defaults to port 465 does not support the TLS versions client submission needs. Use a relay connector or an on premises relay instead.

Can Direct Send reach a customer's Gmail address? No. Microsoft's guide says Direct Send "Can't deliver email to external recipients", for example Gmail or Yahoo addresses. For outside recipients use OAuth, a relay connector or Azure Communication Services Email.

If I order, do you train AI models on my tenant's logs? No, unless you tick a consent box that allows it.


Written by AI agents and checked against the sources above. Last checked 22 Nov 2026. No named human has reviewed this page yet.8 No partner is signed in any country yet.9

Not yet in place9

Nothing is on sale yet; each numbered mark on this page points to a condition below. Every condition, with its state, is on the status board.

  1. 1own test tenant results, devices found per tenant, with n, labelled own property
  2. 2three dated outside prices for SMTP AUTH migration, with URL and read date
  3. 3launch route for the logs confirmed
  4. 4second model vendor connected; two contracted reviewers, target Mon 30 Nov 2026
  5. 5Unit 3 Bench passed and sealed on a test tenant; target Sat 12 Dec 2026, first sale Mon 14 Dec 2026. Until then this unit is not on sale.
  6. 6company formed and checkout live
  7. 7each such row added to the plan source table with an S number and status
  8. 8named human reviewer under contract
  9. 9first partner agreements signed

Each item is also marked where it stands on this page.