Scan to email after Microsoft ends Basic Auth: the December 2026 copier checklist.
At the end of December 2026 Microsoft disables Basic Authentication for SMTP AUTH in Exchange Online. That is the login method almost every copier and multifunction printer uses to scan to email through Microsoft 365. Google made the same change on May 1, 2025. This guide covers what breaks, how to confirm it is this change and not the device, the four options Microsoft leaves you and what each one still leaves exposed, OAuth firmware support by brand, where PaperCut and Scanshare fit, and the fifth option: take the scan off the SMTP path entirely. Updated November 6, 2026.
What Microsoft is changing for scan to email, and the dates that matter
Basic Authentication for SMTP AUTH is the username-and-password login a device uses to send mail through smtp.office365.com on port 587. Microsoft announced its retirement timeline in January 2026 after two earlier dates slipped (September 2025, then a phased rejection starting March 1, 2026). The current timeline, as published by Microsoft and summarized by PaperCut, Marco and other copier channel partners:
| Date | What happens |
|---|---|
| Through December 2026 | Basic Authentication for SMTP AUTH keeps working as it does today. |
| End of December 2026 | Disabled by default for existing tenants. A tenant administrator can re-enable it, which buys time and reintroduces a stored mailbox password on every device. |
| New tenants after December 2026 | Basic Authentication is not available. OAuth is the supported method. |
| Second half of 2027 | Microsoft announces the final removal date, after which the re-enable option goes away. |
Google Workspace already made this change. Support for "less secure apps" ended on May 1, 2025, so a copier that scans to email through Gmail with a plain password stopped working then unless it was moved to an app password or OAuth.
Two things make this a security event and not only a breakage event. First, the reason Microsoft gives is that Basic Authentication is a standing target for password spraying and credential theft even on an encrypted connection: the device holds a real mailbox password, and that password is in the device configuration backup. Second, every fix on Microsoft's list changes how the device authenticates and leaves what the device sends, a scanned document as an email attachment, exactly where it was.
Scan to email stopped working: how to confirm it is the Basic Auth change
When Exchange Online rejects a Basic Authentication submission the device logs a 550 5.7.30 response. On most copier control panels that surfaces as a generic "send failed" or "SMTP authentication error." Three checks separate the Microsoft change from an ordinary device fault:
1. Read the device's SMTP job log, not the panel. HP EWS, Xerox CentreWare, Ricoh Web Image Monitor, Canon Remote UI and Konica Minolta Web Connection all keep an email transmission log with the server response code. A 5.7.30 or "authentication unsuccessful" entry on an account that worked yesterday is the change.
2. Check the tenant. In the Microsoft 365 admin center, the SMTP AUTH setting is per mailbox and per tenant. If the tenant has already moved to the new default, the mailbox the copier uses will show SMTP AUTH disabled.
3. Test the credential outside the device. If a mail client with the same mailbox and the same password also fails on port 587, it is the authentication method, not the copier. If the mail client succeeds with modern authentication and the copier fails with a password, you have your answer.
If the fleet is under a managed print services contract, the first call usually goes to the dealer. Most dealers are preparing for this; Marco, Loffler and Toshiba Tec have all published December 2026 guidance. Ask them which of the options below they are proposing for your fleet, and then read the "what each option still leaves exposed" column before you agree.
Office 365 scan to email settings after Basic Auth: the four options Microsoft leaves you
Microsoft's own guidance for multifunction devices lists these paths. Each one fixes the login. None of them changes what leaves the device.
| Option | How it works | What it still leaves exposed |
|---|---|---|
| OAuth 2.0 (modern authentication) | The device obtains a short-lived token from Entra ID instead of storing a password. Configured per device. Requires firmware that supports it (see the brand table below). | The scanned document still travels as an email attachment through the relay chain and lands in a mailbox and its archive. Older devices never get the firmware. Nothing on the device produces a per-document record an examiner can sample. |
| SMTP relay (connector) | Microsoft 365 accepts mail from the device by trusting its public IP through a connector. No credential on the device. | The device sends to the connector over whatever TLS it negotiates, and most copiers fail open to plaintext when the certificate does not validate. The attachment still lands in the mailbox. IP trust means any host on that address can send as you. |
| High Volume Email (HVE) | A separate Microsoft service for internal bulk mail. Per channel reporting it keeps Basic Authentication until September 2028. | Built for internal traffic. Pushes the same password-on-device problem two years down the road. External recipients are not its use case. |
| Direct Send | The device sends to the tenant's MX endpoint with no authentication, internal recipients only. | No authentication at all, internal only, and dealers themselves describe it as rarely appropriate for the long term because of IP reputation and blocklist risk. |
The pattern is the same in every row. The authentication leg gets fixed. The document leg, the part an auditor samples and the part the CISA directive on printers is about, does not change.
Which copiers support OAuth for scan to email
OAuth support lives in device firmware, and only the manufacturer can ship it. As summarized by Marco Technologies from vendor statements in 2026, and subject to change as firmware lands:
| Brand | OAuth for SMTP client submission |
|---|---|
| HP | FutureSmart 5.7 and later. |
| Canon | Unified Firmware Platform v3.18 and later. |
| Lexmark | Firmware FW24 and later. |
| Sharp | Most recent models only. |
| Konica Minolta | Limited release, with patches reported as late as summer 2026 for some models. |
| Ricoh | Limited. |
| Xerox | No OAuth support reported for this use case. |
A mixed fleet, which is most fleets, will end up with some devices on OAuth, some on an IP-trusted relay, and some on a re-enabled Basic Authentication exception. Three authentication methods, three sets of settings, and still one attachment leaving every device in the clear.
After the login is fixed, the attachment is still the finding
An assessor who flags scan-to-email is not flagging the password. The finding reads "SMTP service cleartext login permitted" or "unencrypted email containing nonpublic personal information," and it is about the document. A scanned loan file, a patient intake form, or a student record leaves the copier as a PDF attachment, crosses one or more SMTP hops that may or may not be encrypted end to end, and lands in a mailbox, where it is copied into an archive, a backup, and a sent-items folder for years.
OAuth does not change any of that. Neither does an IP-trusted relay. The device still has a mailbox to send through, the document still rides as an attachment, and there is still no per-document record that says who received it and when. The CISA directive that names printers (BOD 26-04, compliance date December 7, 2026) and the Basic Authentication change land in the same month for the same reason: the printer fleet is now an inventoried, auditable set of network devices, and what leaves them is in scope.
The practical question for December is therefore not "how do I keep scan to email working" but "do I want the scan on the SMTP path at all."
Take the scan off the SMTP path: how SecureMFP replaces the whole flow
SecureMFP is not an SMTP server and it does not relay mail. It is a full replacement for the traditional scan-to-email path that plugs into the SMTP settings the device already has. The device's existing scan-to-email configuration points at the SecureMFP gateway, which terminates the device's native SMTP. From there the document never touches a mail server or an inbox: SecureMFP encrypts it with AES-256 in real time, moves it through the Secure Digital Transport engine over one direct TLS connection, and sends the recipient an email that carries an expiring secure link, never the attachment. The recipient retrieves the document without creating an account or logging in to a portal, every retrieval is logged per document, and the file is overwritten and deleted after the delivery window, 14 days by default.
Authentication is the part that matters this December. Each device gets its own SecureMFP credential, bound to that machine on first connection. There is no Microsoft 365 or Google Workspace mailbox password on the device, so the Basic Authentication retirement does not apply to it. A credential pulled from a configuration backup fails on any other device. The SMTP, SMB, LDAP and fax credentials that used to live on each copier move to the gateway.
The device side requires port 587, TLS and a validated certificate. A device that cannot meet that does not fall back to plaintext; it does not send. Deployment is about five minutes per device with no firmware change on any brand, which means the Xerox and Konica Minolta devices with no OAuth firmware are handled the same way as the HP devices that have it. One method across the fleet instead of three.
For the auditor, the output is a per-document access log mapped to NIST SP 800-53 SC-8, HIPAA 164.312(e)(1), GLBA, FTC Safeguards 314.4(c)(3) and SOC 2 CC6.6 and CC6.7. For the CISA inventory, the scan leg of every printer has one owner, one configuration and one log. The setup guide covers the five-step rollout; the remediation guide covers the finding language.
The December 2026 copier scan to email checklist
The same fleet has a second December date. CISA BOD 26-04 reaches its Phase III deadline on December 7, and what it means by industry is the other half of this checklist.
Ten items, in the order a fleet should run them. Items 1 through 4 are the inventory the BOD 26-04 checklist also asks for, so one pass covers both deadlines.
- List every device that sends email. Copiers, MFPs, scanners, fax servers, and any print management or scan workflow server with an SMTP setting (PaperCut, Scanshare, uniFLOW). Include the mailbox each one uses.
- Record the authentication method per device. Basic (password), OAuth, IP-trusted relay, or none. Most fleets find they do not know until they open each admin console.
- Record the firmware version per device against the OAuth support table above. Mark the devices that will never get OAuth.
- Pull the device configuration backups and note which contain a mailbox credential. That is the exposure Microsoft is closing and the one an assessor will ask about.
- Check the tenant setting. Confirm whether SMTP AUTH is already disabled for the service mailboxes and whether anyone re-enabled it as a stopgap.
- Decide the policy question before the technical one: does the scanned document stay on the SMTP path as an attachment, or does the fleet move to secure-link delivery. Write the answer down; the auditor will ask who decided.
- For devices staying on SMTP: OAuth where firmware allows, relay connector where it does not, no re-enabled Basic Authentication without an expiry date and an owner.
- For devices moving to SecureMFP: point the existing scan-to-email settings at the gateway, confirm port 587 with a validated certificate, enroll the per-device credential, run one test scan and read the per-document log.
- Repoint PaperCut and Scanshare SMTP settings to the same destination as the devices so the workflow platforms do not become the one path that still sends attachments.
- Capture the evidence. Inventory, authentication method per device, the policy decision, and a sample per-document log. That package answers the Basic Authentication question, the BOD 26-04 printer inventory, and the next scan-to-email finding at the same time.
Scan to email after Basic Auth: questions IT teams are asking
When does Microsoft disable Basic Authentication for SMTP AUTH?
At the end of December 2026 it is disabled by default for existing Exchange Online tenants, and unavailable for new tenants. Administrators can re-enable it after that date until Microsoft announces the final removal date, which it plans to do in the second half of 2027.
Will my copier stop scanning to email in December 2026?
If it signs in to Microsoft 365 with a mailbox username and password on port 587, yes, unless the tenant re-enables Basic Authentication or the device is moved to OAuth, an IP-trusted relay connector, or a path that does not use a mailbox credential at all.
What are the Office 365 SMTP settings for a scanner after the change?
For OAuth the device still uses smtp.office365.com on port 587 with STARTTLS but authenticates with a token from an Entra ID app registration instead of a password. For the relay option the device sends to the tenant's MX endpoint on port 25 and the connector trusts its public IP. Microsoft's multifunction device article documents both. For SecureMFP the device's SMTP settings point at the gateway on port 587 with TLS and a per-device credential; no Microsoft mailbox is involved.
Does OAuth fix the unencrypted scan-to-email audit finding?
No. OAuth replaces the stored password with a short-lived token. The scanned document still leaves the device as an attachment, still crosses the relay chain, still lands in a mailbox and its archive, and still produces no per-document record. The finding is about the document, not the login.
What is the SMTP relay option and is it secure?
A Microsoft 365 connector that accepts mail from your public IP without a credential. It removes the password from the device. It does not control whether the device negotiates TLS to the connector, most copiers fail open to plaintext when a certificate does not validate, and it trusts anything on that IP address.
Does the Basic Authentication change affect PaperCut or Scanshare?
PaperCut states that NG and MF are affected when they use Basic Authentication for Scan to Email, Email to Print or notifications through Exchange Online or Google Workspace, and that Hive, Pocket and scan-to-cloud are not. Scanshare and any other workflow server with an SMTP setting that uses a mailbox password is affected the same way the copier is. In all cases the fix is the platform's SMTP setting, which can point at OAuth, a relay, or the SecureMFP gateway.
Is SecureMFP affected by the Basic Authentication retirement?
No. The device authenticates to SecureMFP with its own per-device credential, bound to that machine on first connection. There is no Microsoft 365 or Google Workspace mailbox password on the device and the document never passes through an SMTP server or inbox; the recipient receives an email with an expiring secure link and the file is deleted after the delivery window.
Do I need new copiers or a firmware update?
For OAuth, you need firmware that supports it, and some brands and models will not get it. For SecureMFP, no firmware change is required on any brand; the existing scan-to-email settings are pointed at the gateway, which takes about five minutes per device.
Run the December checklist with a SecureMFP specialist
Thirty minutes, your fleet. A SecureMFP specialist will walk the ten-item checklist against your brand mix, your Microsoft 365 or Google Workspace tenant, and any PaperCut or Scanshare servers in the path, and show you what the per-device credential and the per-document log look like on a live device. If your dealer has already proposed an OAuth or relay plan, bring it; the walkthrough shows where the attachment still goes under that plan and what changes when the scan comes off the SMTP path.