Scan-to-Email is convenient, but convenience should not create an uncontrolled path for business information. OAuth sounds complicated because the authorization flow happens in a browser, but the security idea is straightforward: an application gets limited permission without receiving the user's normal password.
Why this matters
Access tokens are time-limited.
Permissions can be limited to specific activities such as sending mail.
Think in terms of least privilege
The copier should be allowed to do what the business needs and no more. That means limiting who can use the relay, where messages can go, which mailbox or account is involved, and how much access the relay itself receives from Microsoft or Google.
Practical points to consider
- Consent can be revoked without changing the account password.
- Refresh tokens can maintain service continuity while still being centrally revoked.
- Legacy copiers can gain these benefits through a relay even when they cannot implement OAuth themselves.
What a supportable setup looks like
A good Scan-to-Email design should be understandable months after it is installed. IT should know which device is sending, which cloud connection is being used, which destinations are permitted, and where to look when delivery fails.
That usually means using a dedicated or clearly owned sender identity, encrypted credentials or tokens, modern TLS on the cloud side, useful logs, and a documented reconnect process. It also means avoiding broad permissions simply because they are easier to configure.
Where CM Relay fits
CM Relay is designed as the compatibility and policy layer between copiers or other SMTP devices and modern cloud services. The copier can continue using a familiar SMTP workflow while CM Relay handles OAuth-based delivery, connection health, logging, and policy controls such as sender and destination restrictions.
That approach lets an organization modernize the email path without turning a copier replacement project into the only security option.
Further reading
- https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/authenticated-client-smtp-submission
- https://developers.google.com/workspace/gmail/imap/xoauth2-protocol
Next step
If your organization is still relying on old SMTP credentials, inconsistent copier settings, or manual workarounds, start by documenting the current Scan-to-Email path. From there, you can decide which parts need to be modernized without disrupting the user experience.
https://cmrelay.com/features/ or https://cmrelay.com/contact/ to discuss your environment.