CI/CD for Azure Power Platform

Application Insights
Azure DevOps
Web Apps
Power Apps
Repos

Solution Idea

If you'd like to see us expand this article with more information, such as potential use cases, alternative services, implementation considerations, or pricing guidance, let us know with GitHub Feedback!

Learn how to create a CI/CD pipeline to manage your Power Platform Application lifecycle using Azure DevOps.

Architecture

Architecture diagram Download an SVG of this architecture.

Data flow

  1. The solution is updated, which triggers the build pipeline.
  2. Continuous integration exports the solution from the development environment and commits files to Azure Repos.
  3. Continuous integration builds a managed solution, runs tests, and creates a build artifact.
  4. You deploy to your build/test environment.
  5. Continuous deployment runs tests and orchestrates the deployment of the managed solution to the target environments.
  6. You deploy to the production environment.
  7. Application Insights collects and analyzes health, performance, and usage data.
  8. You review the health, performance, and usage information.
  9. You update your backlog item(s), as required.

Components

  • Power Apps: Microsoft Power Apps is a low-code app-building platform.
  • Azure DevOps: Azure DevOps can build, test, and deploy a solution in any language, to any cloud or on-premises.
  • Azure Repos: Azure Repos provides cloud-hosted private Git repos.
  • Azure Application Insights: Application Insights is a feature of Azure Monitor, which you can use to monitor your live applications.

Pricing

Next steps

Additional Power Apps architectures:

Additional CI/CD architectures: