Build CI/CD with Azure for Microsoft Power Platform

Azure Monitor
Azure DevOps
Azure App Service
Power Apps
Azure Repos

Solution ideas

This article describes a solution idea. Your cloud architect can use this guidance to help visualize the major components for a typical implementation of this architecture. Use this article as a starting point to design a well-architected solution that aligns with your workload's specific requirements.

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

Architecture

Diagram showing continuous integration and continuous deployment pipeline to manage your Power Platform Application.

Download a Visio file of this architecture.

Dataflow

  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.

Scenario details

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.

Considerations

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

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.

Contributors

This article is maintained by Microsoft. It was originally written by the following contributors.

Principal author:

Next steps

Additional Power Apps architectures:

Additional CI/CD architectures: