How to deploy email signatures in Microsoft 365

Build one or more signature templates in the builder and save them. You'll assign these to people or departments after connecting.

Go to Dashboard → Microsoft 365 and click Connect Microsoft 365. You'll be sent to Microsoft to grant consent. A Global Administrator must approve two read-only permissions:

• User.Read.All — to read your directory (names, titles, departments, phones)
• Organization.Read.All — to read your organisation name

After approval, Microsoft redirects you back and the connection is stored.

Click Sync directory to import your users. Sigly pulls each person's display name, job title, department, company, and phone numbers so signatures can be personalised automatically.

Choose a default signature for everyone, then fine-tune with per-person overrides or the Bulk assign control to set a signature for a whole department at once. Keep Personalise on so each person's own details are merged in.

On the Microsoft 365 page, copy the add-in manifest URL Sigly gives you. In the Microsoft 365 admin center go to Settings → Integrated apps → Upload custom apps, choose Provide link to manifest file, paste the URL, and assign it to everyone (or a group).

From then on, whenever a user composes a message, their assigned, personalised signature is inserted automatically. Update a signature in the builder and the change flows out on the next email — no redeployment needed.

There's nothing for staff to do — the add-in fills the signature in as the message opens. There's also a Sigly → Insert signature button on the compose ribbon as a manual fallback, useful if someone deletes the signature mid-draft and wants it back. Point staff at the one-page employee guide rather than this article.

Where it works

Automatic insertion relies on Microsoft's event-based activation, which is supported in most but not all Outlook clients:

For anyone on a client in the "No" rows — mobile, or a perpetual-licence Outlook — send them a self-install link instead. They get the same personalised signature and paste it in once; it just isn't updated centrally afterwards.

"Insufficient privileges" when syncing

The tenant hasn't approved Sigly's permissions. Click Check permissions on the connection — it asks Microsoft exactly what was granted and reports back. If it says none were granted, click Re-authorise and sign in as a Global Administrator of that organisation. Consent is per-organisation: approving Sigly in one tenant never carries over to another.

Signatures aren't appearing in Outlook

1. Confirm the add-in was deployed through Integrated apps (not sideloaded) and assigned to that user.
2. Wait — allow several hours after deployment before assuming something is wrong.
3. Check the user has a signature assigned on the Microsoft 365 page (a default counts).
4. Make sure the signature has been saved at least once in the builder, so its content exists.
5. Test in Outlook on the web first — it picks up add-ins fastest — and try a private/incognito window, as browser extensions and ad blockers can interfere.

Still nothing? Make signatures appear in Outlook and OWA covers the tenant settings and client requirements in full — including roaming signatures, which is the usual culprit when people get two signatures rather than none.

The consent screen says "unverified"

That's a standard Microsoft notice for apps whose publisher hasn't completed verification. It doesn't affect how the integration works, and the permissions requested are read-only.