Skip to main content

Exchange On-Premises

Payal Arya
  • Updated
NOTE: The options within this section are not available in the new UI for this release.

Description

The Exchange On-Premises feature allows emails sent from on-premises Exchange mailboxes to have server-side signatures applied. 

Using this feature, an organization can utilize all the benefits of the complete Exclaimer Cloud solution (such as the template designer on a friendly web-based user interface) for all their Exchange-based mailboxes; without migrating from their on-premises Exchange environment into Cloud. 

This feature is suitable for organizations that:

  • Are exclusively using on-premises Exchange as their mail server.
    or
  • Have a hybrid mail environment with both on-premises Exchange and Microsoft 365.
Pre-requisites:
Before starting the setup, make sure you have the following:
  • An Azure Active Directory subscription
    An Azure Active Directory subscription is required for Exclaimer Cloud to connect to and synchronize data from. Azure Active Directory subscriptions are automatically provided with most Microsoft 365 plans; however, you can sign up for free if you do not have an Azure Active Directory subscription. See how you can configure and synchronize Azure AD to use with Exclaimer Cloud - Signatures for Exchange.

  • Azure Active Directory Connect configured and synchronizing
    To ensure all of the user data is automatically synchronized between the on-premise and Azure Active Directories, it is necessary to have Azure Active Directory Connect configured and synchronizing. See how you can set up Azure AD Connect to use the tenant.

  • Credentials for a Global Administrator account within the Azure Active Directory subscription
    During the setup, you will be prompted to sign in with an account to authenticate various Azure apps. The level of permissions required for the account used during setup is given by the Global Administrator admin role.
    If the account is configured to require multi-factor authentication, then this may also be required during the setup process.

  • System requirements for the Exclaimer Cloud Signature for Exchange Transport Agent
    - Windows Server 2012 and above
    - Exchange 2013 CU22 and above, Exchange 2016 CU18 and above, Microsoft Exchange 2019 CU7 and above
    - PowerShell version 4 or above
    - .Net Framework 4.7.2 or above

  • A domain administrator account for the on-premise domain
    To have the required permission level to install the Exclaimer Cloud Signature for Exchange Transport Agent, you will need to be signed in with an account that is a domain administrator.

How to access it?

To access the Exchange On-Premises option during the initial configuration:

  1. From the left-hand pane, click Configuration, then select Connect to Microsoft 365.
    NOTE: The options within Connect to Microsoft 365 are only available during the initial setup. Once you have successfully configured your Exclaimer Cloud - Signatures for Microsoft 365 subscription, this section will not be available. 
    If required, you can edit the configuration settings via Manager User Data, Manage Mail Flow, Outlook Signatures and Exchange On-Premises.
  2. From the right-hand pane, Apply Signatures is enabled only if the authorization and syncing process has been completed.

  3. Click Exchange On-Premises.

  4. Click Continue to old UI.


    As the options within this section are not available in the new UI for this release, you will be redirected to the old UI.

    The Settings window is displayed.

  5. Select the Exchange On-Premises tab, then under Exchange On-Premises are the relevant options:

NOTE: If the Exchange On-Premises option is not available, please get in touch with the Exclaimer Sales team (Sales@exclaimer.com).

To access the Exchange On-Premises option after the initial Exclaimer Cloud setup:

  1. From the left-hand pane, click Configuration, then select Exchange On-Premises.
    As the options within this section are not available in the new UI for this release, you will be redirected to the old UI.

    The Settings window is displayed.

  2. Select the Exchange On-Premises tab, then under Exchange On-Premises are the relevant options:

Configuring Exchange On-Premises

To configure Exchange On-Premises:

  1. In the Settings window, under the Exchange On-Premises heading, click Edit.

    The Exchange On-Premises window is displayed:

The Exchange On-Premises window consists of all settings required to set up the Transport Agent to route mail from your Exchange servers.

This window consists of the following - please click on the required options listed below to go through the detailed description:

Service Uri

This is the address of the imprint server your emails will pass through to receive a signature. This address will be required during the Exclaimer Exchange Transport Agent installation on your on-premises Exchange servers; you can use the copy button to easily copy this address during installation.

NOTE: This is an https (Hypertext Transfer Protocol Secure) path to securely transport emails to the Exclaimer service.

API Keys

This is a list of API keys the Exclaimer Exchange Transport Agent uses to authenticate securely from the on-premises Exchange server to the Exclaimer Cloud environment.

The API keys is the first stage of validation that the Agent needs to pass to route an email to the Exclaimer service. You will need to create at least one API key, as the Exclaimer Exchange Transport Agent requires a valid API key during installation.


To create an API key:

  1. Click New Key.



  2. Enter a descriptive name for your API key.



  3. Click OK.

  4. Click the copy button to copy your API key.
    NOTE: The Key will not be available again once you leave this page.


    Once copied - the API key is ready to be pasted into the installation wizard for the Exclaimer Exchange Transport Agent. 

To delete an API key

  1. Click the bin icon next to the API key you wish to delete.

NOTES:
  • An API is only valid for 12 months after its creation. A warning to renew the API keys is displayed in the Event Viewer logs on the Exchange server where the Exclaimer Exchange Transport Agent is installed close to the time. If your API key expires before you renew it, it will prevent the servers using that API key from utilizing the Exchange On-Premises feature, resulting in no signature application.

  • You can have as many API keys as required, although it is suggested to have only one, and it can be utilized on any number of Exchange Servers.
Exclaimer Exchange Transport Agent

This section consists of the following: