Google Is Ending Gmail’s Third-Party “Send As”: What to Do Before 2027

employee@company.com → third-party mail server → Gmail interface → customer

If Gmail is being used to send as employee@company.com, the organization may have built an operational dependency around a feature that will no longer exist in January 2027.

Key takeaway: This is not simply a Gmail settings change. For organizations dependent on third-party mail infrastructure, it is an opportunity to reassess email architecture, security, authentication, and data control.

Who Will Be Affected by the Gmail “Send As” Shutdown?

Organizations are affected when Gmail is used to send from an email address hosted outside Google. The impact is especially relevant to companies using custom-domain business email, legacy mail servers, hosted email providers, or hybrid configurations where Gmail is only the user interface rather than the actual email platform.

Definition

A third-party email account is an email account hosted by a provider other than Google, for example, a mailbox hosted on another business email platform or mail server.

Examples

You should investigate your environment if employees currently:

• Send from name@company.com through Gmail while the mailbox is hosted elsewhere.
• Use Gmail to send from Yahoo, Outlook or another non-Google account.
• Fetch messages from an external mailbox using Gmail POP.
• Depend on Gmailify to provide Gmail features to a third-party mailbox.
• Use multiple email domains across different providers.

Google specifically notes that third-party “Send as” addresses such as non-Gmail accounts will be affected.

Practical application