wren.
Log inStart free
Signature guide

Manage Outlook signatures centrally — pick the right lever for your team

Every IT team hits this eventually: 40 people, 40 different-looking signatures, marketing wants to swap the banner by Friday. Outlook has no first-party 'one signature for everyone' button, but there are five real ways to solve it. Here they are, ranked by cost of setup, ordered by team size, with the honest limits of each.

Live example

One of ten built-in Looks. Every element is editable in the builder — colors, photo, links, tagline.

Preview
ToTeam
SubjectAll-hands update
Thanks, Priya

Step-by-step

  1. 1

    Lever 1 — Group Policy signature deployment (free, most fragile)

    A GPO drops an .htm/.rtf/.txt signature file into every domain user's %AppData%\Microsoft\Signatures folder at logon. Free and central; also fragile: users can edit their local copy, new Outlook and OWA ignore the folder entirely, and you're editing HTML by hand. Fine for a static company disclaimer on Windows-only classic Outlook shops.
  2. 2

    Lever 2 — Exchange transport rule (free, wrong position)

    Exchange Admin Center → Mail flow → Rules → Apply disclaimer. Stamps HTML at the bottom of every outbound message, server-side, so it catches mobile-sent mail too. The catch: "bottom" means under the entire quoted reply chain, not directly under the sender. Great for legal disclaimers, useless as a branded signature.
  3. 3

    Lever 3 — Wren (client-installed, centrally designed)

    Owner designs one signature and one banner in Wren's studio. Each teammate opens a personal install link, clicks Copy, pastes once into Outlook (30 seconds). The banner image is hosted on a stable URL — swap the image in the studio and the next email every teammate sends carries the new banner, with no re-install. Owner sees who installed and can resend links in one click. Flat $99/mo up to 50 people. No admin console, no directory sync, no mail routing changes.
  4. 4

    Lever 4 — CodeTwo Signatures 365 (server-side injection)

    Routes outbound Exchange Online mail through CodeTwo's Azure service; injects the signature at send time. Full HTML, correct position under the sender's message, per-department rules from Entra ID, mobile-sent mail covered automatically. Per-mailbox annual pricing (~$1.50–$2.30/mailbox/mo depending on tier), IT setup takes a few days including DNS and pilot rings. The right answer at ~200+ mailboxes with compliance requirements.
  5. 5

    Lever 5 — Exclaimer Cloud (server-side + rich admin)

    Similar server-side model to CodeTwo, with a richer template designer, A/B campaign scheduling, and analytics. Per-mailbox pricing, IT-led rollout. Same fit as CodeTwo — enterprise Microsoft 365 shops that need guaranteed signature enforcement across every mailbox including mobile.

Common questions

›What's the fastest way to get every Outlook user on the same signature this week?
For a team under 100: Wren. Design once, send 40 personal links, each teammate takes 30 seconds. Live for the whole company inside an hour. For 500+ with real IT: start a CodeTwo or Exclaimer pilot; expect a few days including DNS and testing.
›Can Group Policy actually manage new Outlook signatures?
Not really. New Outlook stores signatures in the user's Exchange mailbox (roaming), not the local %AppData% folder. The GPO signature-deployment pattern was built for classic Outlook and is a dead end for new-Outlook users. Microsoft has not shipped a replacement.
›Does Wren need admin rights on user machines?
No. Wren doesn't push anything to any machine. Each teammate opens a link in their browser, clicks Copy, and pastes into Outlook's own signature settings. From IT's perspective this is user-driven — nothing to install, nothing to sign off on.
›How do server-side and client-installed compare when someone edits their own signature locally?
Server-side (CodeTwo/Exclaimer) is definitive — the injection overwrites anything the user had. Client-installed (Wren) shows the owner in the dashboard who installed the current version, but doesn't prevent a user from editing it. In practice we see local drift under 5% because people don't mess with a signature that already looks good.
›Can I use two of these together?
Yes — the most common combo is a transport-rule legal disclaimer at the very bottom (compliance requirement) plus a real branded signature under the sender's message (via Wren or a server-side tool). They don't conflict — they render in different positions in the email.
Also useful