Supported platforms and requirements

CodeTwo Email Signatures for Office 365 consists of several components that are responsible for handling server-side and/or client-side signatures. The core portions of the software that seamlessly process emails and apply signature rules, e.g. the CodeTwo Email Azure Service, run on Microsoft Azure servers and are operated by CodeTwo. 

The administrator of an Office 365 tenant configures the software via the CodeTwo Admin Panel: a web-based panel for registering new tenants to the service, managing payments and accessing other tenant-related options. To manage the signatures, the admin (or the users delegated by the admin in the Admin Panel) needs to launch a dedicated Windows app – the Manage Signatures App.

Outlook users need to install the CodeTwo Signatures Add-in for Outlook on their machines to have access to client-side signatures. An optional component, the CodeTwo Email Signatures for Office 365 Add-in, allows end users to preview server-side signatures while composing emails in Outlook and OWA.

The last component, CodeTwo Email Signatures for Office 365 Custom Attributes Sync App, is required only if you want to use custom AD attributes in email signatures.

Study the tables below for details on the program's requirements.

Software components
Tenant administration: CodeTwo Admin Panel, accessed via a web browser.
Signature management: Manage Signatures App is a ClickOnce application launched via the Start menu in Windows.
Client-signatures add-in for Outlook: CodeTwo Signatures Add-in for Outlook is a ClickOnce application launched via the Start menu in Windows.  
Signature preview in Outlook/OWA: CodeTwo Email Signatures for Office 365 Add-in is an Outlook Web Add-in deployed globally by admins in EAC or individually by Office 365 users.
Manual sync of custom attributes: Custom Attributes Sync App is a ClickOnce application launched via the Start menu in Windows.
CodeTwo Admin Panel
Required permissions: Office 365 global admin rights.
Requirements:
  • Office 365 plans with Exchange Online (access to Exchange Online transport rules is required; F1 and Kiosk plans are also supported). 

Info

The above Office 365 plans store data in the Azure AD cloud, and access to Azure AD is required by the CodeTwo software. A separate Microsoft Azure subscription is not required for any of these plans.

Trial Office 365 subcriptions are supported as well.

  • A modern web browser:
    • Microsoft Internet Explorer and Microsoft Edge,
    • Google Chrome,
    • Mozilla Firefox,
    • Safari.
Manage Signatures App
Required permissions: Only authorized users can log in to the application and configure email signature rules. Learn more
Requirements:
  • 64-bit Windows, at least Windows 7 SP1 or Windows Server 2008 R2 SP1,
  • .NET Framework 4.7.1,
  • Internet Explorer 9 or later.
CodeTwo Signatures Add-in for Outlook 
Required permissions: To install the add-in, no administrative credentials are required. However, if the required version of .NET Framework is missing, a user must have administrator privileges to install it.
Requirements: Outlook:
  • 32 or 64-bit versions of Outlook 2013 or later,
  • at least Windows 7 SP1 or Windows Server 2008 R2 SP1,
  • .NET Framework 4.7.1.
CodeTwo Email Signatures for Office 365 Add-in (server-side signature preview)
Required permissions: Exchange administrator rights (required for central deployment only).
Requirements: Outlook:
  • 32 or 64-bit versions of Outlook 2013 or later(*),
  • Windows 7 or later,
  • Internet Explorer 11 or later.

(*) To use this add-in in Outlook 2013 and 2016, you need to update your Office to the latest version. Learn how to install Office updates

Outlook for Mac:
  • Outlook 2019 for Mac or Outlook 2016 for Mac
  • Mac OS X 10.10 or later.

Important

Although the add-in allows you to preview email signatures in Outlook on a Mac, these signatures need to be created beforehand in the Manage Signatures App (which runs on Windows).

Outlook on the web (OWA):
  • Any modern browser which supports ECMAScript 5.1, HTML5 and CSS3 (Internet Explorer 11 or later, or the latest versions of Microsoft Edge / Chrome / Firefox / Safari).
Custom Attributes Sync App
Required permissions: The admin account whose credentials are used to access Azure AD attributes needs to be able to enumerate Office 365 users and mailboxes. Learn more
Requirements:
  • 64-bit Windows, at least Vista SP2 or Windows Server 2008 SP2,
  • .NET Framework 4.7.1,
  • Internet Explorer 9 or later.
Other
Notes and
warnings:

The software supports multi-factor authentication. However, using the app password is necessary when synchronizing custom AD attributes with the software via the Custom Attributes Sync App. Learn more

In hybrid environments, our software can process only emails going through Office 365 (EOP) servers. See this article to learn how to use CodeTwo software in different hybrid deployments.
Shared mailboxes are supported.
Office 365 DKIM-signed emails are supported.
Microsoft Planner notifications are supported. Learn more
Emails sent from aliases (using an alias as the email sender) are supported. Learn more
The following message types are only supported in client-side mode (and in combo mode for client-side signature rules):
  • messages sent as groups, distribution lists and contacts,
  • messages sent from mail-enabled public folders.

Messages digitally signed and encrypted via Office 365 encryption / Azure Information Protection (Azure RMS and related features: Encrypt-Only, Do Not Forward, sensitivity labels) or by other encryption technologies (e.g. S/MIME, PGP or OpenPGP such as GPG) are supported in client-side mode and in combo mode for client-side signature rules

In server-side mode, encrypted/digitally signed messages will be stamped with signatures only if encryption takes place after these messages pass through the CodeTwo services. The same applies when using server-side signatures in combo mode.

Out of Office messages (autoreplies) are not supported.

See also

Installation and configuration - this article describes how to install and configure the program step by step.

Was this information useful?