Home / Insights

Citizen development without chaos: governing Power Automate at scale

Citizen development works until the day someone asks how many flows the organisation actually runs, who owns them and what data they touch. If the answer is "we're not sure", the automation estate has outgrown its governance. That moment arrives for most organisations sooner than expected. Power Automate is included with Microsoft 365, it is easy to learn, and the people closest to a problem can build their own fix in an afternoon. That is a real strength, and it is why adoption spreads quickly. But success creates its own risks.

, 6 minute read

When the automation estate outgrows its governance

The question for leaders is not whether to allow citizen development, because it is already happening, but how to make it safe, visible and sustainable without strangling the enthusiasm that makes it valuable.

Why Power Automate governance matters more now

Two trends are raising the stakes. First, Power Automate is no longer limited to simple notifications. Flows now run approvals, financial processes and customer communications, and increasingly call AI services. Second, regulators and customers expect organisations to know where their data goes. In New Zealand, the Privacy Act sets expectations for how personal information is collected, used and protected, and an unmanaged flow can put an organisation on the wrong side of those expectations without anyone intending it. Governance is how you demonstrate that you know what your automation is doing.

How good intentions become shadow automation

Power Automate is easy to start with, and that is exactly why estates sprawl. Flows get built by individuals, connected to personal accounts, copied, shared and left running after the author moves on. Each decision is sensible on its own. Together they create unmanaged risk, a hidden support burden and costs nobody planned for.

What the risk looks like in practice

Consider a familiar scenario. An administrator builds a flow that copies customer attachments from a shared mailbox into a personal cloud storage account because it is convenient. Another team member copies the flow and tweaks it. A third shares it with the whole department. Within months there are a dozen variations, running under the credentials of people who may change roles, none of them documented, and one of them sending customer data somewhere the organisation never approved. Nobody did anything malicious. Everyone was trying to help.

The consequences usually surface in one of three ways. A security or privacy review finds data moving through connectors nobody sanctioned. A key person leaves and flows stop working, along with the process that quietly depended on them. Or a licensing review discovers that flows have drifted into premium territory and the bill is higher than anyone expected. All three are governance failures, and all three are avoidable with modest, early investment.

Why blanket restrictions backfire

When organisations first see the scale of unmanaged flows, the instinctive reaction is often to restrict: lock down the default environment, remove makers' access, or block connectors wholesale. Sometimes a temporary tightening is justified, particularly where sensitive data is at risk. But blanket bans rarely work for long. The business need that drove people to build flows doesn't go away, so the building moves elsewhere, into tools and services the organisation can see even less of. Governance that channels the energy of makers into supported routes will always outperform governance that tries to suppress it.

The foundations of governance that enables

  • Environment strategy: keep personal productivity in the default environment and move business-critical work to managed development, test and production environments.
  • Data loss prevention policies: group connectors according to your data risk and block combinations that could leak sensitive information.
  • A Centre of Excellence: own the standards, support makers and monitor the estate. Microsoft's Centre of Excellence Starter Kit is a useful starting point.
  • Ownership and lifecycle: every flow has an owner and a backup, and orphaned flows are detected and reassigned.
  • Training and guardrails: a simple "licence to build" for makers, plus templates and naming conventions.
  • Visibility: dashboards for inventory, usage and failures so leaders can see the estate, not guess at it.

A pragmatic way to start governing Power Automate

Organisations often stall because governance feels like a large programme. It doesn't need to be. Start with visibility: use the admin tools and Microsoft's Centre of Excellence Starter Kit to inventory the environments, flows, connectors and owners that already exist. You cannot govern what you cannot see, and the inventory alone is often a revelation. Next, set a baseline data loss prevention policy that blocks the clearly risky connector combinations, and decide which environment is for personal productivity and which is for business-critical work.

Then focus on people. Nominate a small group of champions, publish a one-page set of building standards, and offer short, practical training. Create a clear path for promoting a successful personal flow into a supported business solution, with review and testing along the way. Over the first 90 days the goal is not perfection. It is to move from "we don't know" to "we know what we have, we know who owns it and we know how new work gets approved".

Governance people don't resent

The goal is a "fast lane and slow lane" model. Personal productivity flows stay lightly governed so people can move quickly, while anything that touches customers, finance or regulated data follows a defined path with review, testing and an accountable owner. The aim is safe speed, not control for its own sake. When makers see governance as the thing that keeps their flows running, rather than the thing that slows them down, adoption and compliance rise together.

Who does what in Power Automate governance

Clear roles prevent governance from becoming everyone's job and therefore no one's. Makers are accountable for building responsibly and keeping their flows documented. Business owners are accountable for the process and the outcome it delivers. The Centre of Excellence owns the standards, tooling and support for makers. IT and security own the platform controls and the policies that sit behind them. Executive sponsors own the funding and the mandate. Writing these responsibilities down on a single page, and checking that every critical flow has a named person in each relevant role, resolves most of the ambiguity that causes governance to fail.

Measuring whether governance is working

Good governance should show up in numbers that leaders already care about: the share of flows with a named owner, the number of orphaned flows found and fixed each month, policy violations caught before data moved, the time taken to move a flow from idea to supported production, and growth in the number of active makers. If makers are leaving the platform or building around the controls, governance has become friction and needs to be redesigned. If the estate is growing while incidents and surprises are falling, the model is working. Review these measures quarterly and share them with the business, because visible results are what earn continued support for the Centre of Excellence.

Culture decides whether it sticks

Culture is the final ingredient. Celebrate makers who solve real problems, and make it easy for them to ask for help. Treat near misses, such as a flow that nearly exposed data, as learning opportunities rather than occasions for blame. Share good examples, templates and reusable components so that doing the right thing is also the quickest thing. Organisations that get this right find that governance stops feeling like a brake and starts to feel like a service: one that helps people build better automation, and gives leaders the confidence to let them.

Flex helps New Zealand organisations design, govern and support automation across Power Automate, enterprise RPA and AI agents. If you would like a second opinion on your own setup, talk to the Flex team.

Related reading

Related Flex services

Sources and further reading

Questions we are asked

What is Power Automate governance?

It is the set of guardrails that lets people build flows safely: environments, data loss prevention policies, named owners, standards and monitoring, so the organisation knows what flows exist, who owns them and what data they touch.

Should we restrict who can build flows?

Blanket restrictions tend to push automation into unofficial tools. A better approach is to keep the safe path easy: a default environment with sensible limits, clear rules on connectors and a quick route to help for anything more critical.

What is a Power Platform centre of excellence?

A small team, often part time to begin with, that sets standards, monitors the estate, supports makers and decides when a flow needs professional support. Microsoft publishes a starter kit to help set one up.

Talk to us about what you would automate first

Your first consultation is free and comes with no obligation. It is a working session, not a pitch: bring a process that is costing your team time and we will tell you plainly whether automation fits it, which platform we would use, and what a pilot would look like.

Book a free consultation