Tenant registration

After you created a CodeTwo Admin Panel account, it's time to register your Microsoft 365 tenant to CodeTwo and specify how signatures should be added to this tenant. See the step-by-step instructions below or check out our video tutorial:

To begin, sign in to CodeTwo Admin Panel (if you are not already signed in). On the Tenants page, click ADD TENANT (Fig. 1.) to launch a wizard that will guide you all the way through the registration process.

Fig. 1. Registering a new Microsoft 365 tenant to CodeTwo Admin Panel. 

License agreement

In the first step of the wizard, read and accept CodeTwo's EULA and linked terms and conditions, then click Next to proceed to the next step.

Sign in

In the second step, click the Sign in as tenant’s Microsoft 365 global admin button (Fig. 2.) and follow the steps shown on the Microsoft sign-in page. Accept the permissions required for CodeTwo Email Signatures 365 to include user data in email signatures. Note that the global admin account is the only account type in Microsoft 365 that can grant the necessary permissions.

Once you've signed in, you'll automatically jump back to the wizard. Click Next to continue.

Fig. 2. Sign in as Microsoft 365 global admin to associate your tenant with CodeTwo.

Region

Here you need to choose an Azure region of the CodeTwo service. This is where your signatures will be added (if you select the cloud signature mode in the next step) and where your settings and some of your data will be stored. You can select a region by clicking its name on the map (Fig. 3.) or by using the Region drop-down menu. It is recommended to choose the same region in which your Microsoft 365 tenant resides (or the nearest one).

Fig. 3. Selecting a location of the CodeTwo service.

Signature mode

This is where you decide how CodeTwo signatures should be added to emails in your organization. You can choose from three signature modes:

• Cloud (server-side) mode – this is the default mode that works with all email clients. Signatures are added in the cloud, after an email is sent (end users can still preview their signatures in Outlook by using a dedicated CodeTwo Web Add-in). This mode requires setting up Exchange Online connectors to reroute emails from your Microsoft 365 tenant though CodeTwo cloud service, located in the Azure region of your choice.
• Outlook (client-side) mode – works with Outlook only (Outlook for Windows, Outlook for Mac and Outlook on the web / OWA). This mode uses a modern Outlook Web Add-in that adds a signature directly to the email body as end users compose their email (the add-in deployment is fully automated – no end-user installation required). In Outlook mode, emails are not rerouted through CodeTwo cloud service, so no connectors configuration is needed.
• Combo mode – works with all email clients. It's a combination of the cloud and Outlook signature modes. A signature is added as end users type an email in Outlook. If they use other email clients, the signature is added in the cloud, after an email is sent.

Once you select a signature mode (as shown in Fig. 4.), click Next and go the proper step:

• If you selected cloud or combo mode, continue with the SPF record step.
• If you selected Outlook mode, go directly to the last step – Deployment. 

Fig. 4. Signature mode selection.

SPF record

In this step, you will find an entry (see Fig. 5.) that should be added to the SPF record of your Microsoft 365 tenant. This is to make sure emails with CodeTwo signatures are not marked by Exchange Online Protection (EOP) as junk and don't land in the recipients' spam folder. This entry corresponds to the Azure region you selected earlier.

For instructions on how to configure the SPF record of a domain, see this step-by-step guide.

Once you have updated your SPF record, click Check my SPF record to validate that everything works correctly. If the status shows SPF record OK (Fig. 5.), click Next to go to the next step of the wizard. 

Fig. 5. Validating the SPF record configuration.

Note that you should use CodeTwo Email Signatures 365 with your own (vanity) domains. If your tenant is only using the default onmicrosoft.com domain, the validation will not occur. The onmicrosoft.com domain is managed by Microsoft and its SPF record can't be changed at your request. You can continue with the wizard for now but remember to update your SPF record as soon as you add your own domain to your Microsoft 365 tenant. Learn more

Connectors

To get CodeTwo cloud signatures (added after an email is sent), you need to create Exchange Online connectors and an Exchange transport rule that will reroute your organization’s email through CodeTwo. The configuration wizard can create these connectors automatically for you, which is the recommended method (the Automatically set up my connectors option is selected by default).

To proceed with the default automatic connector setup, copy the code shown in Fig. 7. by using the  button and click Authorize. This will open a Microsoft sign-in page in a new tab.

