POWER AUTOMATE — PROJECT 7🔴 EXPERT
ProcurementFlowSuite governed as one Solution with a Power Platform pipeline. Static reference only.
Export managed solution v1.3
→
Solution Checker gate
→
Deploy to Test
→
Smoke test run
→
Approval gate
→
Deploy to Prod ✔
Dev
Solution v1.3 — unmanaged
Personal connections OK
Test
Solution v1.3 — managed
Smoke-tested automatically
Prod (Managed Environment)
Solution v1.3 — managed
Runs as Service Principal
DLP policy enforced

Connection references & environment variables

SharePoint connectionref: SP_Conn_ProcurementSuite
SQL Server connectionref: SQL_ERP_Conn
API base URLenv var — differs per environment
Approval thresholdenv var — Dev: 100, Prod: 2500

Licensing decision — this suite

Invoice pipeline flowProcess license — shared infra
Personal notification flow (1 user)Premium user license
Admin inventory viewflow deps + connections visible
What this shows: the exact same solution and flow logic gets promoted Dev → Test → Prod through a gated pipeline with zero code changes — only the connection references and environment variable values differ per environment. Production runs under a Service Principal, not a personal account, and the licensing decision per flow is made deliberately rather than defaulted.