CodeTwo Signatures Web Add-in for Outlook - centralized deployment

The modern CodeTwo Signatures Web Add-in for Outlook, co-engineered with Microsoft, integrates seamlessly with user accounts in Outlook for Windows and Outlook on the web (OWA) and adds company-wide signatures as users type an email. The add-in can be easily deployed centrally to all or selected users through the Microsoft 365 admin center (you can get it directly from AppSource). It is deployed per Microsoft 365 (Office 365) user (not per device), so it works in Outlook and OWA on any device the user signs into. No need to install any additional COM/EXE objects. Read on to learn how to deploy the add-in for all or selected users in your Microsoft 365 organization. 

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

Read this before the deployment

  • The Web Add-in only works with supported versions of Outlook. If necessary, update Outlook desktop apps or change the Microsoft Apps update channel for those users who will be using the add-in. 
  • The Web Add-in needs to be deployed by a global admin.
  • 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.
  • For the Web Add-in to work, the CodeTwo software needs to operate in client-side or combo mode (learn more about signature modes). You also need to prepare an email signature template and assign users who should get it. To do so, create and set up a client-side signature rule(s) by following this guide.

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

Centralized deployment of the new signature add-in via the Microsoft 365 admin center

  1. Sign in to the Microsoft 365 admin center. For simpler deployment, you can go the add-in listing on Microsoft AppSource and click Get add in (it may be necessary to sign in using your Microsoft account first). Once you're automatically transferred to the Microsoft 365 admin center, continue with step 6 below.
  2. Go to Settings > Integrated apps and click Get apps (Fig. 1.). This will open Microsoft AppSource. 

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

  1. Search for 
    codetwo
    and select CodeTwo Email Signatures for Office 365 (Fig. 2.).

CodeTwo Email Signatures for Office 365 in Microsoft AppSource.
Fig. 2. CodeTwo Email Signatures for Office 365 in Microsoft AppSource.

  1. Scroll down to the Other apps from CodeTwo section.
  2. Under CodeTwo for Outlook, click Get it now (Fig. 3.). Accept the permissions request and then click Continue.

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

  1. In the add-in deployment 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. 4.

Selecting the add-in users.
Fig. 4. 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 on the web and Outlook for Windows. However, in rare cases, it might take longer.

You will now see the add-in (CodeTwo for Outlook or CodeTwo Signatures) on the Integrated apps page (Fig. 5.). If you click it, the details pane opens on the right. From here, you can use the provided links to:

  • Manage the Web Add-in's users (by clicking Edit users),
  • Update the Web Add-in (by clicking Update add-in),
  • Remove the Web Add-in from your Microsoft 365 tenant (by clicking Remove app; learn more).

You can manage the add-in by using the CodeTwo for Outlook details pane.
Fig. 5. You can manage the add-in by using the CodeTwo for Outlook details pane.

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?

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.

  1. 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.

  1. 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 for Windows) or a compatible browser (for OWA access) on their (client) computer, as well as be logged in to their Microsoft 365 account in them.

  1. 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).

  1. 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?

No. The add-in will continue to work in your organization and add signatures to emails in Outlook and OWA.

  1. How to remove the add-in?

See this article.

  1. 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.

Was this information useful?