Implementation of Client-Hosted Email Signature Server for Microsoft 365

This article provides step-by-step instructions to implement the Client-Hosted Email Signature Server solution.

Implementation Steps

1. Configure Certificates: A self-signed certificate set is generated to encrypt the communication channels between the Templafy Email Signature Server and the Microsoft 365 Exchange Online subscription.
2. Configure access to mailboxes for Sent Items update: Emails that have been processed by the Email Signature Server, and a signature was appended, also get the signature appended to the e-mail in the Sent Items folder by the Email Signature Server using Graph API.
3. Build the Email Signature Server in Kubernetes: Our Email Signature Server is delivered as a Docker container image which needs to be deployed to the customer's subscription using Azure Kubernetes Services.
4. Configure Microsoft 365 Exchange to use Email Signature Server: Set up connectors and a mail flow rule in the Exchange Online Admin center that will route emails to the Email Signature Server cluster.
5. Configure Templafy for Email Signature Server: In the Templafy Admin center, configure email signatures, set the ESS SAS Link, and have users follow the onboarding flow to set up their User Profiles.