Google Is Ending Gmail “Send As” in 2027: What Businesses Should Do

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

Google is changing how Gmail handles third-party email accounts. From January 2027, Gmail will discontinue “Send as” for third-party email addresses, Gmailify and web-based POP retrieval. Google Workspace aliases and Gmail-to-Gmail “Send as” are not affected.

For businesses using custom-domain email hosted outside Google, this is a chance to review security, encryption and data control.

What Is Changing?

Third-party “Send as” lets Gmail users send mail using an external email address. Google is ending this capability in January 2027, so organizations using external mailboxes through Gmail should identify and replace these dependencies during 2026.

Check whether employees send from employee@company.com through Gmail while mail is hosted elsewhere or depend on Gmailify/POP.

What Should Businesses Do?

Businesses can use their existing provider, a desktop client or Gmail mobile app. Enterprises should consider a dedicated Business Email Solution with custom-domain email, security and flexible deployment.

Evaluate SPF, DKIM, DMARC, encryption, S/MIME, PKI, cloud, private cloud, sovereign cloud and on-premise deployment.

Why SPF, DKIM, DMARC and S/MIME Matter

SPF, DKIM and DMARC authenticate email, while S/MIME adds certificate-based signing and encryption. SPF authorizes sending servers, DKIM adds signatures, and DMARC defines policies for authentication failures.

Poor DNS configuration can cause delivery problems, spam placement and spoofing risks. S/MIME adds protection for sensitive communications.

Practical application: Audit SPF, configure DKIM, establish DMARC monitoring and review S/MIME.

Cloud, Private Cloud, Sovereign Cloud or On-Premise?

Cloud offers scalability; private cloud, sovereign cloud and on-premise deployment provide greater control. The right model depends on compliance, security and data-residency requirements.

• Cloud: Fast deployment and scalability.

• Private Cloud: Greater control.

• Sovereign Cloud: Data sovereignty.

• On-Premise: Maximum infrastructure control.

Where XgenPlus Fits

XgenPlus provides a modern Business Email Solution for organizations seeking greater control over email infrastructure.

It supports custom-domain email, SPF/DKIM/DMARC, encryption, S/MIME, PKI, cloud, private-cloud, sovereign-cloud, on-premise deployment, DLP and AI Compose.

Migration Checklist

1. Audit “Send as” accounts and third-party domains.

2. Review Gmailify, POP, SMTP and forwarding.

3. Validate SPF, DKIM and DMARC.

4. Review encryption and S/MIME.

5. Check applications that send email.

6. Select, pilot and test the new platform.

7. Retire legacy configurations after validation.

Key Takeaways

Third-party Gmail “Send as” ends in January 2027. Gmailify and web-based POP retrieval are also being discontinued, while Google Workspace aliases are not affected. Businesses should audit email infrastructure, authentication, encryption and deployment requirements during 2026.

Conclusion

Google’s 2027 change is a deadline—and an opportunity to modernize business email. Organizations should evaluate security, authentication, encryption, data sovereignty and long-term control.

Prepare before January 2027. Move beyond fragmented email infrastructure with a secure, flexible and enterprise-ready Business Email Solution from XgenPlus.