Skip to content

Power Platform Governance Kickstarter and Handbook

European industrial manufacturer

In short

How can a manufacturer with thousands of Power Platform licences set clear rules?

The client held more than 2,000 per-user Power Platform licences, yet had no agreed way to open an environment, approve a connector or hand an app to IT. Each request was decided from scratch. We ran five governance workshops and wrote the strategy and handbook that make those decisions repeatable.

Results in numbers

handbook pages
c. 180
per-user licences
2,000+

At a glance

  • Five workshops, one per governance pillar
  • Handbook of about 180 pages
  • Five environment types, each with a DLP template

The client

The client is a European industrial manufacturer. It runs Microsoft 365 on E3 and E5 licences, handles IT requests in ServiceNow and already had a small community of citizen developers.

What it was costing them

  • Unused entitlement: more than 2,000 per-user licences were in place, with plans to bring more people onto the platform.
  • No repeatable process: requests for a new environment or connector had no agreed owner, route or criteria.
  • Data exposure: without environment and connector rules, business apps share space with personal experiments.
  • Key-person risk: apps and connections created by one maker stop working when that person leaves.
  • Capacity blind spots: database, log and file capacity is shared by the tenant, and the team wanted per-environment limits.

What we did

We defined the governance model in five workshops, covered the Center of Excellence Starter Kit and wrote it all into one handbook.

  • A shared view of the platform: five workshops on platform management, architecture, application lifecycle, security and user empowerment.
  • Safe places to build: five environment types, from personal productivity to third-party vendor, with naming rules and owners.
  • Data kept where it belongs: a restrictive DLP template per environment type, with new connectors blocked by default.
  • Right effort for each app: Low, Important and Critical levels decide who builds, supports and deploys it.
  • Requests that do not stall: a request form with justification, users, premium connectors, criticality and two owners, routed through ServiceNow or SharePoint.
  • Licences used before new ones are bought: guidance on per-user, per-app and pay-as-you-go plans.
  • An admin team with a clear job: an admin group owns environments, security, DLP and app review, supported by hackathons and App in a day sessions.
  • Oversight from day one: CoE Starter Kit packages Core, Governance, Nurture, Innovation Backlog and Theming.

Results

  • Governance strategy and handbook issued on 12 May 2023, covering strategy, platform basics, step by step use cases and app registration.
  • Five governance workshops held, one for each pillar of the adoption framework.
  • CoE Starter Kit packages Core, Governance, Nurture, Innovation Backlog and Theming scoped for deployment and described in the handbook.

The risk most teams miss

A handbook is only as good as the team that runs it. By month three the first requests arrive, the admin group is busy and exceptions pile up. CoE capacity reservations only send alerts, and connections owned by one maker break when that person leaves. We defined the admin group, a request route, criticality levels that decide who supports what, and a rule to move important apps to a shared owner.

What we would add today

Improvements we would add on top of what is live.

  • Put each department on a Managed Environment in an environment group, so DLP and sharing limits apply by rule.
  • Replace export and import tickets with Power Platform pipelines and an admin approval step.
  • Turn the environment request into a Power Apps and Dataverse app that creates the environment and applies the policy, using a scheduled flow or custom connector for ServiceNow.
  • Move connections to service principals and connection references, so no app depends on one maker.
  • Publish the CoE inventory to Power BI or Fabric with a licence and capacity view.

Technology

Power Platform admin center, CoE Starter Kit, Power Apps, Power Automate, Dataverse, Microsoft Entra ID security groups, ServiceNow, SharePoint, Azure DevOps.

Tell us how many people could build on your Power Platform tomorrow, and we will tell you which environments, connector rules and admin roles you need first.

Products and capabilities

  • CoE Starter Kit
  • Power Platform governance
  • data loss prevention
  • environment strategy
  • governance handbook
  • licensing

Related use cases

IT and platform teams

Have a Microsoft project in mind?

Tell us what you need built, fixed or supported. A senior consultant replies within one business day.