The practical guide to setting up a Microsoft Power Platform Centre of Excellence for UK organisations, covering governance structure, DLP policies, environment strategy, and how to scale beyond pilot.
Most UK organisations reach the same inflection point: Power Platform has grown organically from a few pilot apps into hundreds of flows, apps, and automations built by citizen developers across the business, with no central oversight. This is when a Power Platform Centre of Excellence (CoE) becomes essential, not optional.
What Is a Power Platform Centre of Excellence?
A CoE is not a committee or a bureaucratic overhead. It is a small team, a set of policies, and a governance framework that enables your organisation to scale Power Platform safely. The Microsoft CoE Starter Kit (available free from Microsoft) provides the tooling foundation, but the real work is designing the operating model that fits your organisation.
A well-designed CoE typically has three functions: governance and risk management (ensuring solutions are secure, compliant, and supportable), enablement (helping makers build better solutions faster), and strategy (aligning Power Platform investment with business priorities).
Step 1: Install the CoE Starter Kit
Microsoft's free CoE Starter Kit is the non-negotiable starting point. It deploys into a dedicated CoE environment and gives you:
- A complete inventory of all apps, flows, and connectors across your tenant
- Maker activity data, who is building what, and how frequently apps are used
- Compliance tracking, which apps have been reviewed and approved
- An automated 'Developer Compliance Centre' app for maker self-certification
- Power BI dashboards for tenant-wide visibility
UK Licensing Note: The CoE Starter Kit requires Power Platform for Admins licences. For most UK organisations, these are included in Microsoft 365 E3/E5.
Step 2: Define Your Environment Strategy
Environment sprawl is the most common Power Platform governance failure in UK organisations. The default pattern we recommend for most UK mid-market organisations is a three-tier environment strategy:
| Environment | Description |
|---|---|
| Development | Individual developer sandboxes, no production data, limited connectors, auto-deleted after 30 days of inactivity |
| Test / UAT | Shared environment for user acceptance testing, production-equivalent data policies, no live external connectors |
| Production | Live business solutions, full DLP enforcement, IT-managed, change-controlled deployments only |
Step 3: Implement Data Loss Prevention Policies
DLP policies control which connectors can be used together, preventing citizen developers from inadvertently connecting sensitive internal data (Dataverse, SharePoint) to external services (social media, personal email).
Common UK mistake: Setting a single DLP policy at the tenant level that blocks legitimate business connectors, forcing citizen developers to work around governance entirely. Layer your DLP: permissive at tenant level, tighter at production environment level.
Step 4: Establish Your Maker Journey
- Maker self-registers via the Developer Compliance Centre (from CoE Starter Kit)
- Maker completes a 2-hour self-paced Microsoft Learn path (free)
- Maker receives access to the Dev environment and a starter template
- Solution built in Dev, maker completes a self-certification checklist before requesting UAT promotion
- CoE team reviews and promotes to Test; business sign-off confirms Production readiness
Step 5: Licence Optimisation
Power Platform licensing in the UK is frequently mismanaged, with organisations over-paying for per-user licences when per-app or pay-as-you-go models are more cost-effective. The CoE inventory data from Step 1 is essential. You will typically find that 20–30% of licensed users have not built or used an app in the previous 90 days.
How Long Does a CoE Take to Stand Up?
For a UK organisation of 500–5,000 employees, a functional CoE (Starter Kit deployed, environment strategy in place, DLP policies configured, and maker journey defined) takes 6–8 weeks with dedicated internal resource or 4 weeks with external partner support.
Key Metrics to Track from Day One
- Total active apps by environment (production vs. non-production split)
- Orphaned apps, solutions with no active owner (common after staff turnover)
- DLP policy violations attempted in the last 30 days
- Licence utilisation rate (active makers / total licences)
- App usage by business unit, identifies underused solutions and training opportunities
