Configuring Exchange Server

Ensure the user's Sage CRMemail address matches the impersonated user's primary SMTP address in Exchange. Also ensure the user is included in the global address list in Exchange.

You must prepare Exchange Server to ensure Sage CRM Exchange Integration works correctly.

  1. Complete the prerequisites to configure Exchange Impersonation. For more information, see the latest articles on msdn.microsoft.com.
    • Enable Client Access Server (CAS) on Exchange Server. This performs several functions including exposing the EWS virtual directory.
    • Set up domain administrator credentials, or other credentials with the permission to create and assign roles and scopes.
    • Install Remote PowerShell on the computer from which you run commands.
  2. Set up an Exchange impersonated user mailbox to access the mailboxes of other Exchange users if you have not already done so.
  3. Run the following cmdlet in the Exchange Management Shell. This applies the ApplicationImpersonation role to the Exchange impersonation user so that it can access other mailboxes.

    New-ManagementRoleAssignment –Name:<any name> –Role:ApplicationImpersonation –User:<impersonation user name here>


    For more information about the Exchange Management Shell, see Using the Exchange Management Shell on msdn.microsoft.com.
    For complete information about the New-ManagementRoleAssignment cmdlet, run the following command in the Exchange Management Shell:

    Get-Help New-ManagementRoleAssignment -Full

    Alternatively, to manually enable a user for impersonation using EAC, add the ApplicationImpersonation admin role in permissions and add the mailbox used for impersonation to this role.

    If you're using Office 365 Online, you must explicitly give the impersonated user application impersonation rights in the Office 365 Exchange Admin Centre or via PowerShell commands.
  4. Using Outlook Web Access, log on as the impersonation user to initialize the account.
  5. Click Servers | Virtual directories | EWS | Authentication and enable Basic authentication in the Exchange Administration Center (EAC). Basic authentication is how Sage CRM authenticates with EWS. On its own, Basic authentication is not a secure authentication method so we recommend that you use Secure Sockets Layer (HTTPS) for the connection between Sage CRM and Exchange to secure the connection.
If your Exchange hosting provider does not support Basic authentication on the EWS virtual directory and supports Windows authentication only, you cannot configure Exchange Integration because Sage CRM does not support Windows authentication.