Power Platform ALM GitHub DevOps
Power Platform Pipelines with GitHub Integration
Environment Architecture
The solution spans multiple managed and unmanaged instances:
- DEV — Unmanaged instance where teams actively develop configurations
- Artifact — Managed instance serving as deployment target from development
- BUILD — Maintained by ALM processes with minimal manual intervention
- QA/UAT — Managed instances for testing consolidated solutions
- PROD — Production environment
Two-Pipeline Approach
Pipeline 1: Dev to Artifact
Downloads unmanaged feature solutions, commits them to repository branches, packs the solution, and deploys to BUILD environment. A Power Automate workflow then merges components into a consolidated solution using AddSolutionComponent actions.
Pipeline 2: Build to QA/UAT/PROD
Moves managed consolidated solutions between environments. When a newer version of the consolidated solution is ready for testing, it is deployed to QA.
The process includes verification checks ensuring deployments target appropriate environments, with Power Automate intercepting deployment requests and triggering GitHub Actions for unpacking and committing solution versions.
Key Design Principles
- Automation first — Minimize manual intervention in the release process
- Security — Service principal validation at each stage
- Solution integrity — Managed solutions maintain component ownership across environments
- Traceability — Every solution version committed to Git with full history