SendAs Relay

Guides › Workspace Send As External Domain in 2027: What Changes

Workspace Send As External Domain in 2027: What Changes

Updated 2026-10-03 · by Adam Hale

Google Workspace users lose "Send as" for external domains in January 2027, just like personal Gmail users. Workspace aliases, and any domain added to your Workspace organization, keep working. Addresses at domains Google doesn't host for you stop working: a partner's domain, a personal Yahoo address, or a brand domain still on another mail host. For admins, the main fix is to bring owned domains into Workspace; for addresses you can't bring in, users need another way to send.

What Google says, and what admins are being told

Google's help page draws the line at hosting, not at account type:

Source: Gmail Help 17101213.

Admin notices make the Workspace impact explicit. An admin email quoted on r/gsuitelegacymigration says: "Starting January 2027, the Send-As feature will no longer be available for external, non-Google Workspace domains." Keio University's IT center told its users the same on 2026-08-04 (Keio notice).

Who in a Workspace organization is affected

Scenario After January 2027
User alias in your primary domain Keeps working
Address in a user alias domain or secondary domain you added Keeps working
Google Group address in your domain Keeps working (Google-hosted)
A domain you own but host elsewhere (an old brand on Zoho or Microsoft 365) Removed, unless you move it into Workspace
A partner's or client's domain, added with their SMTP server Removed
A personal Yahoo or Outlook address added to a work account Removed
University departments sending as addresses on non-Google servers Removed (the Keio case)

Workspace send as external domain in 2027: admin options

1. Bring domains you own into Workspace

In the Admin console, go to Account, then Domains, then Manage domains, then Add a domain. Google offers two types (Workspace Help):

You must own and verify the domain. Google allows up to 599 additional domains, including up to 20 user alias domains (multiple-domains FAQ). For mail to arrive in Workspace, the domain's MX records must point to Google. If the domain's mail lives elsewhere today, that's a migration, so plan the cutover. (Our reading of Google's help, not confirmed with Google:) an alias domain doesn't add license cost, because it only gives existing users extra addresses.

2. Domains you can't bring in

You can't add a client's or partner's domain to your organization. The address has to send from that domain's own system:

3. Personal addresses on work accounts

Personal Yahoo or Outlook addresses on a work account are mostly a policy question. Many organizations will simply let this one lapse.

Copies in Sent and app passwords on work accounts

Users replacing Send as with an external tool often want a copy in their Workspace Sent folder. That usually means IMAP with an app password. Google's help notes that the app-password option may be missing when "you're logged into a work, school, or another organization account" (Account Help 185833). Expect to rely on Bcc-to-self unless your admin policy allows app passwords. See copy sent mail to Gmail's Sent folder.

Google's warning, from an IT point of view

Google cautions against "third-party tools or browser extensions that offer to replicate 'Send as'" because they "often require access to your email credentials or OAuth tokens". For an organization, ask the usual vendor-review questions. Where are credentials stored? Does mail transit a vendor's server? Is the code auditable? Can we run the server part in our own account? A tool you can't answer those questions about shouldn't touch company mail.

How SendAs Relay fits

SendAs Relay can fill the gap for an external address that has its own SMTP server, if your organization's policies allow it:

Not the right fit for domains you can move into Workspace (do that instead), for Outlook.com/Hotmail or Microsoft 365 addresses that only allow Microsoft sign-in, for Chrome-only fleets, or for mobile users. Read security and privacy before a rollout.

Sources