Power Platform Governance and Centre of Excellence
International law firm
In short
How does a law firm bring ungoverned Power Apps and flows under control?
The clients had let the Power Platform grow faster than its rules. About 100 canvas apps, 5 model-driven apps and 250 flows were in use, and the firm itself described that use as largely ungoverned. We set up formal governance and a Centre of Excellence, so the firm keeps the speed of low-code and protects client data.
Results in numbers
- canvas apps analysed
- c. 100
- flows analysed
- 250
- adoption support
- 120 hrs
At a glance
- About 100 canvas apps, 5 model-driven apps and 250 flows brought under review
- Centre of Excellence set up and administrators trained
- Security baseline and checklist for every new environment
The client
The client is an international law firm with offices worldwide. Its teams had adopted Power Apps and Power Automate on Microsoft 365, and the engagement covered the firm's UK tenant.
What it was costing them
- Unknown ownership: apps and flows were created by many teams, so owners and business criticality were not recorded.
- Security exposure: a law firm holds privileged client data, and unmanaged sharing and connectors put that data at risk.
- No lifecycle: without agreed environments or a deployment path, changes went straight into the apps people used.
- Key-person risk: knowledge of how each solution worked sat with the individual who built it.
What we did
We ran a six phase governance programme: discovery, administrator training, strategy, a security baseline, the CoE Starter Kit and three months of adoption support.
- A clear inventory: we exported the list of apps and flows with their owners, then sent every owner a questionnaire.
- Priorities based on risk: answers were assessed for criticality, complexity and return, so cleanup began with what mattered.
- Confident administrators: a hands-on Admin-in-a-Day session covered apps, flows, data security and compliance.
- One agreed direction: two strategy workshops fed a single Governance Strategy and Architecture document, revised after feedback.
- Visibility day to day: the CoE Starter Kit modules were agreed with the clients, deployed and shown to administrators.
- A repeatable baseline: a health check and two configuration sessions set it for one tenant and one environment, with a checklist for every new one.
- A smooth handover: a service transition workshop passed the CoE to IT operations, backed by three months of adoption support.
Results
- About 100 canvas apps, 5 model-driven apps and 250 flows were analysed for transition under the new CoE.
- The agreed deliverables were one Governance Strategy and Architecture document, a security baseline checklist and a deployed CoE environment.
- Adoption support was set at 120 hours, 40 hours a month for three months.
The risk most teams miss
The month three risk is a Centre of Excellence that nobody acts on. The inventory goes stale, new makers appear outside managed environments and cleanup stalls once consultants leave. We handled it with named owners from the questionnaire, a checklist for each new environment and three months of adoption support. The firm must also keep the Starter Kit current.
What we would add today
Improvements we would add on top of what is live.
- Group environments into environment groups with Managed Environments rules, so sharing limits and usage digests apply by default.
- Replace blanket restrictions with advanced connector policies, blocking client data connectors in personal environments and allowing them in approved ones.
- Move deployment to Power Platform pipelines with service principals and connection references, so no solution depends on one person's account.
- Feed the Microsoft Purview audit log into the CoE and enable Dataverse auditing, to show who accessed which matter data.
- Add a Copilot Studio agent for makers that answers which environment to use and starts the request flow from the governance document.
Technology
Power Platform admin centre, Power Platform CoE Starter Kit, Power Apps, Power Automate, Dataverse, Microsoft Entra ID, Microsoft 365.
Tell us how many apps and flows your teams have built without a register, and we will tell you where the risk sits and how to bring them under control.
Products and capabilities
- Power Apps
- Power Automate
- CoE Starter Kit
- Centre of Excellence
- security baseline
- environment strategy
- Power Platform governance
The service behind this work
Power Platform governance
Related use cases
IT and platform teamsPower Platform Business Kickstarter
Firms often start with Power Platform by building something, then find that licences, ownership and priorities were never settled. We ran a short kickstarter that gave a firm a ranked idea backlog, a group of trained early adopters and a business case, before any large spend.
- 45
- people in ideation workshops
- 4
- programme phases
Power Platform Governance Kickstarter
The client was building on Power Platform in several countries without agreed rules for environments, data policies or ownership. Each month without governance meant more apps and flows to untangle later. We ran a governance kickstarter that trained the administrators, set a security baseline, deployed the Centre of Excellence Starter Kit and documented the strategy.
- 4
- programme phases
- 6 hrs
- Admin in a Day
Dataverse Housekeeping and Storage Advice
Dataverse capacity costs money, and it fills quietly. Import logs, system jobs and old workflow records grow in the background until an environment runs short. The client asked how to housekeep its environments. We put in place a short routine of checks and clean-ups that frees storage without touching business data.
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.