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

IT teams should inventory:

1. All domains.
2. All MX records.
3. SMTP servers.
4. Gmail “Send as” configurations.
5. POP-based mailbox retrieval.
6. Forwarding rules.
7. Email aliases.
8. SPF, DKIM and DMARC records.
9. Encryption and S/MIME requirements.
10. Regulatory or data-residency requirements.

Key takeaway: Don't wait for January 2027. Q3–Q4 2026 is the transition window Google recommends for migration.

What Should Businesses Do Before January 2027?

The safest approach is to identify every affected mailbox, determine where the authoritative mailbox is hosted, then move users to a supported architecture rather than simply replacing Gmail “Send as.” For businesses, the preferred long-term solution is usually a properly managed business email platform with authenticated sending, encryption, centralized administration and appropriate deployment control.

Option 1: Use the original email provider

Businesses can access mail through the provider's native webmail or application.

Best for: small teams with straightforward requirements.

Limitation: It may not provide the centralized security, administration or deployment flexibility expected by larger organizations.

Option 2: Use a desktop email client

Desktop clients can connect to supported mail systems through protocols such as IMAP and SMTP.

Best for: users managing multiple independent accounts.