› Dynamics CRM › Setup Email Router for Microsoft Dynamics CRM 2015 Online and Exchange Online

Setup Email Router for Microsoft Dynamics CRM 2015 Online and Exchange Online

 4 Comments

Email Router is a service that runs continuously to synchronize only emails between CRM and specified Email system. Tasks, Appointments and Contacts are not synchronized using Email Router.

Email Router is a separate component available for download and needs to be installed.

Note: Only one instance of Email Router should be setup for an Organization.

Settings in Dynamics CRM Online

In Dynamics CRM Online, make sure the following settings are in place:

The Process Email using in the Email Configuration Settings under Settings > Email Configuration should be: Microsoft Dynamics CRM 2015 Email Router. Also make sure, Incoming and Outgoing Email are set to Email Router as shown below.

1
 
Additionally, set the user’s mailbox and the Incoming and Outgoing Emails should be Server-Side Synchronization or Email Router marked as Success when a mailbox is approved for Email and is Test & Enabled as well.

Download & Install Email Router

You’ll need to download the Email Router so that you can install it on your server. Here’s where you can get to download the Email Router:

https://www.microsoft.com/en-us/download/details.aspx?id=45017

Run the setup and let the wizard install Microsoft Dynamics CRM Email Router Service.

Configuration Profiles

Configuration Profiles hold information about the server and authentication methods to the same to which the Email Router will connect to.

You’ll need to create one or more Incoming configuration profiles and one or more Outgoing configuration profiles.

  1. First, I’ll create a configuration profile for Outgoing email.
    Enter a suitable Profile Name for the configuration profile you are creating.
  2. Chose the direction between Incoming and Outgoing. For this configuration, I’ll choose Outgoing.
  3. Since I’m configuring for Exchange Online server, I’ll choose Email Server Type as ExchangeOnline.
  4. The Authentication Type will remain Clear Text since this is the only Authentication Type for ExchangeOnline.
  5. Check mark the Use Autodiscover as it is a way to obtain the Exchange Web Services URL. This option is available when you select ExchangeOnline.
  6. In Access Credentials, I’ll select Other Specified since I want Email Router to authenticate by using the credentials of a specified user.
    Note: The specified user must have full access to mailboxes. Ideally, an Administrator should be selected.
  7. For User Type – When ExchangeOnline server type is selected and Other Specified as the Access Credentials is chosen, options available are Administrator or User. I’ll chose Administrator since I want to enter only 1 credential to authenticate mailboxes.
  8. Enter Username and Password in username@fulldomain
  9. For Access Type – Use either Delegate Access or Send As access. I chose Delegate Access in this case where I want email to be sent as ‘Send on behalf of’.
  10. 2

    Similarly, I’d configure the following for Incoming configuration for CRM Admin user, which is as follows:

    3

Deployments

At least 1 deployment needs to be configured. Deployments hold the information to connect to your Dynamics CRM environment.

  1. Create a New deployment in the Deployments
  2. I’ll chose the Deployment as Microsoft Dynamics CRM Online since I’m connecting to an Online deployment of my Dynamics CRM.
  3. Microsoft Dynamics CRM Server: You’ll need to use https://disco.crm5.dynamics.com/<OrganizationName> where, Organization Name can be found in Settings > Customizations > Developer Resources.

    4

    Note: I’ll be using disco.crm5.dynamics.com/ since my organization is in Microsoft Office 365.

  4. Provide Access Credentials of the Administrator mailbox which you want the Email Router to connect to Dynamics CRM Online deployment.
  5. Select the default Configuration Profiles that the current deployment will use. Chose from the Incoming and Outgoing profiles created in the Configuration Profiles in the Email Router.
  6. 5

Users, Queues and Forward Mailboxes

Users, Queues and Forward Mailboxes of a CRM deployment can be managed under this tab in the Email Router application.

  1. Select the Deployment created in the Email Router and click Load Data. This will show a list of all the mailboxes for that organization.
  2. 6

  3. You can chose any once / all mailboxes and click on Test Access to verify the connection was successful or not.
  4. Once you get a success as shown below, your mailbox is now functional.
  5. 7

Forward Mailbox

A Forward Mailbox is a centralized mailbox which reduced administrative efforts for a mailbox and diverts messages to respective users.

Here, your Email Router is set to send and receive Email from and to CRM using the Email Router.
 


Liked it? Share it.

4 thoughts on “Setup Email Router for Microsoft Dynamics CRM 2015 Online and Exchange Online”

  1. Hi,
    We have successfully installed CRM Email Router 2016. Our CRM application is CRM online 2016 version. We have configured the outgoing profile. And also configure deployment option to connect to CRM 2016 online. URL is disco.crm.dynamics.com/OrgName and provided service account user name and password. Service account is having system admin role in CRM. When we click on load data we are getting below error.
    The E-mail Router Configuration Manager was unable to retrieve user and queue information from the Microsoft Dynamics CRM server. This may indicate that the Microsoft Dynamics CRM server is busy. Verify that URL ‘dev.crm.dynamics.com/CrmOrgName’ is correct. Additionally, this problem can occur if specified access credentials are insufficient. To try again, click Load Data. (GetAuthState() – Request Status:.).

    When we are using any particular user credential instead of service account it is working fine. However when we used service account it is giving this error.

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.