When the description becomes the build
Until quite recently, building a Power Automate flow felt like a craft. You learned the connectors, the trigger patterns, the ways the platform bites you when you assume it works like Excel. It was approachable, but it wasn't trivial — and most non-IT users gave up around the fourth or fifth step of any meaningful flow.
Copilot in Power Automate has eaten that learning curve. When a new email arrives in a shared mailbox with the word "invoice" in the subject, save the attachment to the Finance SharePoint site and send a Teams message to the AP team channel. You type that, Copilot builds the flow, you correct the bits it got wrong, you publish. Five years ago it would have been an IT ticket. Today it's a fifteen-minute job for someone who's never written a flow.
Power Apps with Copilot has done the same thing to app building. Describe the data you have, describe the screens you want, and the platform builds the data model, the layout and the basic logic. The result still needs a human pass — but the gap between I have an idea and I have a working app is now an order of magnitude shorter than it used to be.
Why this is a governance event, not a productivity one
Most of the press treats this as a productivity story — anyone can automate now! — and it is, but the more interesting consequence is structural. Power Platform now has tens of millions of monthly active users. AI Builder ships pre-built models for document processing, sentiment analysis and GPT-powered prompts you can drop into any flow. The number of apps and flows running inside the average enterprise has been on a steep curve for two years and the natural-language layer has tipped that curve into something steeper still.
The orgs handling this well aren't the ones treating every new app as a risk to be reviewed. They're the ones who've split their estate into two tiers and govern each accordingly.
The two-tier estate
Personal automation. Flows and apps that affect only the maker — their inbox, their calendar, their Planner. The right governance pattern here is minimal. Encourage it, train people on it, put it in a Default environment with sensible DLP policies, and otherwise stay out of the way. The single biggest cause of low Power Platform ROI is IT departments smothering personal automation with the same controls they use for production systems.
Shared and business-critical. Anything that affects multiple people, processes a financial transaction, or touches regulated data. This belongs in a Managed Environment with proper sharing limits, solution checker enforcement, ALM, and monitoring. The good news is that Microsoft has invested heavily in this in 2024 and 2025 — Managed Environments now do a lot of the heavy lifting that previously required a custom Centre of Excellence build.
If your makers can't tell which tier their work belongs in, your training is the missing ingredient — not your governance.
What changes for IT
There's a quiet anxiety in IT departments about all this, and it's worth being honest about it. If anyone can build a flow, what do the automation specialists do? The answer, over the orgs I've worked with, is that the role moves up the stack. The valuable IT work isn't building flow #847. It's:
- Designing the platform — environments, DLP, connector strategy, identity
- Coaching the makers — running office hours, reviewing patterns, spotting reuse opportunities
- Owning the critical path — the small set of flows the business genuinely depends on
- Watching for the inevitable consolidation — six teams accidentally building the same thing in different ways
Done well, that's a more interesting job than the one it replaced.
Where to start if you're behind
Three small moves, in order.
- Pick a single repetitive job and let one person automate it. Not a strategic process. A genuinely annoying daily job — pulling a report, copying numbers between two systems, sending a recurring confirmation. Make it visible. Tell the story.
- Stand up a Managed Environment for shared work and a Default environment for personal flows. Two-tier model, sensible defaults, light touch.
- Run a monthly show what you built call. No agenda. Anyone who's automated something demos it for two minutes. The reuse value of these calls is enormous, and they're also the most honest measure of your platform's health.
Power Automate has stopped being a specialist tool. The orgs that benefit most are the ones whose IT teams accept that, and reposition themselves to enable it rather than guard against it.