Home  /  Guides  /  Scan to Email Setup
ABT Guide

How to Set Up Scan to Email on a Copier

A current, plain-English guide to configuring scan-to-email with Microsoft 365, Google Workspace, Gmail, and other email providers—including modern authentication, relay options, app passwords, copier settings, and the fixes for systems that suddenly stopped working.

Published
Reviewed By ABT Service Team
Technical Review
Current For Microsoft 365 & Google Workspace
The 60-Second Concept

Your Copier Is an Email-Sending Device

When a copier emails a scan, it connects to an outgoing mail service, proves that it is allowed to send, and attaches the scanned document to a message. Most scan-to-email failures originate in one of four places:

  • 01The email delivery method — OAuth, SMTP relay, Direct Send, an app password, or another provider-supported method.
  • 02The mail server settings — server name, port, encryption type, sender address, and authentication setting.
  • 03The copier's network settings — a valid IP address, default gateway, DNS server, date, time, and access through the firewall.
  • 04The copier's security capabilities — current firmware, TLS 1.2 or newer where required, certificate validation, and support for the authentication method your email provider now expects.
Why It Can Suddenly Stop WorkingIf scanning worked for years and stopped without anyone changing the copier, the copier itself may be fine. A mailbox password may have changed, an app password may have been revoked, the company may have migrated email providers, or Microsoft or Google may have tightened the authentication policy. The exact error usually points to which layer changed.

Organizations that want ongoing help with driver changes, address books, scan settings, and other everyday printer issues can review ABT Concierge. For broader fleet monitoring, automatic toner fulfillment, and centralized support, see Managed Print Services.

Preparation

Gather These Five Things First

A few minutes of preparation prevents the stop-search-restart cycle that makes this job feel harder than it is.

  • 01A dedicated scanner identity or sender address — for example scanner@yourcompany.com. Avoid using an employee's personal mailbox. Account-authenticated methods may require a licensed mailbox; relay-based methods may not.
  • 02Administrative access to the email environment — Microsoft 365, Google Workspace, or the control panel for your other email provider. Some methods require an email administrator to create a connector, relay rule, or application consent.
  • 03The copier's IP address — print a network configuration report or locate it under a menu such as Settings › Network › TCP/IP. You will use it to configure the device from a browser.
  • 04The exact manufacturer, model, and firmware version — OAuth and modern TLS support vary by device and firmware. Check for a firmware update before assuming the copier is too old.
  • 05The delivery requirement — decide whether the copier must send only to employees inside your domain or also to customers, vendors, and other outside addresses. That answer determines the correct Microsoft and Google path.
Do Not Use an Employee's Everyday PasswordA password change, employee departure, or account security event can silently break scanning. Use a dedicated identity, app password, OAuth connection, or restricted relay configuration instead.
Microsoft 365

Choose the Right Microsoft 365 Setup

There is no longer one Microsoft 365 configuration that is best for every copier. The correct method depends on whether the device supports OAuth, whether scans must go outside your organization, and whether the office has a static public IP address or certificate that can secure a relay connector.

Internal Only

Direct Send

Use this when scans only need to reach Microsoft 365 recipients inside your organization and the device cannot use OAuth.

  • No mailbox password required
  • No licensed mailbox required
  • Can be blocked tenant-wide by the Microsoft 365 administrator
  • Cannot deliver to Gmail, Yahoo, customers, or vendors
Temporary Legacy Path

Password-Based SMTP AUTH

This may still work for existing tenants and older copiers, but Microsoft is moving away from Basic Authentication. Treat it as a transition plan, not a permanent design.

  • Requires a licensed Microsoft 365 mailbox
  • Blocked by Security Defaults and many Conditional Access policies
  • Scheduled to be disabled by default in existing tenants at the end of December 2026

Option 1: OAuth / Modern Authentication

Start here when the copier's email setup includes a button or option such as Sign in with Microsoft, OAuth 2.0, Modern Authentication, or Exchange Online. Update the copier's firmware first, because manufacturers often add or repair OAuth support through firmware updates.

