|
|
|
|
|
Signatures are stamped after an email is sent. They are not visible while composing an email. Signatures can be seen in the sent items folder. |
Signatures are automatically inserted into the email body as users compose an email in Outlook. |
For users configured to use server-side stamping, signatures are stamped after an email is sent while for those configured to use client-side stamping, signatures are inserted in the email body. |
|
Users have less control over their email signatures. |
Provides users with more control over their email signatures as they can preview signatures before sending. |
Server-side users have less control while client-side users have more control. |
|
Works with all email clients & devices on all OS platforms (including Android and iOS). |
Works only with Outlook running on Windows, Mac, iOS, Android, and OWA. |
Works with all email clients & devices on all OS platforms. |
|
Requires two Microsoft 365 connectors and one mail flow rule in the M365 tenant to route and process email stamping. |
Utilizes the Outlook add-in to push signatures to the desired mailboxes. |
Combines both the Microsoft 365 connectors and the Outlook add-in. |
|
Utilizes an SMTP service to communicate with Microsoft 365. |
Works independent of SMTP. |
Utilizes both an SMTP service and an Outlook add-in. |
|
Detailed reporting for each user such as the number of emails sent. |
No detailed reporting. |
Detailed reporting for each user such as the number of emails sent. |
|
Admins can test signature rules and preview signatures in the central web console. |
Admins can test signature rules and preview signatures in the central web console. |
Admins can test signature rules and preview signatures in the central web console. |
|
Admins can display and manage banners with email signatures. |
No banner management. |
Admins can display and manage banners. |
|
Can convert plain text email to HTML. |
Cannot convert plain text email to HTML. |
Can convert plain text email to HTML. |