
However, Project 2016 MSI is supported for running side-by-side with the 2013 build of Office 365 ProPlus click-to-run on the same device, as the click-to-run 2013 build uses Office 2013 bits. Likewise, the 2016 build of Project Pro for Office 365 click-to-run is not compatible with Office 2016 Running side-by-side with the Wave 16 build of Office 365 ProPlus click-to-run on the same device, as the click-to-run 2016 build uses Office 2016 bits. For example, Project 2016 MSI is not supported for Side-by-Side Installation Compatibility for Project and Visio with Office MSI and Office 365 ProPlus Click-to-RunĪcross products, side-by-side installations of the latest versions of Office MSI (traditional, on-premises Windows installation) and Click-to-Run (Office 365 installation) bits are not supported by Microsoft. It's not a program he uses often, so I may have to set up a VM or second computer that he can use when he needs to run Project that does not have a 365 installation on it, but I'd like to avoid that if possible. I did see that some users had reported issues between the two pieces of software a while back, but I would have assumed (or, at least hoped) that it had been resolved at this point, since those posts were from a couple of years ago, and nobody reported the To reactivate it using the key purchased from Microsoft, it tells me that the key is not valid. But, my whole company upgraded to Office 365 a few months back, and now, when he tries to use Project, it tells him that the product is not activated, and when I try I am trying to support a user who had an older version of Office and Project working fine.


Are there any known, out-standing, compatibility issues between the stand alone version of Project 2013 and Office 365 in a Windows 7 environment?
