Power Automate licenses across cloud flows and desktop automation, and the two carry very different economics. Cloud flows split into a per user plan that lets an individual run unlimited automations and a per flow plan that licenses a single automation regardless of how many people it touches. Attended robotic process automation rides inside the per user with attended plan, while unattended automation requires a dedicated and considerably more expensive bot license tied to the machine that runs it. Layered on top, AI Builder consumes a separate credit pool, and the premium connectors carry the same paid boundary that governs the rest of the platform. The error that costs the most is licensing broad automation through individual seats when a handful of per flow licenses would cover the same business processes for a fraction of the spend. Power Automate is where automation sprawls faster than anyone models the license mix.
Power Automate licenses through per user and per flow cloud plans, an attended and unattended split for robotic process automation, an AI Builder credit pool, and the seeded rights inside M365. The decisive choice is whether a given process is licensed by the people who use it or by the automation itself.
Cloud flows license two ways. The per user plan covers an individual running any number of automations and suits the heavy maker. The per flow plan licenses a single automation that serves an entire department or process regardless of how many people trigger it, which makes it the efficient choice for broadly shared automations.
Robotic process automation splits sharply. Attended automation runs alongside a logged in user and rides the per user with attended plan. Unattended automation runs without a person on a dedicated machine and requires a separate, premium bot license. AI Builder draws from its own credit pool that meters every model call.
Power Automate produces three recurring waste patterns. The first is licensing shared automations through individual seats rather than per flow. The second is over provisioning unattended bots that sit idle most of the day. The third is letting premium connector flows run on seeded rights that do not cover them.
A single automation that serves a whole department gets licensed by giving every participant a per user plan. The same process licensed once on a per flow plan would cost a fraction. Organizations default to per user because it is the familiar seat model, and the per flow efficiency for broadly shared automations goes unclaimed across the estate.
Unattended bot licenses are expensive and tied to the machine. Organizations provision one per process and leave them running when the automation executes for minutes a day. Consolidating processes onto a shared bot schedule, or moving low frequency jobs to attended execution, recovers the premium spend on capacity that mostly sits idle.
A flow built on standard connectors is covered by the seeded M365 rights. The moment it adds a premium or custom connector, it requires a paid plan, and the seeded coverage stops. Flows drift across that boundary as they mature, and the unlicensed premium usage becomes a documented shortfall when Microsoft maps connectors to entitlements.
The Power Automate bill responds to three levers. The plan mix moves shared automations to per flow and reserves per user for the heavy makers. The bot consolidation right sizes unattended capacity to the real schedule. The connector audit clears the premium overreach before it becomes exposure.
We map every automation against the number of users it serves and the number of flows each maker owns. Broadly shared processes move to per flow licensing. Heavy individual makers stay on per user. The reassignment converts a population of redundant seats into a small set of per flow licenses that cover the same business processes for far less.
The optimized mix then anchors the EA renewal so the automation line reflects the process count rather than an inflated seat rollout.
Unattended bot capacity is consolidated onto a shared schedule so a small number of licensed machines carry many low frequency processes rather than one bot per job sitting idle.
AI Builder credit consumption is then governed against the pooled allocation, with the heavy model calls audited so the credit pool is sized to real usage rather than purchased speculatively against automations that never reach production.
Power Automate negotiates inside the Power Platform envelope, frequently bundled with Power Apps and the broader M365 agreement. The unattended bot and AI Builder lines carry the premium pricing and therefore the largest negotiation upside.
The unattended bot and AI Builder lines are where the premium pricing concentrates, which makes them where the discount matters most. A buyer scaling automation holds leverage to negotiate the bot license rate, the AI Builder credit pricing, and multi year protection on both. Focusing the negotiation on the premium lines rather than the seat plans is where the recoverable spend actually sits in a growing automation estate.
A buyer who arrives with the automation inventory, the per flow versus per user mapping, and the bot utilization data negotiates the renewal against the real process requirement. Carrying an unreconciled estate forward, where shared flows sit on individual seats and idle bots run unconsolidated, anchors the agreement on inflated counts and hands Microsoft the benefit of the unexamined sprawl.
The Power Automate engagement is an automation inventory, a plan and bot optimization, and the integration of the clean baseline into the Power Platform negotiation. The output is an automation estate priced at the processes that run, with the premium lines negotiated where the money is.
We inventory every cloud flow and desktop automation, map each against its connectors, its user count, and its execution schedule, and separate the seeded rights from the paid requirements. We quantify the per flow opportunity, flag the premium connector overreach, and measure the unattended bot utilization. The output is a defensible picture of what the automation estate actually requires.
We move shared automations to per flow, consolidate unattended bots onto a shared schedule, size the AI Builder credit pool to real usage, clear the connector overreach, and fold the clean baseline into the Power Platform negotiation. We focus the discount on the premium bot and AI lines and lock multi year protection. The output is a Power Automate position priced at real process load and defensible through the term.
The Power Automate diagnostic inventories every automation, moves shared processes to per flow, consolidates idle unattended bots, sizes the AI Builder pool to real usage, clears the connector overreach, and brings the clean baseline into the Power Platform negotiation. The result is an automation line priced at the processes that run, with the premium bot rates negotiated where the spend actually sits.