ALM & CI/CD

From commit to production, without manual steps.

Source control, branching and automated pipelines for Dynamics 365 and the Power Platform, so every release is repeatable and every change is traceable.

Built onAzure DevOpsPower Platform Build ToolsPower Platform CLI

Sound familiar?

Solutions are exported by hand and imported into production on a Friday evening.

Nobody knows exactly which version is running in which environment.

A fix in production gets overwritten by the next release.

Works with what you have

Every change traced. Every release repeatable.

Changes start in a developer environment and go through Git and a pull request, never straight into production. From there, one pipeline builds, checks and promotes the same managed solution through every environment.

Where changes start

  • Developer environments

    One per developer or feature

  • Git in Azure Repos

    The single source of truth

  • Pull requests and reviews

    Every change reviewed before merge

What I implement

Branching and release strategy

Azure DevOps Pipelines

BuildSolution checkerManaged solutionsApprovalsEnvironment variables

Your environments

  • Development

    Unmanaged, where the team builds

  • Test

    Automated and functional tests

  • Acceptance

    Sign-off by the business

  • Production

    Managed solutions only

Infrastructure as code (Terraform / ARM) · service connections · full audit trail

What I deliver

A branching strategy

A Git branching and release strategy that matches your team size and release rhythm.

Automated pipelines

Azure DevOps pipelines that build, check and deploy managed solutions to every environment.

Environments as code

Environment variables, connection references and Azure resources defined in code, not clicked together.

A framework the team builds on

A plugin framework and coding standards so new developers are productive from day one.

Where I've done this

At Savaco I designed the branching and release strategy and built the release pipelines in Azure DevOps. At AG Insurance I set up and maintained the CI/CD pipelines for automated deployments.

More about me

How I work

  1. 01

    Discover

    Understand your processes, data and goals before a single line of code is written.

  2. 02

    Design

    Architect a solution that fits the platform: configuration first, code where it counts.

  3. 03

    Build

    Deliver in short iterations with automated tests and source-controlled solutions.

  4. 04

    Deliver

    Ship through CI/CD pipelines, document, and hand over a solution your team can own.

Go deeper

The technical guides behind this solution.

Related articles

Let's talk about your project

A short call is usually enough to see where the quick wins are and what a realistic plan looks like.