Microsoft Dynamics CRM for Outlook and Proxy Servers

Microsoft Dynamics CRM for Outlook and Proxy Servers

The latest update to the Outlook Client for Microsoft Dynamics CRM 2011 (Update Rollup 15 and Update Rollup 11 CU) as well as the Outlook Client for Microsoft Dynamics CRM 2013, includes a number of enhancements for the Outlook Client, mostly around performance improvements.

One of the major changes is the separation of some of the core CRM components from the Outlook processes.

While this separation is a great result for the improvement of performance, it also introduces some “hidden” and unexpected behaviour in environments that have proxy servers for internet access and are using either CRM Online or a Partner Hosted CRM.

Historically CRM ran within the Outlook process and the Outlook client is Proxy aware, so adopted the settings configured for your internet access, this meant that you could use CRM without any issues, the separate process, Microsoft.Crm.Application.Outlook.WebFormsHost.exe however, is not proxy aware by default. This results in a behaviour where CRM for Outlook appears to be functioning normally on the surface, until you try and open a form record (or new form). The reason it appears to work before this point is because Dashboard, Record lists and preview pane are all still running within the Outlook process, so these calls to the CRM web services execute as expected, but the moment you try and open a form, nothing happens.

If you enable tracing for the Outlook client, you are likely to find an error in the trace logs of type 407, proxy authentication required.

The fix for this is relatively straight forward, although does need to be applied on each user’s computer.

You need to create a new Config xml file for the Microsoft.Crm.Application.Outlook.WebFormsHost.exe process. This file should be called Microsoft.Crm.Application.Outlook.WebFormsHost.exe.config and should be placed in the \Microsoft Dynamics CRM\Client\res\web\bin in your respective “Program Files” folder (“Program Files” for 64-Bit Clients and “Program Files(x86)” for 32-Bit Clients)

The contents of this file should be a derivative of the following, filling in your own proxy server specific details :

<defaultProxy enabled=”true” useDefaultCredentials=”true” >
<proxy usesystemdefault=”true” bypassonlocal=”True” proxyaddress=”http://<proxy address>:<port #>“/>

Once you have saved this file and restarted the Outlook Client then you should now hake a working Outlook Client.


Be Sociable, Share!


  1. Thanks for the advice, this is exactly the issue I am struggling with at the moment, and having spend an hour and a quarter with a Microsoft support person from Washington this afternoon, he seemed to be struggling too.
    I will make this change tomorrow when I am in the office and I am sure it will be fine and work perfectly, however it raises a question, in that I use my notebook PC at the office with a proxy server, and out of the office without a proxy, will the configuration work in that manner or are there other issues I am going to encounter.

    Thank you.

  2. This is a great find and will hopefully be addressed by MSFT soon. Does adding this config file stop the client working if they are not behind a proxy. i.e. a proxy at work and not at home?

  3. Great post – and certainly solves the problem of users behind a proxy, but what if those users are sometimes NOT behind the Proxy for internet access – such as laptop users when they are at home or elsewhere?

    Is there a quick way for them to disable this so as not to use the proxy settings in those circumstances?



  4. How does this impact connectivity when the user is on a network where the proxy is not present ie. working from home?

Leave a Reply

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

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

WordPress Appliance - Powered by TurnKey Linux