Do you use Azure DevOps Pipelines with your Dynamics solutions?

Last updated by TiagoAraujo over 3 years ago.See history

Are you still managing your Dynamics solution changes manually? Manually exporting and importing solutions across environments? Manually exporting unmanaged solutions to commit to source control. If so, read on, because there is a better way!

Dynamics (and model-driven Power Apps) use solution files to store and apply changes across environments. Using the Power Platform Build Tools for Azure DevOps will let automate manual tasks like:

  • Exporting unmanaged solutions and committing to source control
  • Generating managed solutions for use in downstream environments such as Testing and Production
  • Deploying solutions to downstream environments
  • Provisioning or de-provisioning environments

Want to learn more?

Check out the guide on GitHub. The guide demonstrates:

  1. Configuring Azure DevOps
  2. Build the 'Capture Pipeline' (Export solution)
  3. Build the 'Build Pipeline' (Generate Build Artifact)
  4. Build the 'Release Pipeline' (Deploy to Production)

sample azure 1
Figure: Sample Azure Pipeline to export solution and commit to source control

sample azure 2
Figure: Sample Azure Pipeline to create a managed solution from source

sample azure 3
Figure: Sample Release Pipeline to deploy the managed solution to production

We open source. Powered by GitHub