SMTP serversmtp.office365.com
Port587
EncryptionSTARTTLS — TLS 1.2 or newer
AuthenticationOAuth 2.0 / Modern Authentication
MailboxDedicated, licensed Microsoft 365 mailbox
From addressUse the authenticated mailbox unless Send As permission is configured

The exact registration and sign-in steps are manufacturer-specific. Some devices open a Microsoft sign-in page and request administrator consent; others require an application registration or vendor cloud service. Follow the copier manufacturer's instructions for that exact model.

Option 2: Direct Send for Internal Recipients

Direct Send May Be DisabledMicrosoft 365 administrators can block Direct Send across the tenant with the RejectDirectSend setting because unauthenticated Direct Send can be abused for spoofing. If this method fails immediately even though the MX endpoint, sender domain, network, and port are correct, ask the Microsoft 365 administrator whether Direct Send has been blocked tenant-wide.
  1. Find Your Microsoft 365 MX Endpoint

    Look up the MX record for your Microsoft 365 domain. It normally resembles yourdomain-com.mail.protection.outlook.com. Use the actual MX endpoint for your domain—not smtp.office365.com.

  2. Enter the Direct Send Settings

    SMTP serverYour domain's Microsoft 365 MX endpoint
    Port25
    EncryptionSTARTTLS when supported
    AuthenticationNone
    From addressAn address in your accepted Microsoft 365 domain
    DeliveryRecipients inside your Microsoft 365 organization only
  3. Verify Domain Authentication and Port Access

    Have the email administrator verify the domain's SPF, DKIM, and DMARC configuration. Confirm the office firewall and internet provider allow outbound port 25, and ask whether the tenant-wide RejectDirectSend setting is enabled. If the copier sends internally but not externally, that is expected behavior for Direct Send.

Option 3: Microsoft 365 SMTP Relay

SMTP relay is often the best answer for an older copier that cannot use OAuth but must send scans to people outside the organization. An administrator creates an inbound connector that recognizes the office by a TLS certificate or a static public IP address. Dynamic public IP addresses are not supported for IP-based Microsoft 365 relay authentication.

SMTP serverYour domain's Microsoft 365 MX endpoint
Port25
EncryptionSTARTTLS — TLS 1.2 or newer
AuthenticationInbound connector using certificate or static public IP
Username / passwordNot entered on the copier for IP- or certificate-based relay
From addressAny address in an accepted Microsoft 365 domain
DeliveryInternal and external recipients
Administrator-Level ConfigurationThe connector must be restricted carefully so your domain does not become an open relay. Use only the office's verified static public IP address or an approved certificate, require TLS when the device supports it, and test external delivery after the connector is active.

Option 4: Temporary Password-Based SMTP AUTH

Microsoft 365 Transition Warning — July 2026Microsoft says current SMTP AUTH Basic Authentication behavior remains unchanged through December 2026. At the end of December 2026, it is scheduled to be disabled by default for existing tenants, and new tenants created after December 2026 will have it unavailable by default. Microsoft recommends OAuth. Do not build a new long-term scanning strategy around a stored mailbox password.

If the copier cannot support a durable authentication method even after a firmware update, compare the cost of continued workarounds with replacement using our Upgrade vs. Keep guide. Organizations considering new equipment can also review the Business Printer Leasing Guide.

  1. Enable Authenticated SMTP for the Dedicated Mailbox

    In the Microsoft 365 admin center, go to Users › Active users, open the dedicated scanner account, select Mail › Manage email apps, and enable Authenticated SMTP. This only enables the mailbox-level setting; tenant security policies can still block Basic Authentication.

  2. Enter the Transitional Settings

    SMTP serversmtp.office365.com
    Port587
    EncryptionSTARTTLS — TLS 1.2 or newer
    AuthenticationOn — username and password
    UsernameThe full licensed mailbox address
    PasswordThe dedicated mailbox password
    From addressMatch the authenticated mailbox unless Send As is granted
  3. Do Not Disable Organization-Wide Security

    Microsoft Security Defaults and Conditional Access policies commonly block Basic Authentication. Do not turn off MFA, Security Defaults, or a company-wide legacy-authentication block just to make one copier work. Move the device to OAuth, Direct Send, SMTP relay, or a properly secured third-party relay.

