Customer case study
Embedded Power Platform Governance at Sandpiper Manufacturing
Engagement summary
Sandpiper Manufacturing added one full-time Power Platform developer and governance lead from MS Dynamics Guys to its IT team from January to June 2024. The specialist designed environments, data loss prevention policies and deployment pipelines for an estate of 41 apps and 96 flows. Sandpiper accepted the work on 21 June, and its June deployment record shows that all production apps deployed through managed pipelines.
Engagement Facts
| Field | Detail |
|---|---|
| Client | Sandpiper Manufacturing, 560 employees |
| Industry | Precision engineering |
| Client and delivery locations | Coventry, UK / Lisbon |
| Product | Power Platform (Power Apps, Power Automate, Dataverse), Microsoft Dynamics 365 Finance |
| Roles | 1 Power Platform developer and governance lead (full-time) |
| Engagement dates | 22 Jan – 28 Jun 2024 |
| Overlap | 7 hours GMT |
| Reporting line | Client IT Manager |
Why the Client Added Capacity
Sandpiper's citizen development programme had grown across Power Apps, Power Automate and Dataverse without a shared environment strategy or an ownership register. The client had recorded two production outages in the previous quarter. Its IT Manager set the priorities for governance and remediation.
Decision Rights
| Decision | Owner |
|---|---|
| Governance design | Specialist proposes; IT Manager approves |
| Environment strategy | IT Manager |
| App and flow acceptance | Operations Director |
| Deployment approval | IT Manager |
Work Delivered
The specialist put four environments and data loss prevention policies in place and documented ownership across the inherited estate. They created three deployment pipelines and remediated 12 priority apps for redeployment through managed solutions. The IT Manager approved the governance design and deployments, and the Operations Director accepted the app and flow work.
| Role | Assignment | Accepted output | Reviewer | Approver |
|---|---|---|---|---|
| PP developer/governance | Environment and DLP design | 4 environments; DLP policies; ownership register for 41 apps and 96 flows | Client IT Manager | IT Manager |
| PP developer/governance | Deployment pipelines and remediation | 3 pipelines; 12 priority apps remediated and redeployed via managed solutions | Client IT Manager | Operations Director |
Outcomes
By June, Sandpiper's ownership register showed a named owner for all 41 apps. Its review record showed error handling on all 96 flows, up from 18.
| Measure | Baseline | Result | Window | Source |
|---|---|---|---|---|
| Apps deployed via managed pipelines | 0% | 100% of production apps | Jun 2024 | Client deployment record |
| Production outages | 2 in Q4 2023 | 0 in Q1–Q2 2024 | Jan–Jun 2024 | Client incident log |
| Apps with documented ownership | 0 of 41 | 41 of 41 | Jun 2024 | Client ownership register |
| Flows with error handling | 18 of 96 | 96 of 96 | Jun 2024 | Client review record |
| First accepted governance artifact | — | 9 business days | Onboarding | Client ticket record |
Client perspective
“We had shadow IT and no ownership. Now every app has a name against it and a pipeline.”
Your next step
Discuss the capacity your team needs
Share the application, workstream and specialist allocation you need. Your team can define its own backlog, acceptance and release responsibilities.