Steps for Deploying the Addin

There are several steps involved, outlined here.

1. Upgrade DSM & DSBS

Install at least versions so that all new features are available.

2. Review Templates

Avoid Heading Styles – Inline Styling Only – Do not place CSS in the <style> block of the HTML header; instead apply styles inline (e.g., <span style="…">). Mobile clients ignore header‑based CSS and will display poorly if it is used.

Explicit Table Widths – Set a fixed width for every table and cell. Outlook on desktop can infer sizes, but mobile devices cannot.
Explicit Colors & Fonts: – Specify colors and font families directly rather than inheriting from surrounding text or defaults.

Why It Matters – Desktop Outlook handles HTML more flexibly, so issues may not surface there. Mobile devices have stricter rendering engines; missing inline styles or widths often lead to garbled layout or unreadable content. Make sure all tables and cells have a defined width and that all styling is applied inline before deploying the templates.

3. Licensing and configuration of jobs to publish to the cloud API.

After adding the license you only need to enable the API end-point. Jobs are defined like any other jobs.
 

Note: To prioritize bandwidth for end-users we have build-in throttling of jobs running during day times. We incourage you to setup your jobs to run during the night. (EU Time). Your jobs are throttled between 07.30-17.30.

4. Admin note in the add‑in task pane, and User allowances
 

Enable “Allow Users Override?” Contact DynamicSignature support (usually during licensing) to activate this setting— it is not publicly exposed.

First‑Line Contact Notice. A default notice appears for users who want to request changes. Only our staff can edit or remove this message; let us know if you need a change.

Add‑in Deployment. Deploy the add‑in client to a test group by adding the tenant’s manifest URL in Outlook.

Optional Cleanup. Run a GPO script to delete all local signatures—or only those with specific names—from Outlook storage, ensuring that only add‑in–managed signatures remain.

Feel free to contact us for any of these steps.

Deployment of the Add-in manifest

After you run a publishing job in DSBS and confirm it succeeded, you can deploy the Add-in client to your tenant.

The screenshots below illustrate the process. 

If you don’t see the Settings → Integrated Apps option immediately, click “See more” first.

You can use a link to the manifest instead of the actual manifest.

This URL for the manifest should be provided by us in the email that you received along with the license for the product. 

Assign users to the add-in experience. Start conservatively

Note: As stated here, it can take up to 72 hours before the add-in will show up. Normally we experience this to be only 15 min to 1 hour.

After full deployment, you may consider removing all signatures previously deployed to Outlook using the classic DS-Client, using a script via GPO. We have provided a script for that here.

Post-deployment you can modify the add-in usage by going to the settings tab.