Dynamics AX 2012 R2: Office, SharePoint, and Lync versions supported

I just completed my Office Interop presentation at Convergence in New Orleans and I had a number of people asking about version support for Office and SharePoint since I demonstrated in Microsoft Office 2013. I didn't make a specific mention of Microsoft Office 2010 but, yes, Office 2010 is supported as well as Office 2013.

High Level
At a high level, Dynamics AX 2012 R2 supports Office 2010 and 2013, SharePoint 2010 and 2013 (*not for EP yet), and Lync 2010 and 2013.

Office Add-ins
The Dynamics AX 2012 R2 Office Add-ins for Excel and Word can run and are supported in Office 2010 and 2013. Office 2007 SP3 also works at this time but is not officially supported and may encounter issues in the future.
The documents generated and workbooks exported from Dynamics AX 2012 R2 can also be viewed in the Office 365 web versions of Excel and Word, however the Add-ins only run in the local versions of Excel and Word.

Exports, generated documents, attachments, and templates can be exported to, sent to, placed in, and hosted on document libraries and folders within SharePoint 2010, SharePoint 2013, and SharePoint Onlne.

Dynamics AX 2012 R2 works with Lync 2010 client and Lync 2013 client.


 *Enterprise Portal support for SharePoint 2013 is still under development. A hotfix will be available soon.

Comments (13)

  1. Richard Shepherd says:

    Looking for guidance on integrating on-prem AX 2012 R2 with O365 Outlook.  Maybe a comparison of features/functionality as compared to on-prem Outlook.  

    Also, curious about best practice configuration on any of the above.  We have on-prem Outlook right now.  Seems that we need to have Outlook run on the same machine as AX client to get some features (e.g. calendar/contact sync).  That's possible either by running remote desktop or putting AX on the local client.  Trade-offs in either case.  

    Want to move to O365 though.  

    The ideal setup for me would be O365 Outlook c/w on-prem AX.  Next best, Outlook on the local desktop, AX remote desktop.  Either of those possible without losing functionality?

    Thanks so much.

  2. Chris Garty says:

    You are correct in your assumption that Outlook needs to be running on the same machine as the AX Client.

    O365 Outlook isn't supported for Dynamics AX 2012 calendar/contact sync. And unfortunately "local Outlook + remote AX Client" is not supported either.

  3. Martin Abrle (Axperience AG) says:

    however, http://www.axperience.ch provides a module to synchronize directly with Exchange (off the premises, Outlook 365 or RDP Ax client + local outlook)

  4. Richard Shepherd says:

    So, if I'm accessing my O365 mailbox via a desktop Outlook client, and the client is on the same machine as AX, will that work?  Or is this just a limitation of O365?  That wouldn't really be functionally different than desktop Outlook connecting to on prem Exchange right?

  5. Chris Garty says:

    Richard, that is correct. Dynamics AX will talk to the local Outlook application to get the information, so as long as you get the information in into Outlook then it will be available to Dynamics AX.

  6. Rajan says:

    Chris – What you mean by "O365 Outlook isn't supported for Dynamics AX 2012 calendar/contact sync. And unfortunately "local Outlook + remote AX Client" is not supported either." ??

    Are you saying having MSExchange (Office365) + On-Prem MS Office(Outlook) is not a supported combination? We plan to design the solution with local MSOffice/Outlook instance for the AX users but the mailbox would reside in the cloud(Office 365- Exchange) isn't it a supportable design? Please clarify

  7. Chris Garty says:

    The Dynamics AX Client and the Outlook client need to be running on the same machine.

    The location of the mailbox doesn't matter, so it can be local, remote, or in the cloud (O365).

    I hope that clears it up!

  8. Richard Shepherd says:

    Chris – Will it work if the Outlook client and the AX client are both running on the same virtual machine instance under terminal services?  Or does it have to be the same physical machine?

  9. Chris Garty says:

    Yes, running in the same virtual machine is the same (as far as this scenario is concerned) as running in the same physical machine.

  10. Jolene Bartlett says:

    Chris – We are in process of upgrading from DAX2009 to 2012 and I have questions on "dependencies".  Is the out-of-the-box DAX2012 application dependent on (or to) Sharepoint 2010 or 2013?  Does Enterprise Portal work (in DAX 2012) if we have Sharepoint 2007 & have not yet upgraded our Sharepoint product?  Thank you for any clarity you can give in this area.

  11. Jesper Arent says:

    I am having trouble synchronizing document templates from a SharePoint library inside the Document types Template library in AX. I keep getting an error saying, that no templates was found in the SharePoint library, when O choose synchronize in the Document types screen in AX.

    Any help on how to make the document templates available in AXX?

    I have put several types of documents in the SharePoint template library, and AX can find the document library under the Document Templates section, but the templates are not shown so I can activate them… Any help is appreciated

  12. Chris Garty says:


    Dynamics AX 2012 uses SharePoint 2010. It will shortly add support for SharePoint 2013 as well.

  13. Chris Garty says:


    The document templates need to be built using the Excel Add-in or Word Add-in. If they don't have any Dynamics AX fields bound inside them using the Add-in then they will be ignored.

    Did you use the Add-in to build those templates?

Skip to main content