Relevant Products: Exclaimer Cloud - Signatures for Office 365
If your Exclaimer Cloud - Signatures for Office 365 subscription is configured for our Exclaimer Cloud service (so signatures are applied to all email messages via Exclaimer's Cloud service), and you wish to add Outlook Client functionality (so applicable signatures are synchronized to Microsoft Outlook on users' computers), follow the steps below:
- Configure Outlook Client for Exclaimer Cloud - Signatures for Office 365
- Deploy the signature update agent to users' computers
To learn more about our Outlook Client feature, please see our Outlook Client for Exclaimer Cloud - Signatures for Office 365 article.
Configure Outlook Client for Exclaimer Cloud - Signatures for Office 365
- Log into the Exclaimer portal (portal.exclaimer.com) and Launch your subscription. All existing signatures (and signature folders) are displayed on the Home page, in processing sequence.
- Hover your cursor over any signature that you wish to synchronize to Outlook clients (if necessary, create a new signature) and then select the Signature rules option:
The Applies to... window is displayed with focus on Exclaimer Cloud options:
- Select the Outlook Clients tab (at the top of the page) to access Outlook options and click the Configure button:
- A summary page is displayed, detailing tasks that will be completed during this setup:
- Click Next to grant permission for Exclaimer's Outlook Client Agent to sign into Office 365 as a user:
- Click Next. You are directed to a page within the Microsoft Online environment, where you should enter Global Administrator credentials and grant required permissions. Having confirmed these details, you are directed back to Exclaimer's setup wizard, where you'll see confirmation of this:
- Click Next to access the Home page - you're now ready to create your first email signatures in Signatures for Office 365.
Deploy the signature update agent to users' computers
To synchronize signatures to Microsoft Outlook, Exclaimer's Signature Update Agent must be deployed to each user's computer. The agent runs in the background and synchronizes signatures at regular intervals.
There are two ways that you can deploy the Signature Update Agent to client computers:
Unless you have a specific need to deploy via GPO, we recommend that URL deployment is used - this is the simplest method, and ensures that the agent is always up to date.
Note: To learn more about the Signature Update Agent, please see our Signature Update Agent article.