Company-Wide Email Signatures in Microsoft 365 and Google Workspace: What Each Can and Can't Do

Quick answer: Microsoft 365 and Google Workspace can each add a company-wide footer or disclaimer to outgoing email, and Microsoft can fill in details from each sender's directory record. Neither lets every person see a personalized, per-office signature while they write, and Microsoft's own documentation lists what its mail flow rules cannot do. A signature platform covers those gaps.

Google Workspace: the Append footer setting

In the Admin console, Gmail has a setting that appends a footer to outgoing messages. Google's help page describes it this way: the footer applies to everyone in an organizational unit, and child units inherit it from their parent. You can enter up to 10,000 characters. The editor offers text formatting but not HTML, and images must be inserted by web address from a public server, because images stored in Google Drive can't be used. Changes can take up to 24 hours, though they usually happen sooner.

• It covers every message sent from the unit, including mail sent from aliases and from third-party apps such as Outlook and Apple Mail.
• It isn't supported for messages encrypted with Google Workspace client-side encryption.
• Plain-text messages get a plain-text footer, with no images or formatting.
• The page doesn't describe filling in each person's own name, title or phone, so it is a footer for a unit, not a signature for a person.

Microsoft 365: Exchange mail flow rules

Exchange mail flow rules (transport rules) can add a disclaimer or signature to the top or bottom of messages that leave the organization. You can scope a rule by group, by recipient or by other conditions, and the disclaimer text can use tokens that pull values from the sender's directory record, such as display name, title, company, department, office, phone and address. Microsoft's documentation for Exchange Server 2016 and 2019 says plain text is limited to 5,000 characters including any HTML tags and inline CSS, and that images are added with an image tag pointing to a file on the internet. Outlook blocks external images by default, so users have to allow them.

The same page lists what these signatures cannot do: insert the signature directly under the latest email reply or forward, display server-side signatures in users' Sent Items folders, and skip a line when the value for a variable, such as a phone number, isn't filled in for that user. Microsoft's own advice for those cases is to use a third-party tool. That documentation covers Exchange Server; Microsoft 365 uses the same kind of rule, so check the current limits for your plan.

Where the built-in tools stop

• No per-office design: one footer per unit or rule, not one shared design with each office's own address filled in.
• The sender doesn't see it while writing (server-side), so a mistake or a missing field goes out unseen.
• Limited layout: a text editor without HTML in Google, character limits and external images in Microsoft.
• No control over what individuals can edit, no check against required wording, and no record of which version each person had on a given date.

What a signature platform adds

A signature platform builds each person's signature from one organization template plus their own details, with offices and teams in between, and puts it in their mailbox. Email Signature Magic writes the signature into each person's Gmail signature setting and, for Microsoft 365, inserts it in Outlook through an add-in your Microsoft 365 admin installs once. Because the signature is part of the message while it is written, the sender sees what goes out. The trade-off is coverage: server-side tools reach every app, while a compose-time tool only reaches the apps it runs in.