Why governance cannot wait
In most organisations, Power Platform is available to anyone with a Microsoft 365 licence. That is both its strength and its risk. Within months, dozens of apps and flows appear that IT knows nothing about. Some process personal data, some send information to external services, and many depend on a single person who might leave.
Governance is not about saying no. The goal is to let people build safely while the organisation keeps track of what is running. Done well, governance actually speeds up adoption, because makers know what is allowed and where to get help.
What a Center of Excellence is
A Center of Excellence (CoE) is neither a department nor a new system. It is a small team plus a set of rules, tools and support. It typically brings together IT, security and business representatives who:
- define policies and environments,
- monitor what is being built in the tenant,
- support makers and share good practice,
- decide which solutions move under IT ownership.
Two or three people working part-time are enough to get started.
Step 1: Environment strategy
An environment is a container for apps, flows and data. The default environment is created automatically and everyone has access to it, which is why unmanaged solutions accumulate there.
A proven structure:
- Default environment for personal productivity and experimentation only, with strict policies.
- Team or departmental environments for shared solutions.
- Development, test and production environments for business-critical apps managed by IT.
Step 2: Data loss prevention policies
Data loss prevention (DLP) policies determine which connectors can be combined. Typically you separate business connectors (SharePoint, Dataverse, Outlook) from personal and external services, so a flow cannot copy company data into private storage.
Start with one tenant-wide policy blocking obviously risky connectors, then apply stricter rules to the default environment.
Step 3: Visibility into what is running
You cannot govern what you cannot see. Microsoft provides the CoE Starter Kit, a set of solutions that collects data on environments, apps, flows and makers and surfaces it in dashboards. Some capabilities are also available directly in the Power Platform admin center.
Pay particular attention to:
- widely used apps and flows without a clear owner,
- solutions whose author has left the organisation,
- the use of premium and external connectors.
Step 4: Managed Environments and sharing rules
Managed Environments add extra controls: limits on app sharing, weekly usage digests and requirements such as solution descriptions. They suit environments where solutions are built for larger audiences. Check the licensing implications, as Managed Environments require premium licences.
Step 5: Lifecycle for critical solutions
Once an app becomes important to the business, it no longer belongs in one maker's personal space. Critical solutions should:
- be packaged as solutions,
- move through development, test and production using ALM practices such as Power Platform Pipelines,
- have a backup owner and documentation,
- use service accounts rather than personal connections.
Step 6: Maker enablement
Governance only works if makers embrace it. What helps:
- a simple getting-started guide linking to the policies,
- a community in Teams where people ask questions and share solutions,
- training tailored to different skill levels,
- a clear process for requesting a new environment or connector.
Bottom line
Power Platform governance is introduced in stages: environments and DLP first, then visibility into solutions, and finally lifecycle rules for critical apps alongside maker enablement. A small CoE team with clear policies lets low-code flourish without sprawl or security gaps.
If you want to establish or review your governance model, explore our Power Platform consulting — we help design policies that fit the size and maturity of your organisation.