Microsoft is retiring Basic SMTP Authentication for Office 365, which will change how many multifunction printers and copiers send scanned documents by email. This guide explains what’s happening, why modern authentication (OAuth 2.0) matters for scan-to-email, and how to avoid interruptions from the initial rollout on October 1, 2025 through full enforcement on March 31, 2026. You’ll find which devices are most likely to stop working, practical fixes (upgrade, SMTP relay, Direct Send or managed services), and a straightforward checklist to assess and remediate your fleet. This is written for small and medium business owners, office managers and IT teams who currently use smtp.office365.com and need a clear plan. Read on for timelines, quick device checks, solution comparisons, compatibility pointers and how to book a free compatibility assessment with Copier King to keep scan-to-email running after the change.
What is the Office 365 SMTP authentication change — and why it matters
Microsoft is phasing out Basic SMTP AUTH (username/password) and moving services that submit mail via smtp.office365.com to Modern Authentication such as OAuth 2.0. That matters because many copiers and MFPs were set up to submit email with static credentials; those setups will fail once Basic Auth is removed and scan-to-email will stop on affected devices. Modern Authentication uses short-lived tokens and ties into Azure AD controls, allowing MFA and conditional access to reduce credential exposure and improve security. If any of your devices still use smtp.office365.com with Basic Auth, you should check compatibility now and pick a remediation route before the enforcement dates. Key milestones below summarise the rollout and what to expect.
- October 1, 2025: rollout begins — you may start seeing authentication changes.
- March 31, 2026: Microsoft enforces the deprecation and blocks Basic SMTP Authentication.
- Impact summary: Devices using Basic Auth to smtp.office365.com may stop sending email, interrupting scan-to-email workflows.
Those dates create a clear timetable for action. If your copiers rely on smtp.office365.com, arrange a compatibility assessment with a trusted supplier without delay.
Office 365 SMTP authentication changes — what they mean for multifunction devices Microsoft’s removal of Basic SMTP Authentication will affect how MFPs and copiers deliver scanned documents via email. This note outlines the core impact, why OAuth 2.0 is the preferred replacement, and practical ways to avoid disruption from the October 1, 2025 rollout to the March 31, 2026 enforcement. It highlights at-risk devices, remediation choices (upgrade, relay, Direct Send or managed services) and a step-by-step checklist for assessing and fixing your estate.
What is Basic SMTP Authentication — and why is Microsoft removing it?
Basic SMTP Authentication is a legacy method where devices authenticate to smtp.office365.com with a username and password. Because those credentials are static they can be exposed and cannot be protected by MFA or conditional access, leaving accounts vulnerable to theft and brute-force attacks. Microsoft is deprecating Basic Auth to reduce the attack surface and bring mail submission in line with modern identity controls. That’s why token-based OAuth 2.0 is the safer alternative — and why some older devices can’t simply be made secure with a firmware update and will need different solutions.
How does OAuth 2.0 improve security for photocopiers?

OAuth 2.0 issues short-lived tokens instead of storing long-lived passwords on devices. That reduces the chance of reused credentials, and it supports MFA and conditional access via Azure AD. For MFPs, OAuth lets administrators manage access centrally, revoke tokens without touching each device, and apply risk-based controls. Overall, token-based authentication is easier to manage long term and is the recommended route where manufacturers support it instead of relying on Basic Auth workarounds.
Who will be affected by the multifunction printer Basic Auth deprecation in 2026?
Only organisations whose copiers or MFPs submit mail to smtp.office365.com using Basic SMTP AUTH are in scope — other SMTP providers or different submission methods aren’t affected. Many older devices predate OAuth support and lack the hardware or secure storage needed to implement it, so they can’t be patched by firmware alone. Typical at-risk setups are legacy office copiers in SMBs where scan-to-email was configured once with a service account and left untouched. The first practical step is to identify which devices use smtp.office365.com so you can decide whether to upgrade, relay or use an alternative send method.
Which photocopiers and MFPs are likely to fail scan-to-email?
Risk depends on device age, manufacturer support for OAuth and how scan-to-email was configured (per-user credentials, shared service accounts or IP-authenticated relays). Common brands in the field — Toshiba, Develop, Konica Minolta, Sharp and Utax — have mixed model support: newer business models often offer OAuth firmware, whereas older units usually don’t. Hardware limits such as missing secure token storage, weak TLS support or missing OAuth libraries mean firmware can’t always add modern auth, and those devices will need replacement or an alternate sending arrangement. The next section covers the business risks of leaving unsupported devices as they are and how to prioritise remediation.
What business risks come from not upgrading before October 2025?
Leaving affected devices unchanged risks immediate disruption: reception, HR, accounts and other teams that rely on emailed scans may lose key workflows. Last-minute emergency fixes are often more expensive, lead to rushed equipment choices and can introduce compliance gaps if insecure workarounds are used. Manual alternatives increase staff time and can delay client work or regulatory reporting. Recognising these risks helps you prioritise critical devices, schedule assessments and pick the most cost-effective remediation path.
What are your options to keep copier scan-to-email working with modern authentication?
There are four practical approaches: upgrade to OAuth-capable MFPs, implement an SMTP relay (connector or IP-based), install manufacturer firmware where available, or use Direct Send / High Volume Email for specific cases. Each option balances compatibility, security, cost and deployment time differently — the right choice depends on how many devices you have, whether recipients are mainly internal or external, and your security needs