Dynamics CRM E-mail Router Configurations

This post should help you if you are setting up the Dynamics CRM E-Mail Router etc ...

• Functionality is always the same although execution (Configuration Method) may be different
• Even with a different e-mail system in UAT from the users perspective ‘look’s the same as PROD’
• As N number of users increases, configuration is more complicated
• Centralisation -> More complex configuration
• Possible to mix and match configurations – this will likely be used as a cutover method
• Data Flows are like so; 

Dynamics CRM Outlook Client Configuration Method

• Easiest to configure and easier to configure than the Dynamics CRM E-Mail Router configuration – most basic configuration
• Not much fundamental difference between Dynamics CRM Outlook Client and Dynamics CRM E-Mail Router configuration
• Cannot be used for Queues
• Load is spread across all clients – this could slow down laptops and tablets, workstations won’t be a problem

Dynamics CRM E-Mail Router Configuration Method

• With Dynamics CRM E-Mail Router messages are created from the central router rather than the client
• So possibly being a different configuration method, this may be more stable than say the myriad of local Outlook environments
• Still spread the Load problems, because need to listen on ‘N’ mailboxes rather than on just 1 mailbox in the Forward Mailbox scenario. 
• Only requires admin rights to the E-Mail Router and Outlook client
• Probably more efficient overall since centralised models are generally more efficient

Forward Mailbox

• Most complicated to configure
• Need to create an extra mailbox
• Requires more Exchange Administrator Involvement
• Create mailbox
• Deploy forwarding rules
• Contact point is only one 1 Mailbox