Create my signature
Microsoft 365 add-in

Outlook and Microsoft 365 signatures: central deployment, no transport rule.

The Signally add-in installs from your Microsoft 365 admin center and applies the right signature to every employee, in Outlook Web, Windows, Mac and mobile. Your email always leaves from your own tenant.

What actually happens, on the admin side and on the employee side

ADMIN SIDE — 15 MINUTES
  1. 01
    Connect the tenant

    You authorise Signally from Entra ID with admin consent, read-only on the directory.

  2. 02
    Deploy the add-in

    Under "Integrated apps", you deploy the add-in to the whole organisation or to a pilot group.

  3. 03
    Assign the templates

    You map each Microsoft 365 group to the signature template that fits it.

  4. 04
    Continuous updates

    A new joiner appears in the directory: they get their signature with nothing for you to do.

EMPLOYEE SIDE — 0 MINUTES
  1. 01
    They open Outlook

    Nothing to install, nothing to copy and paste, no tutorial to follow.

  2. 02
    They write a message

    The signature is inserted into the body of the message, with their details and the current banner.

  3. 03
    They send it

    The message leaves from their Microsoft 365 account. Signally plays no part in sending.

  4. 04
    They see what the recipient sees

    The signature is visible in sent items — unlike server-side transport rules.

Why an add-in rather than an Exchange transport rule?

A transport rule adds the signature after sending, server-side: the employee never sees it, threaded replies stack up badly and encryption can get in the way. The add-in inserts the signature as the message is written, in the message the user has in front of them, with no traffic rerouting and no SMTP connector to maintain.

Environments covered

Outlook Web
Browser, all operating systems
Outlook Windows
Classic and new Outlook
Outlook Mac
Current version
Outlook mobile
iOS and Android
Exchange Online
Microsoft 365 tenants

Frequently asked questions — Microsoft 365 and Outlook

How do I deploy an email signature to all Microsoft 365 users?
You connect your tenant to Signally with admin consent, deploy the add-in from the "Integrated apps" section of the Microsoft 365 admin center, then assign a template to each group. The full deployment takes about fifteen minutes.
Does the add-in work on the new Outlook?
Yes. The add-in works on Outlook Web, the new Outlook for Windows, classic Outlook for Windows, Outlook for Mac and Outlook mobile on iOS and Android.
Do I need to create an Exchange transport rule?
No, and that is an advantage: no traffic rerouting, no connector, no change to your outbound routing. The signature is inserted into the message as it is written.
Does the add-in have access to the content of my emails?
No. It inserts a signature block into the body of the message being written. It does not read, analyse or keep the content of your messages, and no email passes through our servers.
What happens for a new joiner?
As soon as their account appears in the directory and belongs to a group mapped to a template, they get their signature. Nothing is asked of them or of the IT team.
Can we test on a pilot group before going wider?
Yes. The add-in deployment can be limited to a Microsoft 365 group of your choice, then extended to the whole organisation once you are satisfied.

Go further

Deploy your Outlook signatures with Signally

Fifteen minutes from your Microsoft 365 admin center, without touching your routing.

Create my signature Request a demo