Power Platform: Setup Pipeline Approvals

Key insights

• Power Platform pipelines: Use pipelines to move solutions between environments and add checkpoints so deployments stop for review before reaching the next stage.
  
• Power Platform admin center: Enable "Require approval before deploying to this stage" on the stage settings, add approvers, set minimum approvals and timeouts, then save the stage configuration.
  
• Power Automate flow: Build a cloud flow to handle custom approvals. Start with the OnApprovalStarted trigger, send the approval request, then write the decision back to the pipeline record.
  
• Dataverse: Read and update deployment records in Dataverse (for example, Deployment Stage Runs) to pass context between the pipeline and your approval flow.
  
• Service principal vs stage owner: Choose the identity for delegated deployments and make sure that identity has the required environment and pipeline permissions.
  
• Approval gates and ALM best practices: Use approval gates to protect production, enforce minimum approvers, test flows in a non-production environment, and log decisions for audits.
  

Griffin Lickfeldt (Citizen Developer) published a clear walkthrough showing how to set up pipeline approvals inside the Power Platform. In the video, he guides viewers step by step through building the necessary cloud flow and linking it to a pipeline stage, so admins can require sign-off before deployments move forward. Moreover, the presentation aims to help people who have not previously built Power Automate flows by breaking the process into manageable actions. As a result, teams can add governance checkpoints without heavy investments in external DevOps tools.

Overview of the video

The video opens by explaining why teams need approval gates and then defines how pipelines in the Power Platform bring ALM capabilities into the service. After that, Griffin demonstrates creating a cloud flow and shows the specific triggers and actions used to pause and resume a pipeline. He emphasizes the use of the OnApprovalStarted trigger so the flow reacts to the pipeline lifecycle. Consequently, viewers see both the administrative stage setup and the flow logic that enforces approvals.

Griffin also walks through practical examples, including creating conditions and a switch control to route approvals. He points out common pitfalls, for instance missing permissions or incorrect stage identity settings, and shows how to inspect the Dataverse record that stores deployment stage context. Furthermore, the video covers how to record approval decisions back into Dataverse so the pipeline can continue or stop cleanly. Thus, the walkthrough links pipeline configuration with the cloud flow in a reproducible way.

Step-by-step setup explained

First, Griffin instructs viewers to open the Power Platform admin center and mark the stage to “require approval” so manual gates exist at the right points in the release path. Next, he builds a cloud flow that listens for the pipeline event and sends an approval request to the designated approver or group. Then he demonstrates reading the deployment stage context from Dataverse to provide meaningful details in the approval request. Finally, he writes the decision back into the system so the pipeline can move forward or halt based on that outcome.

Along the way, the video shows configuration options such as minimum approvers, self-approval rules, and timeout behavior, which help tailor the gate to an organization’s risk tolerance. Additionally, Griffin explains selecting the stage identity — whether to use a service principal or the stage owner — and why that choice affects the flow’s permissions. He also points out how to test the whole flow by triggering a pipeline run and watching the approval lifecycle in action. Consequently, administrators gain a repeatable approach to connect pipeline events to automation safely.

Technical tradeoffs and governance challenges

Implementing approval flows brings clear governance benefits, but Griffin highlights tradeoffs between simplicity and flexibility. For instance, the built-in stage-level approver list is easy to configure, yet custom Power Automate flows deliver richer decision logic and notifications. However, the custom route introduces operational overhead because flows must be maintained, tested, and granted correct Dataverse permissions. Therefore, teams must balance immediate ease of setup with long-term maintenance costs.

Another tradeoff concerns identity and delegated deployments: using a service principal enables automated, noninteractive deployments, while a stage owner approach leverages individual identities for clearer audit trails. Yet service principals can simplify scriptable deployments at scale, and so choosing between them depends on governance needs and the organization’s identity model. Moreover, reliance on Dataverse for event records centralizes data but also creates a single point that administrators must monitor. In short, the technical choices affect security, auditability, and operational complexity.

Practical tips from the walkthrough

Griffin recommends starting with a small set of approval rules and expanding them as teams gain confidence, thus reducing initial friction. He also suggests documenting the flow design and permission model so future admins understand why a flow exists and how it interacts with pipeline stages. In addition, testing flows in a nonproduction environment helps catch permission or logic errors before they block real deployments. Consequently, these pragmatic steps reduce the risk of accidental downtime when approvals are enforced.

He further advises using clear approval messages that include deployment context and a link to the pipeline run so approvers can make fast decisions. Griffin notes that organizations should think about exception paths, such as emergency or rollback scenarios, and how those will be authorized. Finally, he encourages teams to monitor approval timeouts and to align timeout policies with release windows to avoid disrupting planned deliveries. As a result, the approval process becomes both protective and predictable.

Why this matters for teams

Overall, the video makes a strong case that adding approval gates to Power Platform pipelines strengthens governance without forcing teams into external CI/CD tools. Because the pattern uses native pipeline events and cloud flows, it remains accessible to admins and citizen developers who already work in the platform. At the same time, organizations must accept the tradeoffs that come with custom flows, such as maintenance and permission management. Nevertheless, when implemented thoughtfully, the approach improves control and visibility across the application lifecycle.

In conclusion, Griffin Lickfeldt’s walkthrough offers a practical, stepwise method for bringing approval checks into pipeline deployments. Therefore, teams that follow his guidance can achieve a balance between rapid delivery and environment protection. Moreover, the video provides enough detail to help both new and experienced administrators implement a reliable approval process. Consequently, the walkthrough is a useful resource for organizations aiming to tighten ALM practices within the Power Platform.

• 00:00 - Intro
• 00:37 - What are Pipelines
• 02:14 - Making the Flow
• 07:24 - Switch Control
• 09:43 - Making the Approval
• 13:57 - Setting Up the Condition

Keywords

Power Platform pipeline approvals,Configure pipeline approvals Power Platform,Set up approval gates Power Platform,Power Automate deployment approvals,Solution pipeline approvals Power Platform,ALM pipeline approvals Power Platform,Azure DevOps pipeline approvals Power Platform,Power Apps release approvals