Not Sure Which Microsoft Path Fits Your Copier?

Send ABT the manufacturer, model, firmware version, email domain, and whether scans must go to outside addresses. Those details usually identify the correct method before anyone begins changing settings. Existing and prospective customers who need recurring remote help can also review ABT Concierge.

Submit the Copier Details ›
Google Workspace & Gmail

Use SMTP Relay for Workspace—or an App Password for a Simple Gmail Setup

Google recommends its SMTP relay service for printers, scanners, and business applications in a Google Workspace environment. A personal Gmail account or a simple one-device setup can use smtp.gmail.com with a 16-character app password.

Google Workspace: SMTP Relay Is the Recommended Method

  1. Create a Restricted Relay Rule

    In the Google Admin console, open the Gmail routing settings and configure the SMTP relay service. Restrict the rule to approved senders and the office's public IP address or another Google-supported authentication method. Require TLS when the copier supports it.

  2. Enter the Relay Settings on the Copier

    SMTP serversmtp-relay.gmail.com
    Port587 with STARTTLS preferred; Google also supports 25 or 465
    EncryptionSTARTTLS / TLS when supported
    AuthenticationAs configured in the Google Workspace relay rule
    From addressAn address permitted by the relay rule
    DeliveryInternal and external recipients
  3. Test from the Office Network

    If the relay authenticates by public IP address, test while the copier is on the approved office internet connection. A dynamic public IP can change and break an IP-restricted relay, so verify the internet service arrangement before choosing that design.

Why Relay Is Better for Multiple DevicesThe organization controls one restricted delivery policy instead of storing a separate Google account password on every copier. It is easier to audit, easier to revoke, and Google identifies SMTP relay as the recommended and most secure option for Workspace devices and apps.

Personal Gmail or Simple Account Authentication: Use an App Password

  1. Turn On 2-Step Verification

    Sign in to the dedicated Google account, open Google Account › Security, and enable 2-Step Verification. App passwords are available only after 2-Step Verification is active.

  2. Create a 16-Character App Password

    Open the account's App Passwords page and create a password named “Copier.” Copy it immediately because Google displays it only once. Enter the 16 characters on the copier without spaces.

  3. Enter the Gmail SMTP Settings

    SMTP serversmtp.gmail.com
    Port587 with STARTTLS, or 465 with SSL
    AuthenticationOn — username and app password
    UsernameThe full Gmail or Google Workspace email address
    PasswordThe 16-character app password
    From addressThe same Google account address
When App Passwords Are MissingThe option may be unavailable when the account uses Advanced Protection, 2-Step Verification is configured only with security keys, or a work or school administrator prevents app passwords. Google also revokes app passwords after the main Google Account password is changed, so create a new app password if scanning stops immediately after a password change.

Restricted Gmail SMTP: A Limited Special Case

Google Workspace also offers aspmx.l.google.com on port 25 without authentication, but it can send only to Gmail or Google Workspace users and requires IP allowlisting and correct SPF configuration. Because the delivery limits are easy to misunderstand, most organizations are better served by the normal Workspace SMTP relay.

Every Other Email ProviderThe pattern is similar, but do not guess. Obtain the provider's current SMTP server, supported port, required encryption, authentication method, sender restrictions, and any app-password requirement. Port 587 with STARTTLS is common, but not universal.
The Device Side

Enter the Settings Through the Copier's Web Page

