#microsoft-365

← All tags

Microsoft 365 is the platform used by most UK businesses for email, and the environment where email signature management is most commonly addressed. While M365 includes basic transport rules for appending email footers, it lacks a built-in mechanism for visually consistent, centrally managed signatures — particularly at compose time and on mobile. Third-party tools, deployed via Microsoft Centralised Deployment, fill this gap.

Further reading

Frequently asked questions

Does Microsoft 365 have a built-in way to manage email signatures for all employees?

Microsoft 365 includes mail flow rules (transport rules) that can append a text or HTML block to outbound email at the server level. However, these rules have significant limitations: they run after the email is sent so the sender never sees the signature during composition, image support is unreliable, and they cannot display different signatures based on individual user attributes. Most organisations that need consistent visual signatures use a third-party add-in tool instead.

What is Microsoft Centralised Deployment, and how does it relate to email signatures?

Centralised Deployment is Microsoft's mechanism for deploying Office Add-ins from the Microsoft 365 admin centre to specific users or groups, without requiring individual installation. Email signature tools built as Outlook add-ins are typically deployed this way. It supports Outlook on Windows, Mac, the web, and the Outlook mobile app, and propagates to users within 24 hours of assignment.

How does the new Outlook for Windows affect email signature management?

The new Outlook for Windows uses a web-based add-in model (Office.js) rather than the COM add-in model used by classic Outlook. COM add-ins are incompatible with the new Outlook. If your email signature tool relies on a COM add-in, it will stop working for users who switch. Add-in tools built on the Office.js API are compatible with both classic and new Outlook and are deployed via Centralised Deployment.