HP printer scan to email with Office 365 after Basic auth ends

On HP, OAuth support depends on the product line. HP LaserJet Enterprise and Managed MFPs on recent FutureSmart firmware can use OAuth 2.0 with Microsoft 365. HP says its LaserJet Pro MFPs cannot.

What changes in December 2026

Microsoft's updated timeline (Exchange Team blog, January 27, 2026) says that at the end of December 2026, Basic authentication for SMTP AUTH is disabled by default in existing Exchange Online tenants. Admins can still turn it back on for the tenant or for single mailboxes. Tenants created after that date won't have it at all, and Microsoft will announce the final removal date in the second half of 2027.

Many HP devices are set up with smtp.office365.com, port 587, STARTTLS and a mailbox username and password. That's Basic auth. When it's turned off, scans fail at the send step. The device log or the SMTP conversation usually shows a 535 5.7.139 error.

Option 1: native OAuth 2.0 on current HP firmware

HP's May 2026 white paper, HP LaserJet Pro MFPs: Embedded Scan to Email and Microsoft deprecation of Basic Authentication, says: "As of spring 2026, HP LaserJet Pro MFPs do not support OAuth 2.0 authentication for SMTP client submission." It gives two options: an HP cloud service that sends scans through an HP-managed relay (availability varies by region and model), or a customer-managed Microsoft setup such as SMTP relay. A local relay like ScanRelay fits that second option.

For LaserJet Enterprise / Managed / Flow MFPs, HP has a support article, Set up Scan to Email with OAuth 2.0 and a Microsoft account. An HP partner guide says OAuth requires FutureSmart 5.7 or newer (dealer guide). We couldn't confirm the minimum firmware in an HP-published document, so check the release notes for your model. HP community reports mention the sign-in hanging at "Getting Code" until IPv6 was turned off (thread), and Conditional Access policies blocking the device sign-in.

Where the SMTP settings live in the Embedded Web Server (EWS)

On FutureSmart Enterprise models, the partner guide above says to open the Scan/Digital Send tab, go to the Scan to Email settings, and add or edit a server under Outgoing Email Servers (SMTP). We couldn't confirm this path in HP's own documentation, and LaserJet Pro, OfficeJet Pro and Smart Tank models use a different EWS layout. On those, the SMTP settings page moves around between models, so check your model's manual or HP's support site.

Option 2: point the device at a local relay

If a device can't do OAuth, if the OAuth token keeps expiring, or if you run a mixed fleet and want one way to set everything up, point the device at a relay on your LAN. The device then sends plain SMTP to the relay, and the relay does the Microsoft 365 authentication. ScanRelay sends through Microsoft Graph as one mailbox you choose, so messages reach internal and external recipients, land in Sent Items, and need no DNS or SPF changes.

Device field	Value when pointing at ScanRelay
SMTP server / host	The relay's LAN IP or DNS name (for example `10.0.20.5`), not `smtp.office365.com`
Port	`25`, or whichever host port you mapped to the container
SSL/TLS or STARTTLS	Off, unless you gave the relay a certificate (`SCANRELAY_TLS_CERT`). If you did, use STARTTLS
SMTP authentication	None, if the device's IP is in `SCANRELAY_ALLOW_IPS`. Otherwise the per-device login from `SCANRELAY_USERS`
From / device email address	Anything sensible. The relay rewrites From to your sending mailbox and keeps the device address as Reply-To

On an HP, add an outgoing SMTP server with the relay's address and port 25. Leave Enable SMTP SSL protocol unchecked unless the relay has a certificate. Choose no authentication, or Server requires authentication with the relay's per-device login. Run the EWS server test, then send a real scan.

Deploy the relay (Docker or LXC) and connect it to one sending mailbox. The README has the app registration and the RBAC for Applications commands.
Add the device's IP to SCANRELAY_ALLOW_IPS, or give it its own login.
Change only the SMTP host, port, TLS and authentication fields on the device, as shown in the table above.
Send a test scan to an internal and an external address, then check Sent Items on the sending mailbox.

Which option should you use?

Current model with OAuth firmware available: use native OAuth. It's supported by the vendor and needs no extra box. Plan for the case where a token has to be re-authorized, for example after a password reset, a Conditional Access change or a long outage.
Older model with no OAuth firmware: a relay (ScanRelay, or a Microsoft connector) is the realistic way to keep scan-to-email going. Scan to folder or SMB is another option.
Mixed fleet or an MSP managing many sites: a relay per site means one set of settings for every brand, and one place to watch delivery logs and secret expiry.

Comparing every approach, including HVE, direct send and third-party senders? Read the hub guide.

Keep older scanners sending, without a third-party mail service

ScanRelay takes plain SMTP from devices on your LAN and sends it as your own mailbox through Microsoft Graph with OAuth. It's open source and self-hostable. The hosted relay and MSP dashboard are in beta from October 2026.

Join the beta View on GitHub