Power Automate licensing: the real cost of "free"

Why "free" Power Automate is hard to budget for

This article explains where the costs sit, why they creep, and how to build a view of total cost that holds up to scrutiny. Licensing details change regularly, so treat this as a framework and confirm specifics with Microsoft or your licensing partner.

What is included with Microsoft 365, and what is not

Microsoft 365 licences typically include Power Automate for standard connectors in flows that work with Microsoft 365 services. Premium connectors, unattended desktop automation, higher request limits and AI capacity generally require additional licences, and the licensing options have changed several times. The gap between "included" and "what we actually need" is where budget surprises come from.

A further complication is that the licence a flow needs can depend on who runs it, which connectors it uses and what it does, rather than on a single organisation-wide setting. A flow that is covered when run by one user may need a different licence when it is shared across a team or triggered by an external event. That is why an inventory of what flows actually do, rather than a list of the licences held, is the foundation of any reliable cost view.

Why Power Automate costs creep

Most flows begin life as simple, standard-connector automations. Then a team realises the same flow could update the finance system, call an external service or run on a schedule against a larger data set. Each of those improvements is sensible and each can change the licence the flow requires. Because the person improving the flow rarely sees the licensing consequences, the cost increase is invisible until it is noticed centrally, often during a true-up or an audit.

There is also a structural reason. Costs are spread across several budgets and owners. Licences sit with IT or procurement, build effort sits with business teams, and support effort sits with whoever happens to be asked. No single person sees the whole picture, so no single person is asked whether the estate is good value. Pulling those threads into one view is the first step towards making sensible decisions, such as consolidating licences, retiring flows nobody uses or deliberately moving a critical process onto a more appropriate licensing model.

An illustrative example

Consider a hypothetical organisation of 200 people. It starts with standard connectors and a handful of approval flows at no extra cost. Over the following year, three business-critical flows are connected to the finance system through a premium connector, an unattended desktop flow is added to handle a legacy application, and an AI-based document step is introduced for invoices. Individually, each change is small. Together they introduce premium licensing, machine costs, AI capacity charges and a support burden that was never in the original plan. The figures vary by organisation, but the pattern doesn't: the cost of an automation estate tends to follow the value of the processes it carries, not the licence it started on.

Costs that rarely make the budget

Premium connector use creeping in once flows become genuinely useful.
Unattended automation licensing, plus the machines or virtual machines it runs on.
AI capacity, such as AI Builder and Copilot credits consumed by AI-enabled flows.
Request limits and throttling as volumes grow.
Support, monitoring and maintenance effort after go-live.
Governance, training and Centre of Excellence time.
Environments and Dataverse storage when solutions mature.

Of everything on that list, the largest cost is usually the one that never appears on a licence invoice: people's time. Every flow that matters needs someone to build it properly, test it, monitor it and fix it when something changes upstream. If that effort is not planned, it is paid for anyway, through urgent fixes, interrupted projects and business users who spend their afternoons troubleshooting rather than doing their jobs. The cheapest automation to run is one that was designed with support in mind from the start. Putting a realistic figure on ongoing effort, even a rough one such as a number of hours per flow per month, changes how leaders compare options and prevents the false economy of "free" tooling that is expensive to keep alive.

How to budget for Power Automate with confidence

Start by inventorying existing flows and connectors. Classify them by business criticality, map each to the licence it actually needs, forecast growth over the next 12 to 24 months and include the support effort. Review quarterly, because usage patterns shift as adoption rises. A total cost of ownership view lets finance compare Power Automate fairly against other options, and gives the ROI conversation a credible cost side.

Questions to ask before you commit

Whether you are reviewing an existing estate or planning a new programme, a short list of questions will surface most of the surprises before they cost money.

Which of our current flows use premium connectors, and who is relying on them?
Which processes need unattended automation, and what will that infrastructure cost?
How much AI capacity will we consume at expected volumes, and what happens when it runs out?
Which flows run under personal accounts, and what licence does each owner actually hold?
What is our growth forecast for the next two years, and does the licensing model scale sensibly?
What is the ongoing support effort, and who pays for it?

Licensing is a strategy decision, not an admin task

Treat licensing as part of your automation strategy, not an afterthought. The right licensing model can make a high-value process cheap to run, and the wrong one can make a simple process surprisingly expensive. Review the position at least annually, ideally with someone who understands both the technical design and the commercial terms. Organisations that do this well tend to make a deliberate choice about which workloads belong on which model, rather than discovering the answer through invoices. The outcome is not necessarily lower spend. It is spend that the business understands, can defend and can connect directly to the value the automations deliver.

What to put in front of finance

When you take the picture to a CFO, keep it simple. Show current licensing spend, the forecast for the next two years, the support effort expressed in dollars, and the benefits the estate is delivering. A one-page summary that connects cost to value is far more persuasive than a licence schedule. It also positions IT as a steward of the investment rather than the owner of a cost, and sets the tone for a constructive conversation about where to invest more, where to consolidate and what to stop.

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 Flex services

Sources and further reading

Questions we are asked

Is Power Automate free with Microsoft 365?

Partly. Microsoft 365 licences typically cover flows that use standard connectors with Microsoft 365 services. Premium connectors, unattended desktop automation, higher limits and AI capacity generally need extra licences. Check Microsoft's current licensing guide, because the options change.

What are the hidden costs of Power Automate?

Beyond licences, the costs that are often missed are support and maintenance effort, machines for unattended runs, monitoring, rework when a flow outgrows its design, and the time of the people who build and own the flows.

When should we check licensing for a new flow?

At design time, not deployment time. One premium connector or an unattended step can change the cost of the whole process, and it is far cheaper to adjust the design before it is built.

Power Automate licensing and hidden costs: the real cost of "free"