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:
- Directory Synchronization for Active Directory synchronization.
- Configure Open Auth with Microsoft.
To set up the Microsoft Mailbox:
- Open the Site Configure utility on the server where MSE is installed.
- Click the Accounts tab.
- 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:
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. |
- Click the Apply button.
- 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.
- Microsoft Article: How to Configure Application Impersonation
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:
- Open an Exchange Management Shell with a logon containing the Organization Management role.
- Run the following command:
User1 is the account selected to run the Mimecast Synchronization Engine or Sync & Recover service.New-ManagementRoleAssignment -Name:exchangeImpersonation -Role:ApplicationImpersonation -User:User1 - Check that the user has been successfully added to the Management role by running the following command:
Where the same User1 and the same 'name' value (exchangeImpersonation) is used from Step 2.Get-ManagementRoleAssignment -Role ApplicationImpersonation -GetEffectiveUsers | Where { $_.EffectiveUserName -Eq "User1" }
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
- Outbound connectivity using HTTPS (port 443) from the server where the MSE is installed to Mimecast.
- Access to the server where the MSE is installed.
- The email address and password for the Mimecast account. See the Mimecast Administration Console - Administrator Role Permissions and Administration - Managing Administrator Roles pages for creating, adding, and setting the role and permissions.
- The user account used must have the "Synchronization Engine Administrator" role.
- Before binding via Open Auth, a single-tenant application must be created. To do this, follow the instructions in this article: How to Configure an Open Authentication Register.
Binding Process
- Open Mimecast Synchronization Engine.
- Configure the Accounts tab according to your environment using the supported configurations below.
Microsoft 365 Using OAuth
- Follow the OAuth steps in the article Configuring OAuth to Configure the Azure App, Set Permissions, Account Roles, and Generate the Certificate and Thumbprint.
- Then, complete the Accounts tab section as shown below.
|
|
Failure to provide correct credentials for the authentication type or using a user with insufficient permissions results in the site bind failing.
|
On-Premise Exchange & On-Premises Exchange with O365 Hybrid Using OAuth
- Follow the OAuth steps in the article Configuring OAuth to Configure the Azure App, Set Permissions, Account Roles, and Generate the Certificate and Thumbprint.
- Then, complete the Accounts tab section as shown below.
|
|
Failure to provide correct credentials for the authentication type or using a user with insufficient permissions results in the site bind failing.
|
On-Premise Exchange using Basic Auth
To configure and bind to an on-prem exchange, complete the Accounts tab section as shown below.
|
|
Failure to provide correct credentials for the authentication type or using a user with insufficient permissions results in the site bind failing.
|
On-Premise Active Directory
To configure and bind to an on-premises Active Directory method, complete the Accounts tab section as shown below.
|
|
Failure to provide correct credentials for the authentication type or using a user with insufficient permissions results in the site bind failing.
|
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.
Comments
Please sign in to leave a comment.