Mimecast Synchronization Engine - Site Binding

This guide describes how to use the site configuration utility to configure and view information about your Mimecast Synchronization Engine (MSE) site.

STEP 1 - Configuring the Microsoft Mailbox

The Mimecast Synchronization Engine uses a single mailbox with elevated permissions to access the mailboxes in your organization; this is referred to as the Microsoft Mailbox. The Microsoft Mailbox requires Impersonation permissions to access other mailboxes. For full details on these requirements, read the following:

To set up the Microsoft Mailbox:

  1. Open the Site Configure utility on the server where MSE is installed.
  2. Click the Accounts tab.
  3. Complete as follows:
Field / Option Description
SMTP Address Enter the primary email address of the user you want to use to access your environment.
Password Enter the primary email address's password in the "SMTP Address" field.
Use Exchange Impersonation Please select this option to allow the user to Impersonate other users in your organization to perform tasks on their behalf.
Host Address
(For OAuth)
If you used a custom Host Address during the application registration, use that instead of the default one.
Tenant ID
(For OAuth)
See: Register an application with Azure AD and create a Service Principal (Step 4).
Client ID
(For OAuth)
See: Register an application with Azure AD and create a Service Principal (Step 4).
Client Secret
(For OAuth)
See: Configure for app-only authentication (Step 8).
Directory Type
The option to specify in this dropdown is controlled by the type of deployment you are using. Refer to the table below for the value to select:
Target Environment Directory Type
Microsoft Exchange (On-Premises) Microsoft Active Directory
Microsoft Active Directory (On-Premises) Microsoft Active Directory
Microsoft 365 (Standalone) Microsoft 365 Directory

 

Changing the Directory Type affects where group/address resolution occurs. This will either be the On-Premises Active Directory or Microsoft 365.

Requires Authentication Select whether authentication is required.
  1. Click the Apply button.
  2. Start the Site Bind process described below.

 

STEP 2 - Configuring Application Impersonation

Application Impersonation is used when a single account needs to access many mailboxes. It allows an application (e.g., Mimecast Synchronization Engine) to use a dedicated service account to access multiple users' mailboxes and their respective data. The following Microsoft KB Article describes configuring Application Impersonation in your environment to allow Mimecast to access your mailboxes as a named user.

Exchange 2016 or Later

For Exchange 2016 or later, the user selected as the master mailbox must:

  • Have you enabled the Microsoft Mailbox? (configured in Step 1)
  • Have you assigned the Microsoft Mailbox user the Application Impersonation Management Role? To configure this permission:
  1. Open an Exchange Management Shell with a logon containing the Organization Management role.
  2. Run the following command:
    New-ManagementRoleAssignment -Name:exchangeImpersonation -Role:ApplicationImpersonation -User:User1
    User1 is the account selected to run the Mimecast Synchronization Engine or Sync & Recover service.
  3. Check that the user has been successfully added to the Management role by running the following command:
    Get-ManagementRoleAssignment -Role ApplicationImpersonation -GetEffectiveUsers | Where { $_.EffectiveUserName -Eq "User1" }
    Where the same User1 and the same 'name' value (exchangeImpersonation) is used from Step 2.

 

Microsoft 365 Hybrid Environments

In a Microsoft 365 hybrid environment:

  • On-premises Exchange: The Mimecast Services for Exchange (MSE) service account requires the Application Impersonation role to process mailboxes.
  • Exchange Online: The MSE OAuth application needs Exchange.ManageAsApp, EWS full_access_as_app permissions, and the Exchange Administrator Role.
  • Permissions must be configured in both environments to ensure the MSE can operate seamlessly across the hybrid setup.

 

STEP 3 - The Binding Process

In the context of the MSE, a binding is a security association between the application and Mimecast. The binding is created when a user with the required permissions successfully authenticates using the site Bind process on the server where the MSE is installed. You need a binding to view the MSE site in the Administration Console and apply scheduled tasks.

 

Binding Requirements

 

Binding Process

    1. Open Mimecast Synchronization Engine.
      1. Configure the Accounts tab according to your environment using the supported configurations below.

 

Microsoft 365 Using OAuth

      1. Follow the OAuth steps in the article Configuring OAuth to Configure the Azure App, Set Permissions, Account Roles, and Generate the Certificate and Thumbprint.
      2. Then, complete the Accounts tab section as shown below.
  1. To use Open Authentication for O365, you only need to check the Open Auth option.
  2. Enter the Microsoft O365 mailbox SMTP address.
  3. The Host Address should be prefilled with the Office 365 EWS address.
  4. Complete the following details.
  • Tenant ID
  • Client ID
  • Client Secret
  • Cert. Thumbprint
  • Organization
  1. Ensure the Directory Type is set to Microsoft Office 365 Directory.
  2. Click Apply.
