Migrate Templafy Email Signature Server to use Graph API

About this article 

Microsoft has recently announced the support of Graph API within their Exchange Online servers. This will allow for a more granular access to Exchange Online mailboxes with no longer requiring the full_access_as_app to all permissions. 

Microsoft also included in this announcement that they are planning to deprecate the current method relying on EWS (Exchange Web Sockets) by Sept 30th, 2022.  

Templafy has updated the Email Signature Server to support Graph API method on the App registration.

Below the steps needed to be followed: 

1. Configure the Graph API endpoints 
2. Update Templafy Email signature server 
3. Remove the EWS settings 

Prerequisites

Configure the Graph API endpoints 

• Go to https://portal.azure.com

• Ensure the intended subscription is selected

• Go to Azure

• Go to App registrations

• Go to the previously created application which most likely has the following name [templafyemailsignatureserver] 
• Click [View API permissions]
• Click [+ Add a permission]
• Select [Microsoft Graph] at the top under  Commonly used Microsoft APIs 
  1. Click [Application permissions] 
  2. Select 🗹 Mail.ReadWrite
  3. Click [Add permissions] 
     
     

• Click [+ Add a permission] to add another permission

• Click [Microsoft Graph] under Commonly used Microsoft APIs 
  1. Click [Application permissions] 
  2. Select 🗹 Domain.Read.All
  3. Click [Add permissions] 

• Click Grant admin consent for <YOURTENANT> (this needs to be clicked each time permissions are modified) 
  
  

Update Templafy Email signature server 

• Go to https://portal.azure.com

• Ensure the intended subscription is selected

• Go to Azure

• Go to App registrations

• Go to the previously created application which most likely has the following name [templafyemailsignatureserver] 
• Copy the value of [Directory (tenant) ID]

Client Hosted Update the Kubernetes deployment and the Docker image  

Add the Directory ID property to the deployment image 

1. Navigate to the Resource group containing the [templafyemailsignatureserver] Kubernetes service
2. Select the [Workloads] item under the [Kubernetes resources] section of the left hand panel
3. Click the [email-signature-server-deployment] in the main panel
   
   

   
   
   

4. Select the YAML item in the left hand pane of the email-signature-server-deployment Overview

5. Select the JSON tab of the main panel   
   
   
   
   

6. Add the following as an environment variable in the env section, you can place this after the office365AuthenticationUrl block:
   

   {
      "name": "office365DirectoryId",
      "value": "<Your TenantID>"
   },

7. Replace the "<Your GUID>" with the the GUID you have retrieved from the App registration as described above

8. Click the [Review + Save] button
   
   

   

9. Check the ☑[Confirm manifest changes] checkbox

10. Click the [Save] button

Upgrade the email signature server version to support this functionality  

Remove the EWS settings

• Go to https://portal.azure.com

• Ensure the intended subscription is selected

• Go to Azure Active Directory

• Go to App registrations

• Go to the previously created application which should have the following name [templafyemailsignatureserver] 
• Click [View API permissions]
  1. Right Click on [...] next to [Office 365 Exchange Online] 
  2. Select [Revoke all admin consents]
     
  3. Then again Right-click on [...] and select [Remove all permissions]

Related articles