Find out exactly where it fails
Start at the device. Most multifunction printers show an error code or message when a scan fails, and many keep a job log you can view on the screen or through the web admin page. Note whether the scan fails immediately, after a long pause, or appears to succeed but never arrives. Each points to a different cause.
Check what changed recently. A password reset on the email account used by the scanner, a new internet provider, a server replacement, a Microsoft 365 security change or a Windows update on the computer hosting the scan folder are the usual triggers. Scanning rarely breaks on its own; something around it moved.
Scan to email and Microsoft 365
Older devices send scanned files by signing in to Microsoft 365 with a username and password over SMTP. Microsoft has been steadily retiring this kind of basic authentication, and security defaults or conditional access policies often block it. When multi-factor authentication is turned on for the account the printer uses, the printer can't complete the extra step and sending fails.
There are several reliable alternatives. An SMTP relay connector in Exchange Online lets the printer send from your office's fixed public IP address without signing in. Direct send works for delivering only to your own mailboxes. Newer devices support modern authentication with Microsoft 365, and some brands offer a cloud connector that sends scans through their own service. The right choice depends on the device, whether you have a static IP address and who needs to receive scans.
Common scan to email mistakes
Using a real staff member's mailbox for the printer is fragile, because the person changes their password or leaves and scanning stops. Use a dedicated, appropriately secured account or a relay that doesn't need one. Check that the sender address on the device matches a domain you own and that your SPF record includes the method you use, otherwise scans may land in junk or be rejected.
Large scans can exceed attachment limits, especially colour scans at high resolution. Set sensible defaults such as black and white at 200 to 300 dpi as PDF, with colour available when needed. If the device sends through your internet provider's mail server, that path may disappear when you change provider, which is a common cause after a fibre or ISP switch.
Scan to network folder
Scan to folder uses Windows file sharing to save directly into a shared folder on a server, NAS or computer. Common failures include a changed password on the account the device uses, a shared folder that was moved or renamed, and a device that only supports the older SMB1 protocol, which modern Windows disables by default because of security risks.
Check the device's address book entry for the folder path, username and password, and test the same credentials from a computer. If the device only supports SMB1, update its firmware; many manufacturers added newer SMB support in later releases. Don't re-enable SMB1 on your server or computers to make an old scanner work, as it reopens a well-known security hole.
Scanning to the cloud instead
With files increasingly in SharePoint and OneDrive rather than on a local server, scanning to a network folder makes less sense. Many devices now support scanning straight to SharePoint or OneDrive through a manufacturer app or connector. Alternatively, scan to a monitored folder that syncs to SharePoint, or scan to email and file the attachment from Outlook.
Choose based on how documents are used next. Accounts teams may prefer scanning into an inbox that their accounting software watches, while practices might scan directly into a client folder. A short conversation with the people who scan most often usually reveals the simplest workflow.
Making it reliable from now on
Document how scanning is set up: which method, which account or connector, which IP address, folder paths and credentials (stored in a password manager, not on a note). Record the details in the same place as the device's admin password and firmware version. When something changes, whoever fixes it won't have to start from scratch.
Add scanning to your change checklist. Before resetting a service account password, changing internet provider, replacing a server or tightening Microsoft 365 security, check whether the scanners depend on it. A two-minute test scan after each change catches problems before the accounts team discovers them on a busy day.
Firmware updates on the device itself also help. Manufacturers regularly add support for newer security protocols, modern Microsoft 365 sign-in and cloud connectors. A device several years behind on firmware may be missing exactly the feature that would make scanning reliable again, so check for updates before deciding the hardware is the problem.
In short
- Check the device's error message and what changed recently.
- Basic SMTP sign-in to Microsoft 365 is often blocked; use a relay or modern auth.
- Never use a staff member's mailbox for the scanner.
- Don't re-enable SMB1 to suit an old scanner; update its firmware.
- Document scanning setup and test it after any related change.