image.png

 
  1. In the Validation window, enter your Mimecast Sync Engine Administrator address and the Cloud Password associated with that account. See Authentication - Cloud Password Reset - Configurations and Administrator Roles for more information.
  2. After entering the credentials, click Apply at the bottom of the screen.

Failure to provide correct credentials for the authentication type or using a user with insufficient permissions results in the site bind failing.

  • If the screen to the right is presented, the MSE has been bound successfully.
  • If any errors appear, please see the latest Mimecast Bind Logs in...%ProgramData%\Mimecast Synchronisation Engine\Logs\Site Configure\
image.png

 

On-Premise Exchange & On-Premises Exchange with O365 Hybrid Using OAuth

      1. Follow the OAuth steps in the article Configuring OAuth to Configure the Azure App, Set Permissions, Account Roles, and Generate the Certificate and Thumbprint.
      2. Then, complete the Accounts tab section as shown below.
  1. To use Open Authentication with an On-Premises and Hybrid exchange setup, check the Basic Authentication and Open Auth boxes.
  2. Complete the SMTP Address for the On-Prem Microsoft Mailbox, enter the password, and check the Use Exchange Impersonation fields.
  3. Enter the SMTP for the Microsoft Mailbox for O365.
  4. The Host Address should be prefilled with the Office 365 EWS address.
  5. Complete the remaining fields with the following details.
  • Tenant ID
  • Client ID
  • Client Secret
  • Cert. Thumbprint
  • Organization
  1. Ensure the Directory Type is set to Microsoft Active Directory, and enter your Exchange Server authentication details...
  • Server - The on-premises Active Directory Server Name or FQDN you want to connect to.
  • User Name - The MSE service account
  • Password - MSE service account domain credentials are only used for MSE AD Sync.
  1. Click Apply.
image.png
  1. In the Validation window, enter your Mimecast Sync Engine Administrator address and the Cloud Password associated with that account. See Authentication - Cloud Password Reset - Configurations and Administrator Roles for more information.
  2. After entering the credentials, click Apply at the bottom of the screen.

Failure to provide correct credentials for the authentication type or using a user with insufficient permissions results in the site bind failing.

  • If the screen to the right is presented, the MSE has been bound successfully.
  • If any errors appear, please see the latest Mimecast Bind Logs in...%ProgramData%\Mimecast Synchronisation Engine\Logs\Site Configure\
image.png

 

On-Premise Exchange using Basic Auth

To configure and bind to an on-prem exchange, complete the Accounts tab section as shown below.
 

  1. To use the Basic Authentication on-premises exchange setup, you must only check the Basic Authentication box.
  2. Complete the SMTP Address for the Microsoft Mailbox, enter the password, and check the Use Exchange Impersonation fields.
  3. Ensure the Directory Type is set to Microsoft Active Directory, and enter your Exchange Server authentication details...
  • Server - The on-premises Active Directory Server Name or FQDN you want to connect to.
  • User Name - The MSE service account
  • Password - MSE service account domain credentials are only used for MSE AD Sync.
  1. Click Apply.
image.png
  1. In the Validation window, enter your Mimecast Sync Engine Administrator address and the Cloud Password associated with that account. See Authentication - Cloud Password Reset - Configurations and Administrator Roles for more information.
  2. After entering the credentials, click Apply at the bottom of the screen.

Failure to provide correct credentials for the authentication type or using a user with insufficient permissions results in the site bind failing.

  • If the screen to the right is presented, the MSE has been bound successfully.
  • If any errors appear, please see the latest Mimecast Bind Logs in...%ProgramData%\Mimecast Synchronisation Engine\Logs\Site Configure\
image.png

 

On-Premise Active Directory

To configure and bind to an on-premises Active Directory method, complete the Accounts tab section as shown below.

  1. To configure for On-Premise Active Directory, leave both Auth boxes unchecked.
  2. Ensure the Directory Type is set to Microsoft Active Directory, and enter your Exchange Server authentication details...
  • Server - The on-premises Active Directory Server Name or FQDN you want to connect to.
  • User Name - The MSE service account
  • Password - MSE service account domain credentials are only used for MSE AD Sync.
  1. Click Apply.
image.png
  1. In the Validation window, enter your Mimecast Sync Engine Administrator address and the Cloud Password associated with that account. See Authentication - Cloud Password Reset - Configurations and Administrator Roles for more information.
  2. After entering the credentials, click Apply at the bottom of the screen.

Failure to provide correct credentials for the authentication type or using a user with insufficient permissions results in the site bind failing.

  • If the screen to the right is presented, the MSE has been bound successfully.
  • If any errors appear, please see the latest Mimecast Bind Logs in...%ProgramData%\Mimecast Synchronisation Engine\Logs\Site Configure\
image.png

 

Next Steps

Select and proceed to the relevant Exchange Task(s) articles you would like the MSE client software to perform and implement according to your environment.

>> Exchange Tasks >>

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.