I would like to put in place a platform for the support of efficient Dynamics (Online) based development. Part of that (at least in my view) is the ability to observe a level of integrity around configuration management. So, in short: I want to be able to recreate an environment in it's entirety according to a rigorous configuration, e.g.,
For the purposes of complete control, my initial feeling was to go with a completely locally managed instance of Dynamics, mimicking the online version (since ultimately, for our purposes, the production application will always be based on the online version), so, along the lines of what Mohamed Radwan has detailed here (admittedly somewhat dated), provide some automated means of setting up a completely standalone and fresh install of Dynamics, and populate base data. I have subsequently become aware of the fact that this does not seem practical since (not exhaustive, but at least illustrative):
Now as much as I understand the motivation for the third point above, it really doesn't make life much easier for those of us who want to push the envelope in respect of the good ideas around DevOps and the automation of infrastructure setup and teardown (ala tools such as Puppet and Docker). Online per se should not be an inhibitor to infrastructure automation efforts, but in the Dynamics world, I can't seem to find any support for the same. At least with an on-prem solution, I have the option of automating everything, even if it means building the tool-suite myself.
So I guess my question is: what is Microsoft's answer to being able to implement a DevOps platform for Dynamics? I'm not looking for unsupported third-party solutions that are likely to be scuppered the second Microsoft decide to change how they do things, but rather: from the horses mouth, how do the Dynamics 365 team recommend we do DevOps?
*This post is locked for comments
Thank you Adrian for your response—the most hopeful option then is to follow the efforts of Marc and his team.
Hi Lambda,
Microsoft have not standardised the implementation of a DevOps platform for Microsoft Dynamics, but one of their employees Marc Schweigert created a GitHub project to help Dynamics 365 for Customer Engagement solution builders understand and accelerate their implementation of DevOps practices with Dynamics 365 for Customer Engagement and Visual Studio Team Services (VSTS). Marc and his team use community projects such as the xRM CI Framework to automate the build and deployment of his CRM Solutions and SparkleXrm to deploy Plugins, Workflow Activities, and Web Resources. A similar approach may work well for you.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156