Supported platforms and requirements

CodeTwo Email Signatures for Office 365 does not require installation of any components in the client's environment. This is because the software's main engine - the CodeTwo Email Azure Service - is operated by CodeTwo on Microsoft Azure servers where emails are processed seamlessly, without client's engagement. Thus, the program's end users do not have to install anything. The administrator of the client's Office 365 tenant must only run the following two components:

CodeTwo Admin Panel: a web-based panel for adding new tenants, managing payments, monitoring the service status as well as configuring connectors and transport rules.
CodeTwo Email Signatures for Office 365 Manage Signatures App: a ClickOnce app for signature management.

A third component (CodeTwo Email Signatures for Office 365 Custom Attributes Sync App) is required if custom AD attributes need to be manually synchronized in an Office 365 tenant.

Additionally, the CodeTwo Email Signatures for Office 365 Add-in allows end users to preview signatures while composing emails in Outlook and OWA (soon also on mobile clients).

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

Software components
Tenant administration:	CodeTwo Admin Panel runs entirely in a web browser.
Signature management:	Manage Signatures App is a ClickOnce application launched directly from the CodeTwo Admin Panel or via the Start menu.
Manual sync of custom attributes:	Custom Attributes Sync App is a ClickOnce application launched from within the CodeTwo Admin Panel or via the Start menu.
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.

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). Info All of the above Office 365 plans store data in the Azure AD cloud, and access to Azure AD is required by the CodeTwo program. A separate Microsoft Azure subscription is not required for any of these plans. A modern web browser: Internet Explorer 9 or later, Microsoft Edge 20.10240 or later, other browsers such as Google Chrome, Mozilla Firefox or Opera.
Manage Signatures App & Custom Attributes Sync App
Required permissions:	Office 365 global admin rights.
Requirements:	64-bit Windows, at least Vista SP2 or Windows Server 2008 SP2, .NET 4.5 Framework, Internet Explorer 9 or later.
CodeTwo Email Signatures for Office 365 Add-in
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, you need to update Office 2013 to the latest version. Learn how to install Office updates Outlook for Mac: Outlook 2016 for Mac, Mac OS X 10.10 or later. 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).

Other
Notes and warnings:	The software supports multi-factor authentication. Certain exceptions apply: When configuring connectors and deregistering the tenant, remember to use the app password instead of your regular Office 365 password. Learn more Synchronization of custom attributes via the Custom Attributes Sync App cannot be performed with MFA enabled. Learn more
	Shared mailboxes are supported.
	Office 365 DKIM-signed emails are supported.
	Microsoft Planner notifications are supported. Learn more
	The following message types are not supported (they will not be stamped with signatures): Out of Office messages (autoreplies), messages digitally signed and encrypted (e.g. S/MIME, PGP or OpenPGP such as GPG) on the client's side, messages encrypted via Office 365 Message Encryption (Azure RMS), messages sent as distribution groups/lists, messages sent from aliases (using an alias as the email sender), messages sent from mail-enabled public folders.

Supported platforms and requirements

See also