CodeTwo Signatures Web Add-in for Outlook - centralized deployment

The modern CodeTwo Signatures Web Add-in for Outlook, co-engineered with Microsoft, adds signatures as users type an email in Outlook for Windows, Outlook for Mac (early access version of the Web Add-in) and Outlook on the web (OWA). The Web Add-in also allows users to preview the signature that will be added server-side (in the cloud) after an email is sent.

The add-in can be easily deployed centrally to all or selected users in your organization through the Microsoft 365 admin center. The deployment is per Microsoft 365 user not per device, so the add-in works in Outlook and OWA on any device the user signs into. No need to install any additional COM/EXE objects.

Read this before the deployment

  • The Web Add-in only works with supported versions of Outlook. If necessary, update Outlook desktop apps.
  • If your organization uses an endpoint security tool (such as a firewall), be sure to whitelist these add-in endpoint addresses for the Web Add-in to work.
  • The Web Add-in needs to be deployed by your organization's Microsoft 365 Exchange admin or global admin account.
  • If you have already deployed the classic COM Add-in to your Outlook users, you need to uninstall it first before deploying the modern Web Add-in, as you can only use either of them. Otherwise, the add-ins can conflict with each other.
  • You need to create an email signature and assign users who should get it. To do so, create and configure a signature rule by following this guide.
  • The Web Add-in may not provide full support for shared mailboxes. This is because this type of mailboxes is not yet officially supported by Microsoft on their Office Add-in platform. 

For more information about the Web Add-in, see the FAQ section below.

For instructions on how to use the modern Signatures Web Add-in, see this article.

Add-in capabilities

The table below shows how the add-in works depending on the signature mode in which CodeTwo Email Signatures for Office 365 operates:

Signature modes: SERVER-SIDE (CLOUD) CLIENT-SIDE (OUTLOOK) COMBO
Add-in capabilities: Preview signatures added in the cloud after an email is sent Add automatic signatures in Outlook & OWA as user types
  • Add automatic signatures in Outlook & OWA as user types (default behavior)
  • Preview signatures added in the cloud after an email is sent (available only if users are allowed to switch between cloud and Outlook signatures in the add-in by using the Outlook/Cloud toggle, and the toggle is set to Cloud – learn more)

When you change the signature mode from server-side to client-side/combo (or from client-side/combo to server-side), it can take up to 4 hours before the add-in starts to work as intended for the currently selected signature mode. Learn more about signature modes

Using the Web Add-in in combo mode

When CodeTwo Email Signatures for Office 365 operates in combo signature mode, the Web Add-in works the same way as in the client-side mode – it adds client-side signatures in Outlook & OWA. However, the Web Add-in can also be used to preview server-side signatures.

To enable this feature, first sign in to CodeTwo Admin Panel, click the Esig - Admin Panel - Manage tenant button button next to the name of your tenant, and then go to Outlook add-in > Modern Web Add-in and click Show advanced options, as shown in Fig. 7. Select the checkbox next to the Allow users to switch between server-side (cloud) and client-side (Outlook) signatures in Outlook option and click Apply.
 
Once enabled, the Outlook/Cloud toggle will appear in the Web Add-in's pane (it may take up to 4 hours for the toggle to appear). The preview feature will work if the toggle is set to Cloud. Learn more about this feature

Deployment instructions

The simplest deployment is via Microsoft AppSource, which then automatically redirects you to a deployment wizard in your Microsoft 365 admin center.

Important

If your company uses an endpoint manager or a firewall, be sure to whitelist CodeTwo Signatures Web Add-in for Outlook endpoints. Otherwise, the Web Add-in will not work. If you've already whitelisted the necessary endpoints or intend to do this later, proceed with the deployment.

  1. Open the Web Add-in listing on Microsoft AppSource.
  2. Click the Get it now button, as shown in Fig. 1.

