Solution Import Approval Gate

Overview

The Solution Import Approval Gate is an Advanced-level governance flow that acts as a post-import checkpoint for Dataverse solution deployments. When a new solution is imported into the target environment, this flow automatically triggers, gathers solution metadata (name, version, component count, importing user), and routes a formal approval request to the COE lead. On approval, a changelog notification is posted to Teams. On rejection, the imported solution is automatically deleted and the developer receives an email with the rejection reason and guidance for resubmission.

Use Case

Organizations with multiple makers deploying solutions to shared or production environments need a governance mechanism to prevent unauthorized or untested solutions from persisting. This flow provides that gate — every solution import is reviewed before it remains in the environment. It enforces the principle that no solution should exist in production without explicit COE approval, and gives the COE lead full context (solution name, version, component count, who imported it) to make an informed decision.

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Set Teams channel

Update flowlibs_TeamsGroupId and flowlibs_TeamsChannelId to your governance Teams group and channel.

Set COE Lead

Update flowlibs_COELeadEmail to the person who should approve/reject solution imports.

Set notification recipient

Update flowlibs_AdminNotificationEmail to the team or individual who should receive rejection notices.

Authorize connections

Open the flow in the designer and authorize all four connections (Dataverse, Approvals, Teams, Outlook).

Turn on

Toggle the flow from Off to On — it will begin monitoring solution imports immediately.

Scope control

The Dataverse trigger scope is Organization-wide. To limit to specific publishers or solution prefixes, add a Condition action after the trigger to filter by uniquename prefix.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

length(body('Get_Solution_Component_Count')?['value'])

body('Start_Import_Approval')?['outcome']

coalesce(triggerOutputs()?['body/friendlyname'], 'N/A')

coalesce(body('Start_Import_Approval')?['responses/0/comments'], 'No reason provided')