Skip to content

All Insights

GuidePower Platform & Custom Apps

What Microsoft 365 automation costs once you have twelve staff

Automation inside Microsoft 365 is often described as free, because you are already paying for the subscription. Quite a lot of it genuinely is. The part that is not tends to be discovered after something has been built, which is the worst moment to find out.

This is the arithmetic, done before the build rather than after.

Prices change. Everything here was taken from Microsoft’s own Irish pricing and licensing documentation on 13 August 2026. Check the current figures before deciding anything, and treat the structure as the durable part rather than the numbers.

What you already have

A Microsoft 365 business subscription includes automation using what Microsoft calls standard connectors. In practice that covers the things most small businesses actually want to join together: SharePoint, Outlook, Teams, OneDrive, Excel and Forms.

Build a flow that watches a form, writes a row into a list, files an attachment and emails whoever needs to know, and you are inside what you already pay for. No extra licence, no additional cost, and this is a real capability rather than a teaser.

A large share of small business automation never leaves that boundary. If yours does not, this article is reassurance rather than a warning.

Where the line actually is

Microsoft’s licensing documentation is explicit about what the Microsoft 365 entitlement does not cover. Three things:

  • Premium connectors. Anything joining to a system outside the Microsoft world. Your accounting package, your CRM, a SQL database, a payment provider.
  • Custom connectors. Anything talking to a system that has no ready-made connector, which is most industry-specific software.
  • On-premises data. Reaching a server sitting in your own building, through a gateway.

There is a fourth, quieter one. Microsoft 365 subscriptions now include a limited slice of Dataverse, which is the database underneath the platform. The documentation states plainly that it exists for certain Microsoft applications and cannot be used to run custom apps or flows. It looks like a database you have. It is not one you can build on.

Notice what unites the list. The included version is generous as long as everything stays inside Microsoft. The moment your process touches the rest of your business, you are buying something.

The numbers, at Irish list prices

  • Power Automate Premium: €13.00 per user per month, paid yearly. This is the one that unlocks premium connectors for a person.
  • Power Automate Process: €130.00 per bot per month. Licensed per process rather than per person, for automation nobody sits and watches.
  • Hosted Process: €186.30 per bot per month, where Microsoft also provides the machine it runs on.

Power Apps is licensed separately again, so an automation with a screen attached is a second question rather than the same one.

Twelve staff, worked through

Say twelve people need to use one process that reaches your accounting system. That is a premium connector, so each of them needs a licence.

  • 12 × €13.00 = €156 a month
  • €1,872 a year
  • €5,616 over three years, before anyone builds anything

That is the licence alone. The build is on top, and the licence continues whether or not the process changes, for as long as it exists.

Now the same process built as a small application on ordinary hosting. Hosting costs what hosting costs, typically a couple of hundred a year for something modest, and it does not care whether three people use it or thirty. The build is a one-off. There is no per-person charge, ever.

At three users, Microsoft is almost certainly cheaper and definitely simpler. At twelve it is a real decision. At thirty it stops being close.

The argument for paying anyway

Cost is not the only axis, and it would be a poor article that pretended otherwise.

A licensed flow sits inside a platform your data already lives in, governed by policies your administrator already set. Someone non-technical can open it and change a condition. Any Microsoft partner in the country can take it over. Nobody has to think about backups, patching or where it runs.

Against a custom application, those are genuine advantages and they are worth money. €1,872 a year buys a lot of not-having-to-think-about-it. The mistake is not paying it. The mistake is paying it without ever having known there was a choice.

Five things worth doing

  1. Ask which connectors a proposed automation uses, and whether any are premium. That single question determines whether it costs anything at all.
  2. Count the people who need to touch it, including anyone who only views. Per-user pricing does not care that they barely use it.
  3. Multiply by three years. Licensing is a subscription and the build is not, so a one-year comparison flatters the subscription.
  4. Check whether it could stay inside standard connectors with a small change to the process. Sometimes the premium connector is convenience rather than necessity.
  5. Get the licensing position in writing from whoever is quoting, at your headcount. A vague answer is itself information.

Common misconceptions

  • “Power Automate is included, so it is free.” Automation across Microsoft’s own tools is included. Reaching anything else is not.
  • “Only the person who builds it needs a licence.” Generally the people running the flow need the entitlement too, which is what turns one licence into twelve.
  • “We have Dataverse, it came with our subscription.” A limited version, for specific Microsoft applications, explicitly not for running your own apps or flows.
  • “Custom is more expensive than licensing.” Sometimes. Compare over three years at your actual headcount before assuming it.

The honest summary

If your automation stays among SharePoint, Outlook, Teams and Excel, it is included and you should use it. That covers more small business processes than people expect, and there is nothing clever about avoiding something you have already bought.

If it reaches your accounting system, your CRM, or a server in the building, you are buying per-user licences for as long as the process lives. At a handful of users that is fine. At twelve it deserves ten minutes of arithmetic, and it is worth knowing what the alternatives actually are before committing.

If you have a quote in front of you and cannot tell which side of the line it sits on, say what the process touches. That is usually enough to work out whether it costs anything at all.

Sources

Microsoft’s Power Automate pricing page for Ireland, and the Licensing overview for Microsoft Power Platform on Microsoft Learn. Checked 13 August 2026.

Common questions

Is Power Automate included with Microsoft 365?

Partly. Business subscriptions include building and running flows using standard connectors, which covers SharePoint, Outlook, Teams, OneDrive, Excel and Forms. Premium connectors, custom connectors and on-premises data are not included and need a separate licence.

What is a premium connector, in plain terms?

A connection to something outside Microsoft’s own products. Your accounting software, a CRM, a SQL database, a payment provider. The rule of thumb is that staying inside Microsoft is included and leaving it is not.

Does everyone using a flow need a licence, or just the person who built it?

Generally the people the flow runs for need the entitlement, not only its author. That is the detail that turns an apparently small cost into a per-head one, and it is worth confirming for your specific case before building.

Is it cheaper to build something custom instead?

It depends almost entirely on how many people touch it. A custom application has a one-off build cost and no per-user charge, so it improves as headcount rises. At three users, licensing usually wins. At thirty, it usually does not.

All Insights

Have a problem you think technology could solve?

Describe it below. No project is too small or too undefined to start the conversation.

Prefer to talk? Book a call directly →

A sentence or two is plenty. No jargon needed.