This article is a solution idea. If you'd like us to expand the content with more information, such as potential use cases, alternative services, implementation considerations, or pricing guidance, let us know by providing GitHub feedback.
Learn how to create a CI/CD pipeline to manage your Power Platform Application lifecycle using Azure DevOps.
Download a Visio file of this architecture.
- The solution is updated, which triggers the build pipeline.
- Continuous integration exports the solution from the development environment and commits files to Azure Repos.
- Continuous integration builds a managed solution, runs tests, and creates a build artifact.
- You deploy to your build/test environment.
- Continuous deployment runs tests and orchestrates the deployment of the managed solution to the target environments.
- You deploy to the production environment.
- Application Insights collects and analyzes health, performance, and usage data.
- You review the health, performance, and usage information.
- You update your backlog item(s), as required.
- 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.
This architecture enables you to use Azure DevOps, Azure Repos, and Azure Application Insights (via Azure Monitor) to build a CI/CD (continuous integration/continuous deployment) pipeline for Microsoft Power Platform (namely Power Apps).
Potential use cases
- Applications that interact with other Microsoft 365 services.
- Employee onboarding application.
- Image processing tools.
- New user setup scenarios.
- Service request applications.
- Applications with complex entity relationships.
These considerations implement the pillars of the Azure Well-Architected Framework, which is a set of guiding tenets that can be used to improve the quality of a workload. For more information, see Microsoft Azure Well-Architected Framework.
Cost optimization is about looking at ways to reduce unnecessary expenses and improve operational efficiencies. For more information, see Overview of the cost optimization pillar.
This article is maintained by Microsoft. It was originally written by the following contributors.
- Sarah Parkes | Cloud Solution Architect
- Application lifecycle management with Microsoft Power Platform
- Microsoft Power Platform Build Tools for Azure DevOps
- Microsoft Power Platform Build Tools tasks
- Azure DevOps
Additional Power Apps architectures:
Additional CI/CD architectures:
- CI/CD for Azure VMs
- Immutable infrastructure CI/CD using Jenkins and Terraform on Azure virtual architecture
- Gridwich CI/CD pipeline
- CI/CD pipeline for container-based workloads
- CI/CD for containers
- Container CI/CD using Jenkins and Kubernetes on Azure Kubernetes Service (AKS)
- Design a CI/CD pipeline using Azure DevOps
- CI/CD for Azure Web Apps
- Java CI/CD using Jenkins and Azure Web Apps
- End-to-end governance in Azure when using CI/CD
- DevSecOps in GitHub