Getting the CodeTwo Signatures Web Add-in for Outlook from Microsoft AppSource.
Fig. 1. Getting the CodeTwo Signatures Web Add-in for Outlook from Microsoft AppSource.

  1. Sign in to AppSource with your organization's Microsoft 365 Exchange admin or global admin account (if necessary, provide some basic profile information and grant the required permission) and click Continue. You'll be redirected to the Microsoft 365 admin center where the add-in deployment wizard will open automatically.
  2. In the wizard, specify which users can access the add-in. Select:
    • Just me to deploy the add-in only for the admin account used to deploy the add-in,
    • Entire organization to deploy the add-in for all users in your Microsoft 365 organization,
    • Specific users/groups to deploy the add-in only for the selected users or groups of users. Use the search box to find and add individual users or groups, as shown in Fig. 2.

      Supported groups

      While the centralized deployment works for most of the group types available in Microsoft 365, it does not support nested groups or groups that have parent groups (non-top-level groups).

Selecting the add-in users.
Fig. 2. Selecting the add-in users.

  1. Click Next twice and then click Finish deployment.
  2. Once the deployment is completed, click Done to close the pane.

It usually takes up to 6 hours for the add-in to appear and work correctly in Outlook. However, in rare cases, it might take longer (up to 24 hours).

You will now see the Web Add-in (CodeTwo for Outlook) on the Integrated apps page (Fig. 3.). If you click it, the details pane opens on the right. From here, you can use the provided links to manage the add-in's users, update the add-in, as well as remove the add-in from your Microsoft 365 tenant.

The Web Add-in listed on the Integrated apps page.
Fig. 3. The Web Add-in listed on the Integrated apps page.

If you don't see CodeTwo for Outlook on the Integrated apps page but CodeTwo Signatures instead, refer to this FAQ for more information.

Optional: deployment directly from the Microsoft 365 admin center

You can also deploy the Web Add-in directly from the Microsoft 365 admin center, but this scenario is sometimes confusing due to the way apps & add-ins are displayed when you browse through Microsoft AppSource. Pay special attention not to confuse the add-in listing with our cloud service listing.

Important

If your company uses an endpoint manager or a firewall, be sure to whitelist CodeTwo Signatures Web Add-in for Outlook endpoints. Otherwise, the Web Add-in will not work. If you've already whitelisted the necessary endpoints or intend to do this later, proceed with the deployment.

  1. Sign in to the Microsoft 365 admin center using your Exchange admin or global admin account.
  2. Go to Settings > Integrated apps and click Get apps (Fig. 4.). This will open Microsoft AppSource. 

Opening Microsoft AppSource in the Microsoft 365 admin center.
Fig. 4. Opening Microsoft AppSource in the Microsoft 365 admin center.

  1. Search for 
    codetwo
    and click the CodeTwo for Outlook card (Fig. 5.).

    CodeTwo Signatures Web Add-in for Outlook in Microsoft AppSource.
    Fig. 5. CodeTwo Signatures Web Add-in for Outlook in Microsoft AppSource.

    Important

    Do not click the CodeTwo Email Signatures for Office 365 card. It is used to deploy the entire CodeTwo signature service instead, not the Web Add-in.

  2. Click the Get It Now button on the left, as highlighted in Fig. 6.

Getting the Web Add-in from Microsoft AppSource.
Fig. 6. Getting the Web Add-in from Microsoft AppSource.

  1. Next, continue the deployment from step 4, as outlined in the previous section. Keep in mind that you may be prompted to fill out some basic profile information.

Advanced add-in options

Warning

The settings listed below change how the add-in interacts with various Outlook settings. Make sure you understand how they work before enabling them.

Changes to these settings may take up to 4 hours to propagate.

To access additional Web Add-in settings, sign in to CodeTwo Admin Panel, go to the Dashboard or the Tenants tab and click the Manage tenant (Esig - Admin Panel - Manage tenant button) button next to the name of your tenant. Next, under the Manage tenant options, go to Outlook add-inModern Web Add-in and click Show/Hide advanced options (Fig. 7.).

Accessing advanced add-in options in CodeTwo Admin Panel.
Fig. 7. Accessing advanced add-in options in CodeTwo Admin Panel.

The following settings are available:

Always disable end users’ default signatures in Outlook

If you select this option, end users’ default signatures set up in Outlook and OWA will be disabled (Fig. 8.). This means these signatures will not be automatically added to emails composed in Outlook.

Default Outlook signatures disabled by the Web Add-in.
Fig. 8. Default Outlook signatures disabled by the Web Add-in.

Important

This setting also works in server-side mode, when the Web Add-in is used to preview server-side signatures. However, it works only with OWA and supported versions of Outlook.

If you leave this option unselected, default Outlook signatures will be disabled only for end users who have their client-side signatures added automatically by the Web Add-in. See Outlook signature adding options for client-side signature rules

Hide add-in notifications displayed above emails in compose mode (not available in server-side mode)

Select this option to hide Web Add-in's notifications shown above emails in compose mode in Outlook (Fig. 9.). These notifications will still appear if something goes wrong, and client-side (Outlook) signatures are not added correctly.

Web Add-in's notifications can be disabled in CodeTwo Admin Panel.
Fig. 9. Web Add-in's notifications can be disabled in CodeTwo Admin Panel.

Differentiate client-side (Outlook) signatures based on the From field (not available in server-side mode)

With this option selected, when user X sends an email as (or on behalf of) user Y, the Web Add-in will add the signature of user Y, as shown in Fig. 10., item A.

If user Lee is assigned permissions to another mailbox, the Web Add-in can either add a signature set up for that mailbox (item A) or for the user (item B).
Fig. 10. If user Lee is assigned permissions to another mailbox, the Web Add-in can either add a signature set up for that mailbox (item A) or for the user (item B).

With this option unselected, user X always gets their own signature in Outlook, as shown in Fig. 10., item B.

Important

In server-side mode, the Web Add-in always shows a signature set for the user/email address selected in the email's From field.

Allow users to switch between server-side (cloud) and client-side (Outlook) signatures in Outlook (available in combo mode only)

Select this option to enable a toggle button in the Web Add-in's pane (Fig. 11.) that will allow your end users to choose how they want their signatures to be added. They can switch between:

  • Outlook (client-side) signatures – added directly in Outlook & OWA as you compose an email. End users can also use the Web Add-in's pane to manually select a different email signature. Learn more
  • Cloud (server-side) signatures – added in the cloud after an email is sent. The Web Add-in's pane will show a preview of end user's signature(s). Learn more

The toggle button allows users to switch between server-side (cloud) and client-side (Outlook) signatures.
Fig. 11. The toggle button allows users to switch between server-side (cloud) and client-side (Outlook) signatures.

With this option unselected, the Web Add-in will always add client-side signatures in Outlook & OWA.

Add-in FAQ

  1. Can users still get server-side signatures for emails sent from Outlook clients on which the Web Add-in has been deployed?
  2. Can users install the Web Add-in by themselves?
  3. Can I use the Web Add-in on virtualized environments such as Windows Virtual Desktop (WVD) and Microsoft Azure or Terminal Server (RDS)?
  4. Signatures are not being added automatically to emails. Why?
  5. Web Add-in is missing or not working in Outlook. How to fix it?
  6. How to add/remove Web Add-in users?
  7. "CodeTwo Signatures" is shown on the Integrated apps page in Microsoft 365. What is this add-in?
  8. I’ve already deployed the Web Add-in by using the manifest file. Do I need to deploy it again for my Microsoft 365 tenant from Microsoft AppSource?
  9. How to remove the add-in?

1. Can users still get server-side signatures for emails sent from Outlook clients on which the Web Add-in has been deployed?

Yes and no. If you use CodeTwo Email Signatures for Office 365 in combo mode, a server-side signature will be added to an email sent from Outlook desktop and OWA only if:

  • there are no client-side signatures set as default ones for new messages or replies/forwards (learn more); and 
  • a user doesn't add a client-side signature manually (using the CodeTwo Signatures pane) while composing an email. 

