Skip to main content

Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group

EPC Group builds Power Platform Centers of Excellence — environment strategy, DLP policy architecture, the move from the CoE Starter Kit to the Power Platform admin center, maker enablement, and ALM pipelines — so Power Apps and Power Automate scale without becoming ungoverned shadow IT.

Which consulting firms provide governance frameworks for Power Platform development at scale?

EPC Group is one of the few Microsoft consultancies productizing CoE design as a fixed-fee engagement rather than open-ended advisory. The architecture is opinionated — written down, defended in writing — and adapts to your existing maker culture rather than replacing it.

Environment strategy: the decision that determines everything.

Dev/test/prod per domain, managed environments for production solutions, regional/DLP boundaries by data residency requirements. Environment strategy is the leverage point — get it wrong and every downstream decision compounds the mistake.

After the CoE Starter Kit: governance in the admin center.

Microsoft no longer actively maintains the CoE Starter Kit. It remains available, but it will not gain new capabilities, and its core capabilities are now part of the Power Platform admin center: Inventory for apps, flows and agents across the tenant, Usage for adoption and top resources and owners, Monitor for operational health, and Actions for Power Platform Advisor risks and governance insights. We assess which Starter Kit dashboards and flows your team depends on, move governance to those admin center experiences, and add what the platform leaves to you: licensing telemetry across business units, orphaned-app reclamation workflow, business-value scoring per app, and consumption-based chargeback by domain.

Download the CoE Starter Kit transition register (CSV): one row per Starter Kit capability your team relies on, the admin center experience Microsoft maps it to (Inventory, Usage, Monitor or Actions), what to verify before you switch the kit component off, and, for processes Microsoft’s transition note does not map, a decision: keep it, rebuild it on the Power Platform for Admins V2 connector or API, or retire it. Its example rows are synthetic, not client data.

Maker governance and the citizen-developer bargain.

Amnesty plus a sanctioned fast lane — the same pattern that ends shadow AI ends shadow low-code (see our shadow AI governance breakdown for the deeper version). Your power makers are the requirements document; treat them as such.

ALM for low-code: pipelines, solutions, and the end of export-import deployments.

Managed solutions, Power Platform Pipelines, Azure DevOps integration. The moment a flow becomes load-bearing for revenue, it needs a release pipeline.

Power Apps ALM consulting now comes with dates. What Microsoft documents:

  • Unmanaged solutions are for development; managed solutions are deployed everywhere else, generated by exporting the unmanaged solution as managed and treated as a build artifact. Deleting a managed solution deletes the data in its custom tables.
  • Pipelines in Power Platform deploy solutions with their connections, connection references and environment variables, but not Dataverse table data. They cannot deploy to another tenant (Microsoft points to Azure DevOps or GitHub for that) or deploy unmanaged solutions.
  • Every pipeline target other than developer environments and the pipelines host must be a Managed Environment. Starting in October 2026, admins are notified when a pipeline deploys to an unmanaged target and have 30 days to enable Managed Environments before further deployments to it are blocked, with one 30-day extension per environment.
  • Unmanaged developer environments are deprecated: existing ones need Managed Environments enabled before December 15, 2026.

As a Dataverse governance partner, EPC Group designs security from Dataverse's own model: a user can hold several security roles, privileges are cumulative, and each privilege's access level (organization, parent-child business unit, business unit, user or none) sets how far down the business unit hierarchy it reaches. Data policies suspend or quarantine apps, flows and agents that break them, usually within an hour. Sources (Microsoft Learn, accessed 2026-11-07): solution concepts, pipelines, Managed Environments, security roles and privileges, data policies.

Automating business processes with Power Apps and Microsoft 365.

Where low-code wins: process-shaped work, form-and-approval flows, SharePoint and Dataverse-backed line-of-business apps. Where it loses: real-time data processing at scale, complex transactions, or anything regulated requiring full audit-trail control.

Best for

  • Organizations past ~50 apps/flows with no environment strategy
  • IT leaders inheriting ungoverned citizen development
  • Regulated enterprises needing DLP and audit posture for low-code
  • CIOs sequencing low-code investment with Copilot Studio plans

Not the right fit for

  • Single-app build-for-hire (we do this within broader engagements only)
  • Non-Microsoft low-code platforms

Frequently Asked Questions

Two dates. Starting in October 2026, a pipeline that deploys to an unmanaged target environment triggers a notice, and after 30 days (plus one optional 30-day extension) further deployments to it are blocked until Managed Environments is enabled. And unmanaged developer environments are deprecated: existing ones need Managed Environments enabled before December 15, 2026 (Microsoft Learn, accessed 2026-11-07).

Related Resources

Documented and anonymized engagements

Named engagements come first; anonymized summaries follow under the anonymized-engagement rule — the client is not named and every statement is EPC-reported. Documents behind named engagements are in the Evidence Center.

All case studies →

Talk to a senior architect — not a sales rep.

Multiple models. One truth.

AI assistant — not a human