Scan to email has stopped working

You put a document on the office copier, choose the scan-to-email option, and something goes wrong — the screen shows an error, or the job appears to go through perfectly and the email never arrives. It's a maddening one, because nothing looks broken. The machine hums, the paper feeds, the display goes back to normal.

The reassuring part first: the scanner itself is almost certainly fine. What's stopped is the second half of the job, where the device hands the file to your email system and asks it to send. That step lives outside the machine, and it's where these failures nearly always are.

What actually broke (and what didn't)

"Scan to email" is two jobs the device does back to back. First it scans: the paper goes past the glass and becomes a PDF. Then it sends: the device connects to your email system, identifies itself, and asks that system to deliver the PDF to the addresses you picked.

The first half rarely fails quietly — a scanning fault normally shows up as a jam, a streak down the page, or a hardware message on the panel. The second half is the fragile one, because it depends on your email service continuing to accept the device. And your email service isn't part of the copier. It's run elsewhere, by Microsoft, with its own security rules that change over time.

Why a device that worked for years suddenly stops

Your copier has no private back door into email. Like any mail app, it has to prove who it is before your email system accepts anything from it. When that proof stops being accepted, sending stops — usually with no warning, because nothing on the device changed. Something changed on the other side. Three causes account for most of these:

• The account it signs in as changed. Some devices send by signing in to a real mailbox with a password, exactly as Outlook does. If that password is reset, or the account is disabled when someone leaves, the device is turned away at the door.
• The security rules tightened. Turning on multi-factor authentication requirements for your organization, for example, switches off the older and simpler sign-in method many of these devices depend on. That's good for your security and inconvenient for your copier, and the two have to be reconciled deliberately.
• The way the device sends can't reach that recipient. There are a few different ways a device can be set up to send, and one of them only delivers to addresses inside your own organization — it cannot reach an outside address such as a client's Gmail account at all. If scans reach colleagues but never anyone outside, that's a strong clue and one of the most useful things you can tell us.

Worth holding on to: only one of those sending methods uses a mailbox password at all. That's why "just retype the password" is so often not the fix.

Five checks worth doing first

These take about five minutes between them, none of them involve changing a setting, and every one makes the fix faster.

1. Read the device's screen and write down exactly what it says. Word for word, including any code, however meaningless it looks — or take a photo of the panel. This one line often identifies the cause outright.
2. Check that everything else on the device still works. Make a photocopy, and print a page to it from your computer. If both work, the device is on the network and healthy and we can concentrate on the sending step. If it also shows as offline when you print from Windows, that's a different problem — see Printer shows offline.
3. If the device offers scan to a folder or to a USB drive, try one. If the file lands, the scanning half is confirmed fine and you have a workaround for today.
4. Find out how wide the problem is. Scan to yourself, then to a colleague, then to an address outside the company. "Nothing sends at all", "only outside addresses fail" and "one saved address fails" point at three different causes.
5. Check the junk folder — the recipient's, and your own. A scan from a copier is odd-looking email: an attachment, no message body, from an address nobody replies to. That's exactly the shape a spam filter second-guesses. And if a bounce or undeliverable notice came back to anyone, keep it.

Please leave the device's settings alone

This is the part we'd most like you to take away. A device's email settings look simple — a server name, a port number, a user name, a password — and they're anything but. They have to match your organization's mail configuration exactly, and the right values depend on which sending method the device was set up to use in the first place.

• Retyping the password usually isn't the fix. If your device uses one of the methods that doesn't involve a mailbox password, there's nothing to correct, and entering one turns a working configuration into a broken one.
• It erases the evidence. The current settings are our record of how the device worked before it stopped. Once they've been typed over, a fix that would have taken one look becomes a rebuild from scratch.
• You'll probably hit a locked door anyway. On many devices that settings page sits behind a device administrator password, and that's deliberate.

What we check at our end

• Whether the account the device signs in as still exists, still has a working password, and is still permitted to send.
• Whether a change to your organization's sign-in security switched off the method the device depends on.
• Whether the device is permitted to send to the recipients you're trying to reach — inside the company, outside it, or both.
• Whether the scan reached your email service at all. There's a search we can run inside your Microsoft 365 email system that shows what it received and what it did with it, which usually settles within minutes whether the fault is on the device side or the mail side.

All of those are changes to your Microsoft 365 settings or to settings behind the device's administrator password. That's why we can't walk you through this one — not because it's difficult, but because the controls genuinely aren't available to a standard user account.

What to include in your support request

This is what decides whether it's fixed today or on Thursday. The more of this you can answer in your first message, the more we can diagnose before anyone sets foot in your office.

1. Which device, and where it is. The make and model from the label on the front, plus the room or floor — "the copier in the second-floor workroom". Most offices have more than one, and the distinction matters.
2. Exactly what the device says, word for word. Copy the panel message precisely, including any error code, or send a photo of the screen. Please don't summarize — the difference between two similar-sounding messages is often the entire diagnosis.
3. When it last worked. Even roughly. "It worked Friday, it didn't Monday" narrows things enormously, because we can line that up against what changed over that weekend.
4. Who it fails for. All recipients or only some? Does it reach people inside your company but not outside it? Does one saved address in the device's address book fail while others work? And is it failing for everyone in the office, or only when you send?
5. What still works. Printing, copying, scan to folder, scan to USB — which you tried and what happened. This is how we separate a device problem from an email problem in one step.
6. Any bounce message, forwarded intact. If an undeliverable notice came back, forward the actual message rather than retyping what it said. The technical wording buried in those notices frequently names the exact cause.
7. Anything that changed recently, even if it seems unrelated. A password reset, someone leaving, a new sign-in prompt appearing for staff, a network or internet change at the office. You may not think it's connected — tell us anyway, because it very often is.

Send that to [email protected], or submit a support request and paste it in. If you'd like to know what happens next, Submitting a support request walks through the process.

Keeping work moving in the meantime

• Scan to a folder or a USB drive if your device offers it, then attach the file to an email yourself. A few extra clicks, same document — and it sends from your own mailbox, so whatever is blocking the device doesn't apply.
• For a page or two, your phone's camera is often good enough. Fine for a signed note or a receipt; less so for a twenty-page contract someone has to read.
• Scanned documents get large quickly. If the file turns out to be too big to email, sharing files too large to email covers better ways to send it.