If the Web Add-in adds a client-side signature automatically, but you delete this signature manually from your message before sending it, a server-side signature will not be added. The same will happen if you add a signature manually but then remove it from an email.

2. Can users install the Web Add-in by themselves?

Yes and no. Since the Web Add-in is available on Microsoft AppSource, every Microsoft 365 user can install it in their Outlook directly from the AppSource page or by using the Get Add-ins option in Outlook desktop or OWA.

The Web Add-in will work, and users will have access to their signatures (provided that CodeTwo Email Signatures for Office 365 is deployed in your Microsoft 365 tenant, and these users are included in at least one client-side rule). However, the automatic insertion of email signatures (the event-based activation feature) will not work – users will need to add signatures manually, as described here.

To make the most of the Web Add-in and its features, it needs to be deployed centrally, by following these steps. Once you deploy the Web Add-in directly from the Microsoft 365 admin center, it will automatically overwrite the same Web Add-in that has been individually installed by your users.

3. Can I use the Web Add-in on virtualized environments such as Windows Virtual Desktop (WVD) and Microsoft Azure or Terminal Server (RDS)?

Yes, the modern CodeTwo Signatures Web Add-in for Outlook can be used in both standard (physical) and virtual environments. To add client-side signatures regardless of the used environment, your user should have access to the Office 365 desktop apps (Outlook) or a compatible browser (for OWA access) on their (client) computer, as well as be signed in to their Microsoft 365 account in them.

4. Signatures are not being added automatically to emails. Why?

You either use an unsupported version of Outlook (learn more about the Web Add-in requirements) or you have installed the add-in manually from the AppSource or Outlook (see also this question above).

5. Web Add-in is missing or not working in Outlook. How to fix it?

If you are experiencing this issue, make sure to allow traffic on your firewall / endpoint management software for these add-in endpoint addresses.

6. How to add/remove Web Add-in users?

There are two methods that you can use to add or remove Web Add-in users:

  1. (Recommended) If you deploy the Web Add-in to a specific group of users, all members of this group will get the Web Add-in. If you want to allow or deny access to the Web Add-in to specific users, simply add or remove group members, respectively. You can use most of the groups available in Microsoft 365, including Microsoft 365 groups, distribution lists and security groups. Nested groups or groups that have parent groups are not supported.
  2. Go to the Integrated apps page in the Microsoft 365 admin center, select CodeTwo for Outlook (or CodeTwo Signatures) and then click Edit users, as shown in Fig. 12. Next, continue as described in this step of the Web Add-in deployment guide.

Esig - Web Add-in deployment - Edit users
Fig. 12. Editing the Web Add-in users directly from the Integrated apps page.

In either case, it can take up to 24 hours for the Web Add-in to show up in or be removed from users' Outlook apps.

7. "CodeTwo Signatures" is shown on the Integrated apps page in Microsoft 365. What is this add-in?

CodeTwo Signatures is the old name of the CodeTwo Signatures Web Add-in for Outlook. If you see this name instead of CodeTwo for Outlook, it means you deployed the Web Add-in by providing a link to its manifest file (instead of deploying the Web Add-in by following these steps).

See also point 7. below for more info.

8. I’ve already deployed the Web Add-in by using the manifest file. Do I need to deploy it again for my Microsoft 365 tenant from Microsoft AppSource?

In case the manifest file changes in the future, the Web Add-in will continue to work and add signatures to emails in your organization. However, it will no longer get automatic updates. Because of that, it is recommended to remove the Web Add-in from your Microsoft 365 tenant and deploy it again from Microsoft AppSource.

9. How to remove the add-in?

See this article.

10. How to...

For more information about the CodeTwo Signatures Web Add-in for Outlook, see the Signature modes FAQ.

See also

CodeTwo Signatures Web Add-in for Outlook - find out more about the modern Web Add-in and how to use it.

In this article

Was this information useful?