Power Apps Consultants Canada

Building CRM Solutions with DevOps

Deploying Dynamics 365 CRM with Azure DevOps

We use Azure DevOps to manage the optimal balance of creative designs and project execution to ensure that our clients needs are met. Understanding the mental model of "builds" and" releases" can greatly enhance your Microsoft Dynamics 365 CRM project's project management and deployment processes.

The solution ZIP file is our compiled code

In traditional software development, developers compile their code into a deployable package. However, in the world of Microsoft Dynamics 365 CRM, we have a different approach. We create a solution file that contains all the components we want to release, deploy, or push to another environment, and then we export it as a ZIP file. This exported ZIP file is our equivalent of a compiled build.

Creating your artifacts

So what exactly is a "build" in the context of Dynamics 365 CRM? Think of it as a packaged solution with a version. It represents the code as it exists at a specific moment in time. When we create a build, we generate a solution ZIP file with a version number. This ZIP file is what we call an "artifact." An artifact is simply a file or group of files packaged together for deployment to another environment.

Temporarily storing your ZIP in the cloud

When you're working on your local computer, you might export the solution ZIP file (your build artifact) to your desktop or a specific folder on your hard drive. However, if you are utilizing Microsoft Azure DevOps in the cloud, you'll find the "artifacts" section in DevOps, where you can place the ZIP file into a staging folder.

Build and back-up to the repository

In Azure DevOps, we utilize "pipelines" to define a flow that produces our artifact (the solution ZIP file) and stores it in the staging area. It's important to note that the unversioned and undeployed solution components are what we store in the repository. The versioned and compiled solution, packaged as a ZIP file, is what goes into the "artifacts" section of DevOps.

Using releases for environment deployments

But how do we deploy these artifacts to different environments? This is where the concept of "release" comes into play. Just as we use "pipelines" to produce "artifacts", we use" release" to "deploy" a package of "artifacts". In our case, this package typically consists of a single ZIP file. We can push this package to various environments like the Test or Production environment, while all the configuration work is done in the Development environment.

About Purely CRM

For close to a decade our Purely CRM team has been laser-like focused on delivering CRM solutions built solely on Microsoft Dynamics 365 CRM, combined with Power Apps and the Microsoft Power Platform. We’ve expanded our team immensely in the past years to help better serve our clients and partners. Most recently we merged with Endeavour Solutions, a top Microsoft ERP, CRM, and Cloud consulting firm to further expand our talented team of CRM consultants.

Our core focus is on large mid-market and enterprise CRM Design, Development projects, Staff Augmentation, and CRM Support. When needed we can also tap upon our peers at Endeavour for Dynamics 365 Business Central ERP to provide an All-in-One Cloud ERP-CRM.  We provide services to clients Coast to Coast across the United States and Canada. We do not use resources overseas.

Reach out to explore our track record, rates, skills, and approach to discover how we can collaborate and drive your SUCCESS at purelycrm.com

Are You Ready To Get Started?

Let's Talk