Episode Details

Rolling out a Power Platform solution shouldn’t mean dreading the next manual deployment. In this episode, I walk through a step‑by‑step CI/CD setup with Azure DevOps so you can move from “export/import and hope” to reliable, automated pipelines that actually respect how Power Apps, Power Automate, and Dataverse work in real environments. We start with the messy reality behind solution exports—half‑captured configuration, missing environment variables, and broken connection references—and show why your ZIP file is not the complete story your team assumes it is.

From there, we break down what really lives inside a solution file and what still needs explicit handling. You’ll hear how Dataverse tables, apps, and flows travel with the package, while environment variables and connection references behave more like placeholders that must be mapped and filled on every import. Using stories like the healthcare team whose intake app “worked in dev but died in test,” we highlight how untracked variables, misaligned connection references, and inconsistent solution structure quietly sabotage deployments and fuel those late‑night fix sessions.

Then we switch to pipeline design. We look at why copy‑pasted YAML from generic samples usually collapses under real‑world constraints: missing environment names, no parameterization, no secure handling of credentials, and service connections that don’t have the right permissions. You’ll learn how to build pipelines that understand Power Platform’s quirks—separating export, validation, import, and configuration steps; using variables and Key Vault for environment‑specific values; and wiring Azure DevOps service connections so your pipeline can interact with the right environments without exposing secrets.

By the end, CI/CD for Power Platform will feel less like a fragile script and more like an intentional part of your architecture. You’ll walk away with a mental model where solutions are structured deliberately, environment variables and connection references are first‑class citizens, and Azure DevOps pipelines become boring, dependable infrastructure that ships your changes the same way, every time.

WHAT YOU LEARN

• Why exported Power Platform solutions often miss critical pieces like environment variables and connection references.
• What actually lives inside the solution package—and what must be configured or mapped at deployment time.
• How poor solution structure and untracked dependencies turn imports into broken apps and flows.
• Why generic Azure DevOps YAML samples fail for Power Platform and how to design pipelines that handle env‑specific config and credentials.
• How service connections, variables, and Key Vault fit together in a robust CI/CD setup for Power Platform.

CORE INSIGHT

The core insight of this episode is that reliable CI/CD for Power Platform doesn’t come from a clever pipeline script—it comes from treating solutions, environment variables, connection references, and DevOps pipelines as one integrated system. When you design all f