Google has added a deadline to a long-standing Gmail convenience feature: starting in January 2027, Gmail will no longer support “Send as” for third-party email addresses.
That means a user who signs into a consumer Gmail account will no longer be able to compose a message that appears to come from an external address, such as a Yahoo or Outlook account—or, crucially for many small businesses, an address on a custom domain hosted outside Google.
Google’s notice says the change does not affect Google Workspace aliases or other Gmail addresses a user owns.
What is changing
Gmail’s “Send mail as” setting has let users attach alternate addresses, verify control of them and select those addresses in the From field. It has been particularly useful for founders, consultants and small teams that want one Gmail inbox and workflow while presenting mail from a business domain.
After the cutoff, that approach will no longer work for third-party addresses. Google points users to its guidance on changes to third-party email account support, but the immediate operational message is clear: Gmail should not be treated as a permanent sending interface for externally hosted identities.
The policy does not mean companies must abandon a custom domain. It means they need an email setup that natively supports sending from that domain, rather than relying on a consumer Gmail account’s alternate-From configuration.
Why operators should care
For an individual, this may be an inconvenience. For a business, the risk is more practical: a change in the visible sender address can disrupt customer trust, reply handling, sales outreach, invoicing, support queues and automated workflows.
The affected setups may be hard to spot because they are often configured by a founder or former employee, rather than centrally managed by IT. A company might own `name@company.com` but have staff sending it through personal Gmail accounts. That configuration can also leave replies routed to the underlying Gmail address unless the user separately set a reply-to address.
Teams should also distinguish between a true alias in Google Workspace and an externally hosted mailbox added to Gmail. Google explicitly says Workspace aliases are unaffected; third-party addresses are the category being retired.
What to do before 2027
Start with an inventory:
1. Identify every Gmail account using “Send mail as.” Check the Accounts and Import—or Accounts—settings in both personal and business Gmail accounts. 2. Classify each alternate address. Determine whether it is another Gmail address, a Google Workspace alias, or a mailbox/domain managed by another provider. 3. Map business dependencies. Review CRM sequences, support platforms, billing tools, calendar invitations, filters, forwarding rules and auto-replies that rely on the affected identity. 4. Move sending to the domain’s native provider or a managed business email platform. Ensure users can send and receive from the actual business address, with appropriate administrator control. 5. Test reply paths and authentication. Confirm that replies reach the intended shared or individual mailbox and that domain email authentication is correctly maintained.
This is also a useful moment to remove departed employees’ alternate addresses and document mailbox ownership. Google notes that an invalid alias can generate bounced mail.
What to watch next
The key remaining detail for affected users is Google’s migration guidance for third-party account support and whether it introduces additional workflow changes before January 2027. But businesses do not need to wait for the deadline to make the core decision.
If a customer-facing domain matters to the company, its sending identity should be managed as business infrastructure—not as a convenience setting inside someone’s personal Gmail account.