Most network-connected business copiers have a web administration page. Configuring email from a computer is faster and less error-prone than typing server names and credentials on a small touchscreen.

  1. Open the Copier's Web Administration Page

    From a computer on the same trusted network, enter the copier's IP address in a browser. Try https://<copier IP> first when the device supports HTTPS. Some older devices use http://<copier IP>. Never expose this page directly to the public internet.

  2. Sign In as the Device Administrator

    HP often calls this the Embedded Web Server, Canon the Remote UI, Brother Web Based Management, and other manufacturers use similar names. Change any default administrator password before storing email credentials on the device.

  3. Find Email, SMTP, or Digital Send Settings

    Look for a path such as Network › Email, Scan/Digital Send › Email Setup, Send › E-Mail Settings, or SMTP. Enter the settings for the Microsoft, Google, or other-provider method selected above.

  4. Confirm the Device Clock and Firmware

    Verify the date, time, time zone, DNS server, default gateway, and firmware version. A wrong clock can make a valid security certificate appear expired or not yet valid, while outdated firmware can prevent TLS or OAuth from working.

  5. Run a Connection Test and a Real Scan

    Use the device's Test connection or Send test email feature first. Then scan a real page to an internal address and, when external delivery is required, to an outside address. Record the exact error code if either test fails.

  6. Build the Address Book and Sensible Defaults

    Add staff addresses and one-touch destinations through the browser. For everyday documents, start with PDF at 200 or 300 DPI. Use grayscale or black and white when color is unnecessary. Higher resolutions increase attachment size quickly.

Large DocumentsEmail providers normally enforce message-size limits. When long scans exceed those limits, reduce resolution, use black and white, split the document, enable high-compression PDF if supported, or use scan-to-folder or secure cloud scanning instead of email.
Secure the Configuration

Make It Work Without Creating a New Security Problem

A functioning scan-to-email setup should also be restricted, documented, and easy to revoke.

  • 01Use a dedicated scanner identity rather than an employee's everyday account.
  • 02Prefer OAuth or a restricted relay over storing a reusable mailbox password on the copier.
  • 03Restrict relay permissions to approved sender domains, office IP addresses, certificates, and recipient types.
  • 04Change default copier administrator credentials and keep the web page reachable only from trusted internal networks or approved management channels.
  • 05Store the configuration securely — document the method, sender identity, relay owner, firmware version, and recovery steps without recording reusable passwords in an unsecured file.
  • 06Revoke access when the device is retired — remove app passwords, OAuth grants, relay permissions, address books, and stored credentials before a copier is returned, sold, or recycled. Organizations that need ongoing device maintenance and support can also review ABT's printer and copier service plans.
When the Test Fails

Scan-to-Email Troubleshooting

Match the exact symptom or error to the most likely cause. Do not change several settings at once—you will lose the clue that identifies the real problem.

Error: Authentication failed / SMTP login rejected

The Authentication Method or Credential Is Wrong

Confirm the full email address is used as the username. For Gmail, use the app password rather than the normal account password. For Microsoft 365, verify whether the device is using OAuth or legacy SMTP AUTH and whether the mailbox and tenant permit that method. Security Defaults and Conditional Access can block password-based SMTP even when the mailbox setting is enabled.

Error: 5.7.60 / Client does not have permission to send as this sender

The From Address Does Not Match the Authenticated Mailbox

Set the copier's From or Device Email address to the same mailbox used to authenticate. If a different sender address is required, a Microsoft 365 administrator must grant the authenticating account Send As permission for that address.

Error: TLS, certificate, handshake, or secure connection failed

The Copier Cannot Complete the Required Encryption

Confirm the device supports TLS 1.2 or newer where the provider requires it, update the copier firmware, and verify the device's date, time, and time zone. A wrong clock can cause certificate validation to fail. Also confirm the selected port matches the encryption type: commonly 587 with STARTTLS or 465 with SSL for Gmail.

Symptom: Microsoft Direct Send fails immediately for internal recipients

Direct Send May Be Blocked Tenant-Wide

Microsoft 365 administrators can enable RejectDirectSend to reject unauthenticated messages sent through the tenant's MX endpoint. Confirm the MX record, sender domain, DNS, gateway, and outbound port 25 first. If those are correct, ask the Microsoft 365 administrator whether Direct Send has been disabled for the organization. Use OAuth or a properly restricted SMTP relay instead of weakening the tenant's security policy.

Symptom: Sends to coworkers but fails to outside addresses

The Configuration Is Internal-Only

Microsoft Direct Send cannot deliver to external recipients. Google's restricted SMTP server is also limited. Move to OAuth, Microsoft 365 SMTP relay, Google Workspace SMTP relay, Gmail SMTP with an app password, or another method that explicitly permits external delivery.

