Microsoft Dynamics CRM/365 provides functionality to integrate your CRM with your mail system. This allows you to track email messages in CRM and send timely email messages to the people that matter most for your organisation.
There are several options available for email integration with Dynamics CRM/365 – the Microsoft CRM Email Router, Server-side Synchronization, or Outlook integration.
In this blog, I will share some scenarios where certain types of emails are not processed by the Email Router or Server-side Sync. It is important to be aware of these scenarios so there are no surprises when setting up email integration.
For each scenario, suppose you have an email-enabled Queue in Dynamics CRM/365 that is configured for incoming email. The email address of the queue is firstname.lastname@example.org. Also assume that Exchange Online is our email server.
In this scenario, an email is sent To email@example.com and is BCCd to firstname.lastname@example.org. When the email arrives in Exchange, the BCC field is cleared so there is no mention in the email metadata of the email@example.com email address.
The Email Router and Server-side Synchronization skips over this email because it cannot identify the email address in the metadata. This email is never routed to CRM.
A redirect rule can be set up in Exchange which moves an email from one mailbox to another. For example, let’s pretend that Frostys Ice Cream Store had an old mailbox called firstname.lastname@example.org, which they no longer want to use. They want to allow people to send emails to this mailbox, but have the emails redirected to the new email@example.com mailbox.
If an email is sent to firstname.lastname@example.org, the email arrives in that mailbox and is then automatically redirected to email@example.com. The metadata on the email has the “To” field set to firstname.lastname@example.org, so the Email Router and Server-side Sync will skip over this email, and it is never routed to CRM.
A distribution group is an internal virtual mailbox that consists of multiple other mailboxes. For example, there might be an email@example.com distribution group, which contains the firstname.lastname@example.org email address.
If an email is sent to email@example.com, the email will arrive in the firstname.lastname@example.org mailbox. Again, the metadata has no mention of email@example.com and this email is also skipped by the Email Router and Server-side Sync.
A bounced email may appear in a mailbox for several reasons – the most common being a misspelt email address.
For example, if an email was sent from firstname.lastname@example.org to a non-existent mailbox, an “Undelivered” email will appear in the email@example.com mailbox. The Email Router and Server-side Sync will not route this to CRM.
One of our customers needed emails matching the scenarios above to route through to CRM. To solve the issue, we built our own integration service which sits alongside the Microsoft CRM Email Router.
Let us know if you’re having similar troubles with your email integration with Dynamics CRM/365.