Fig. 7. The authorization code in the tenant registration wizard.

Paste the copied code in the space provided and click Next. Then, sign-in to your Microsoft 365 tenant by providing global admin credentials. Once you have successfully signed in, the Microsoft sign-in page will close automatically.

Back in the configuration wizard, proceed to the next step (the wizard will configure the connectors in the last step of the wizard). 

Users

(This step does not appear if you selected the manual connector setup in the previous step)

In the Users step you need to specify users (senders) whose emails will be rerouted through CodeTwo to get signatures. Every sender whose emails go through our cloud service uses one license from your license pool, no matter if this user is defined in any signature rule. That is why you should pay special attention when defining the scope of users here. Find out more how the license counting works

You can select all users in your Microsoft 365 tenant (Azure Active Directory) or limit the scope of senders to members of a particular group in your tenant (a distribution list, Microsoft 365 group, or mail-enabled security group; groups hidden from your address book are also available). If you select the second option, click Choose to select a group. Use the checkbox below these options (as shown in Fig. 8.) to determine if signatures should be added to internal emails (which is the default behavior) or not.

Fig. 8. Configuring the scope of users.

Here are some additional considerations when configuring the scope of users:

• It is recommended to create a separate group for all users who will get CodeTwo signatures. This lets you avoid excessive usage of licenses.
• If you want to select more than one group, you need edit the transport rule and add another group manually, as described in this article.
• If you select a group that has other groups nested inside, emails sent by members of the nested groups will also go through a CodeTwo cloud services.
• If you need to further customize the scope of users who will get signatures, you can do that by creating signature rules.
• Any changes you make in your Active Directory might take some time (up to several hours) to propagate and synchronize with CodeTwo. This means that:
  • If you have just created a new group, it may not be available in the group picker (which opens when you click Choose) right away.
  • Changes made to the group selected in the wizard also need time to propagate. For example, if you add new users to this group, they might not get signatures right away. Learn more
• You will also be able to reconfigure the scope of users later, if you need. Learn more

Click Next to start the deployment.

Deployment

The deployment process is fully automated. The configuration wizard will now add your Microsoft 365 tenant to CodeTwo Admin Panel.

If you choose to use CodeTwo Email Signatures 365 in the Outlook (client-side) mode, go to this section to learn what your next steps are.

If you selected cloud (server-side) or combo mode, the wizard will now perform tenant provisioning (which might take up to a few minutes). It's a process of assigning a unique certificate that's necessary for the correct operation of Exchange Online connectors. If you authorized CodeTwo to configure the connectors automatically, the wizard will do this now as well (Fig. 9.). It usually takes just a few minutes for all these changes to propagate across your Microsoft 365 tenant.

[your unique ID].smtp.codetwo.online

Fig. 9. Actions performed during the deployment process (cloud mode).

Once the deployment is complete, click Finish to close the wizard. A screen showing what next steps you need to take will be shown. You can also find these steps below in this article. 

Next steps

Depending on what signature mode you selected in the configuration wizard, to start using CodeTwo Email Signatures 365, you need to perform the following steps:

• Cloud (server-side) mode
• Outlook (client-side) mode
• Combo mode

Next steps: cloud (server-side) mode

1. Set up email signatures and assign end users who will get them (for instructions, see our video tutorial or this article).
2. (Optional) Deploy our Outlook Web Add-in to these end users to allow them preview their signatures in Outlook (learn more about this feature or see deployment instructions).
3. (Optional) If you use smart host (mail relay) services in your organization, additional configuration might be required. See this article for details.

Next steps: Outlook (client-side) mode

1. Set up email signatures and assign end users who will get them (for instructions, see our video tutorial or this article).
2. Deploy our Outlook Web Add-in to these end users (see deployment instructions).

Next steps: combo mode

1. Set up email signatures (both cloud and Outlook signatures) and assign end users. See our video tutorial or the following articles:
   • set up cloud signatures,
   • set up Outlook signatures.
2. Deploy our Outlook Web Add-in to end users who will get CodeTwo Outlook signatures (see deployment instructions).
3. (Optional) If you use smart host (mail relay) services in your organization, additional configuration might be required. See this article for details.