Symptom: Scans arrive in junk or are rejected as spoofed

The Sender or Domain Authentication Needs Attention

Use a sender address permitted by the selected method. Have the email administrator verify SPF, DKIM, DMARC, relay restrictions, and the From address. An invented or unauthorized sender address is more likely to be filtered or rejected.

Symptom: Short scans arrive but long scans disappear

The Message Is Exceeding an Attachment Limit

Lower the default resolution to 200 or 300 DPI, use grayscale or black and white, enable compressed PDF, split the document, or use scan-to-folder or a secure cloud workflow. Scan-to-folder avoids normal email attachment limits, although the destination still has its own storage and file-size rules.

Error: Cannot connect to server / connection timed out

The Copier Cannot Reach the Mail Service

Verify the SMTP server name and port, then confirm the copier has a valid default gateway and approved DNS server. The gateway is normally the router or firewall address on the copier's subnet; DNS may be the router, an internal server, or another approved resolver. Check whether the firewall or internet provider blocks the required outbound port. Multi-device environments may benefit from managed print monitoring so network and device issues can be tracked centrally.

Symptom: Worked for years and stopped after a password or policy change

The Stored Authorization Was Revoked or No Longer Allowed

Google app passwords are revoked after the main account password changes. Microsoft 365 policies can disable legacy SMTP authentication. A provider migration changes the server settings entirely. Identify what changed on the email side and update only the affected credential, policy, or delivery method.

Symptom: The test passes but the scan never appears

The Connection Worked, but Delivery Did Not

Check the recipient address, junk folder, message trace or email logs, attachment size, sender permissions, and whether the chosen method permits that recipient. A successful connection test proves the copier reached the server; it does not always prove the final message was accepted and delivered.

Common Questions

Scan-to-Email FAQ

These answers summarize the most common setup decisions. The detailed sections above explain when each method is appropriate.

What is the best way to set up scan to email with Microsoft 365?
Use OAuth or Modern Authentication when the copier supports it. For an older device, use Direct Send when scans only go to internal Microsoft 365 recipients, or a properly restricted Microsoft 365 SMTP relay when the device must send internally and externally. Password-based SMTP AUTH should be treated as a temporary legacy method.
Can I still use smtp.office365.com with a username and password?
It may still work for an existing tenant when Authenticated SMTP is enabled and tenant security policies allow Basic Authentication. Microsoft says current behavior remains unchanged through December 2026, then Basic Authentication for SMTP AUTH is scheduled to be disabled by default for existing tenants. Use OAuth or another supported delivery method for a durable setup.
How do I set up scan to email with Google Workspace?
Google recommends the SMTP relay service at smtp-relay.gmail.com for printers, scanners, and applications. Configure a restricted relay rule in the Google Admin console, then connect the copier using a supported port and TLS. The rule should limit who can send and how the device is authenticated.
How do I use Gmail for scan to email?
Enable 2-Step Verification on the dedicated Google account, create a 16-character app password, and configure the copier with smtp.gmail.com, port 587 with STARTTLS or port 465 with SSL. Use the full email address as the username and the app password instead of the normal Google Account password.
Why did scan to email suddenly stop working?
Common causes include a changed mailbox password, a revoked Google app password, an email-provider migration, a new Microsoft or Google security policy, expired or incompatible TLS support, incorrect device time, or a firewall change. Record the exact error before changing the configuration.
Why do long scans fail while short scans work?
The message is probably exceeding an email attachment-size limit. Reduce the resolution to 200 or 300 DPI, use grayscale or black and white, enable compressed PDF, split the scan, or use scan-to-folder or secure cloud scanning for large documents.

Prefer to Skip the Trial and Error?

ABT configures print drivers, network settings, address books, and scan-to-email—and tests the complete workflow before the job is finished. When an email provider changes its rules, we diagnose the account, network, and copier together instead of guessing at one system in isolation. For recurring remote support, review ABT Concierge; for multi-device fleet oversight, see Managed Print Services.