Exchange Server sync in AX2012 R3 CU8

In a previous post I outlined doing some planning with the different options for sending email out of AX2012. While not email but related there is an ability to sync Contacts, tasks, appointments from AX2012 into Outlook. This has always been a client side call to Outlook which causes problems if you deploy the AX Client on a remote desktop server as Outlook will also have to be deployed there for the sync to work.

In AX2012 R3 CU8 that was just released there is a new feature that allows you to setup the sync to be with Exchange server and avoid the sync to Outlook. The sync is now handled via a web services to Exchange. This is a walk through of that the feature looks like and the setup.

It’s important to note there is a manual setup in getting this setup as noted in the KB2984369 you need to download the Microsoft Exchange Web Services Managed API 2.0. You will see what I mean in the above video.



13 responses to “Exchange Server sync in AX2012 R3 CU8

  1. Is there any dependency on a specific version of Exchange, or will the integration work with both Exchange 2010 and 2013? Many thanks!


      • Hi Lachlan

        Many thanks for the response… I did some investigation using Fiddler to check the SOAP requests / responses, and it appears that the required version is being specified as Exchange 2013 (my understanding is that this is the case with 2.0 of the API unless otherwise specified in the service call). I’ve opened a Premier Support case so that it can be confirmed officially whether this is the case.




  2. AX2012R3 CU8 isn’t compatible with Exchange 2007 or 2010, however there’s a hotfix to resolve this, and this hotfix is also rolled up into CU9. 🙂


  3. Hi Lachlan,

    thanks for the post. you saved my day. that was exactly the kind of instruction i needed. excellent video, covers everything one needs to know.

    I tried to set up Exchange Sync on the AX2012R3 CU9v2 VM but permanently ran into the CLRObject issue. So here’s how i got it to work:

    1. VMs A and B Need to be up and running
    2. the dll (Version 2.1) are already in the Exchange folder and need to be copied to the AX Client folder
    3. the binding to the Exchange is missing and needs to be set.
    4. Exchange Version in Setup needs to be changed to Exchange2013
    5. Login must be specified as and cannot be contoso\alicia




    • Hi Kevin.
      This is a server side API to talk to Exchange server. Your Outlook clients would be connect to Exchange. AX uses the EWS API to talk to the server instead of going through Outlook on the client side. So the question is more are you also using hosted Exchange, Exchange Online with your Outlook. I don’t believe it is covered in the system requirements support statement so you might want to log a support case to get it clarified.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s