Following the spirit of low code development, we wanted also wanted to align our CI/CD to reflect the same concept. As a result, we decided to utilize Microsoft Power Platform Pipelines including the relatively new Git integration feature. The over all business value using these technologies was that it provided us with a easily maintainable ALM solution, while also ensuring that our solution would be compliant, secure and protect privacy. The git integration with our managed solution also provided the transparency between the developers to validate any changes that were made, and do code review.

To begin, we created a dedicated production environment for hosting our pipeline app:

Next, we installed the installed the Power Platform Pipelines Model-Driven App and started configuring our pipeline:

NB. We eventually also configured the production environment and added this to our pipeline.

Once the pipeline was all configured we could verify by checking our solution. As illustrated below, we could see that our solution was connected to the pipeline and that we could initiate the first deployment to our TEST enviroment.

While inspecting the sitemap on the left, we could also see that the source control menu item also was available. At first glance we could see the change log:

Lastly, in Azure DevOps we created a new project with branches related to the respective environments:

To summarize, this approach enabled us to quite effectively setup a simple ALM solution and process to maintain control over our components and changes. It was also an appropriate approach in order to gain more knowledge about some of the new features that were quite recently made generally available.