CoE Light for 30 Employees: Lean Power Platform Governance

A full Power Platform Center of Excellence with its own Dataverse data model, multiple Power BI dashboards, and automated governance flows is almost always too much for a team of 30 employees. The underlying idea remains valid, though: without some form of ownership, overview, and guardrails, apps and flows sprawl out of control, and nobody knows anymore who is actually responsible for what once the first colleagues leave the company. The solution isn't necessarily the "CoE Starter Kit" but a CoE light: the same core idea, reduced to what a small team can actually maintain.

This article shows which four building blocks are enough for a CoE light with around 30 employees, why the official CoE Starter Kit is usually the wrong starting point for that, and what to rely on instead. It's based on the official Microsoft documentation on the CoE Starter Kit and on Power Platform adoption.

Why the CoE Starter Kit is usually too much for 30 employees

According to the Microsoft Learn overview of the CoE Starter Kit, the CoE Starter Kit is a comprehensive reference implementation that shows how to build complex governance, monitoring, and adoption capabilities using Power Platform's built-in tools, including its own Dataverse data model, several Power Apps and Power BI analyses, and automated processes for compliance and cleanup. For large enterprises with hundreds of makers, that's exactly right. For a team of 30 employees, of which maybe a handful even build flows or apps, this toolkit is usually oversized, because it has to be maintained, updated, and understood by someone.

One important detail from the current documentation reinforces this point further: according to Microsoft, the CoE Starter Kit is no longer actively developed, and its core capabilities are now part of the Power Platform admin center. Microsoft explicitly recommends starting with the ready-to-use capabilities in the admin center and with managed environments first, and only adding additional parts of the CoE Starter Kit if those built-in capabilities genuinely aren't enough. For a 30-person team, that's exactly the right starting point: use the built-in tools first, instead of maintaining your own governance system that nobody else will look after.

The four building blocks of a CoE light

Building block 1: A named person instead of a committee

According to the Microsoft Learn guide to setting up a CoE, a fully-fledged CoE has several roles: executive sponsor, CoE lead, business stakeholders, IT specialists, change management specialists, and Power Platform champions. With 30 employees, in practice a single person fills several of these roles at once, and that's exactly what Microsoft recommends too: at the start, what matters most is getting stakeholders involved at all, rather than filling every role perfectly right away. Still, an officially assigned Power Platform administrator role is important, one that manages environments at the tenant level, enforces governance policies, and serves as the first point of contact for all questions around apps and flows. This person doesn't need to run their own department, but they do need clearly defined time on their calendar and backing from management, otherwise governance turns into a side project that's the first thing to fall by the wayside in stressful weeks.

Building block 2: Governance basics instead of a complete framework

For a CoE light, governance doesn't mean immediately building an extensive rulebook with data classification, coding guidelines, and formal audits. Of the four governance areas named by Microsoft, data security, solution development, user access, and monitoring, two are enough for a small team to start with: a basic data loss prevention policy that defines which connectors are allowed in which environment, and a simple environment strategy with a clear separation between test and production. Role-based access control and regular access reviews come next, once more than a handful of people actively own apps or flows. Everything else, such as formal test protocols or multi-stage approval processes, can be added later once the team actually grows.

Building block 3: Managed environments instead of your own analytics stack

Instead of running the CoE Starter Kit's own Dataverse data model, a CoE light uses the managed environments built into the Power Platform admin center. Among other things, they provide weekly usage insights, sharing limits, data policies, and maker welcome content, all without having to maintain your own Power BI reports. One point belongs to an honest inventory here: according to the documentation, managed environments are a premium feature included in separate licenses for Power Apps, Power Automate, Copilot Studio, Power Pages, and Dynamics 365, and need to be budgeted for accordingly before you rely on them. For a handful of core environments, such as production and one or two test environments, this effort is manageable for 30 employees and considerably cheaper than running your own analytics stack.

Building block 4: A central point of contact instead of a community program

According to Microsoft, a full CoE builds structured training programs, an extensive documentation library, and its own community of practice with forums, meetups, and hackathons. For 30 employees, a much leaner counterpart is enough: a single, maintained page with the most important rules, three to five templates for common flow types, and a fixed recurring slot, say every four to six weeks, where questions and new ideas get collected. What matters less is the form than the reliability: makers need to know where to look and who to ask before improvising a solution that nobody understands later on.

What a CoE light deliberately leaves open

A CoE light deliberately does without automated compliance processes, its own ROI calculation model for ideas, and a formal maturity assessment based on the Power Platform adoption maturity model. That's not a shortcoming but a deliberate prioritization: these building blocks only pay off once the number of makers, environments, and production flows grows significantly. Until then, a named person, two governance basics, the built-in managed environments, and a fixed point of contact already keep you on top of things, without running a system that's bigger than the problem it's meant to solve.

If you want to clean up your Power Automate environment, set up an initial DLP policy, or figure out which license for managed environments fits your team size, we can help you with our Power Automate services.

Frequently asked questions

Do we even need a CoE, even a light one, with 30 employees?

As soon as more than one person independently builds flows or apps, at least a CoE light is worthwhile. Without a named responsibility and a minimal environment strategy, it becomes difficult to keep an overview once makers leave the company or several departments build their own solutions in parallel. The effort for the four building blocks described here is manageable and can usually be set up within a few weeks.

Can we switch from a CoE light to the full CoE Starter Kit later?

Yes, that's even the path Microsoft recommends. The documentation explicitly advises starting with the built-in tools in the Power Platform admin center and with managed environments first, and only adding the parts of the CoE Starter Kit that these built-in capabilities genuinely don't cover. Since the CoE Starter Kit itself is no longer actively developed, though, it's worth taking a close look before switching at whether the feature you need isn't already built into the admin center.

Is one person really enough as Power Platform administrator?

For 30 employees, usually yes, as long as that person actually gets time for the role and isn't just managing it on the side. According to Microsoft documentation, this role includes, among other things, enforcing governance policies, environment management, security and compliance, and support for makers. If the team or the number of environments grows significantly, it's worth splitting this into an overarching Power Platform administration and additional environment administrators for individual areas.

Do managed environments cost extra with a CoE light?

Yes. According to Microsoft documentation, managed environments are a premium entitlement included in separate licenses for Power Apps, Power Automate, Copilot Studio, Power Pages, and Dynamics 365. Before building your governance strategy on this, you should therefore check which of your existing licenses already include this entitlement and for how many environments you actually need it.

What happens if we don't introduce governance basics?

Without minimal guardrails, unused apps and flows pile up over time, their original owner long gone from the company. At that point at the latest, you lose track of which connectors are actively used in production, which environment serves which purpose, and who even needs to be informed in case of an error. The two basics from this article, a simple DLP policy and a clear separation between test and production environments, prevent exactly this scenario with comparatively little effort.