Power Automate for SMEs: where the included licence ends

Most companies evaluating an automation tool already pay for one.

Power Automate ships with Microsoft 365. It sits in the tenant, licensed and idle, until someone builds a first workflow and hits a message asking for an additional licence — usually after the work is done, not before.

The boundary that triggers that message is not where people expect it. It has nothing to do with how complex the workflow is, or how many steps it has. It depends on two things: which application you connect to and how often the workflow runs.

Both are knowable in advance. That is what this article is for.

What a Microsoft 365 licence already includes

Microsoft calls this a seeded licence — a usage right attached to another product. A Microsoft 365 subscription does not give you Power Automate as a product. It gives you a defined slice of it.

That slice is: cloud flows with standard connectors, unlimited in number. A cloud flow runs in Microsoft's cloud, triggered by an incoming mail, a schedule, or a new item in a list.

How far the standard connectors reach

Further than the name suggests. Outlook, SharePoint, Teams, OneDrive, Excel, Planner, Forms and To Do are all standard — essentially the whole Microsoft 365 estate a small business already works in every day.

That covers the workflows that quietly consume the most time: filing mail attachments, chasing approvals, watching deadlines, moving form entries into a list. Automating inside Microsoft 365 costs nothing beyond the subscription you already hold.

If you want the wider picture of what else sits unused in that subscription, we have written it up separately for Microsoft 365 features in a small business and for the security controls in Business Premium.

The first boundary: the connector, not the feature

What is not included: premium connectors and custom connectors. That is the line where the cost starts — and it runs straight through applications that feel entirely ordinary to a small business.

Premium covers SQL Server, Dataverse, Salesforce, direct HTTP calls to any API, and most third-party systems. The moment a workflow needs to touch your own CRM or a line-of-business application, you are almost always across the line.

This is where automation in smaller companies usually stalls. Not on capability — on the fact that the interesting data lives outside Microsoft 365. Getting those systems to talk to each other is a separate problem, and it belongs to data silos between ERP and CRM rather than to the automation tool.

The exception, and why it rarely helps

There is one. A workflow using a premium connector is permitted without an extra licence if it is in-context — bound to the application the seeded right came from, such as a Power App or Dynamics 365. A standalone workflow does not qualify.

For a small business without Power Apps, that exception is usually not an exception at all.

The second boundary: actions per day

Every step counts as an action. Setting a variable counts. A failed attempt counts. Each retry counts. Microsoft calls these Power Platform requests and caps them per 24 hours.

The official figures, as of September 2026:

A separate ceiling of 100,000 requests per five minutes applies regardless of licence.

The contradiction worth knowing about

Those numbers are not currently enforced. Microsoft states that every organisation is in a transition period with more generous limits: 10,000 per flow instead of 6,000 per user, 200,000 instead of 40,000.

The same document also says: *"Build your cloud flows based on official limits."* And it gives no date for when the transition ends — only a condition. Usage reporting has to reach general availability first, and then six months pass.

So planning against 10,000 today means planning against a number that can drop to 6,000 with six months of notice. That is not cause for alarm. It is a reason to measure consumption rather than assume it — the Power Platform admin center reports it per flow, per day.

What a licence costs if you need one

Swiss list prices, excluding VAT, billed annually:

Premium is the user licence: every connector, 40,000 actions a day, and one attended RPA bot for that person. Process is a capacity licence — it attaches to a single workflow or machine rather than to a person.

Which one is cheaper, and when

This is arithmetic, not preference. One Process licence costs roughly what ten Premium licences cost.

It still wins in one specific shape: one workflow used by many people. A workflow holding a Process licence may use premium connectors no matter what licence the triggering user holds. An approval process that fifty employees start needs one licence instead of fifty.

Two conditions that catch people out: the workflow has to live in a solution, and up to ten Process licences can be stacked on the same workflow. Alternatively, up to 25 workflows can share one licence's 250,000 actions through a flow group.

RPA: the part most people underestimate

Alongside cloud flows there are desktop flows — automation that drives mouse and keyboard for software with no API. For older line-of-business applications it is often the only route.

The licensing here is stricter than it looks:

• Attended, supervised on your own machine: included in Premium, one bot per licence.
• Unattended, running overnight on its own: not included in Premium. That needs a Process licence.

One useful detail: running a desktop flow consumes no Power Platform requests. The daily ceilings above apply to cloud flows only.

Where a small business actually starts

The first step is an inventory, not a purchase. The useful question is not "what could we automate" but: which repeating manual task costs us time every week and runs entirely inside Microsoft 365?

Everything that meets the second condition is already paid for.

Three workflows that nearly always pay off

• Incoming invoices: a mail with an attachment arrives, the attachment lands in a structured SharePoint location, finance gets a notification.
• Approvals: a request through a form, a decision by one click in Teams, the outcome written to a list — instead of a mail thread nobody can reconstruct later.
• Deadlines: a scheduled flow checks a list daily and reports what expires in fourteen days. Contracts, certificates, service intervals.

None of the three needs a premium connector. All three run far below 6,000 actions a day.

What actually goes wrong

Rarely the technology. Almost always one of two organisational problems.

The workflow belongs to a person

A cloud flow runs under its owner's account and draws on that person's action allowance. When they leave, the workflow stops — usually on an inconvenient day. Workflows that matter belong in a solution, with more than one owner.

Nobody notices a failure

By default a failed run notifies only the owner, by mail, among everything else. A workflow without an agreed response time is a workflow nobody should depend on — the same logic as a service level agreement in IT operations.

Where Power Automate stops being the right tool

It moves work between existing systems. It is not a substitute for an application.

Once a workflow needs more than roughly thirty steps, splits into many branches, or starts holding its own data, the question is no longer which connector. It becomes a question of custom software versus off-the-shelf. A workflow only its author understands costs more than the manual work it replaced.

And where the task needs judgement rather than rules — reading text, classifying it, drafting a reply — rule-based logic ends regardless. That is the territory of AI agents with system access, not of if-then chains. Which processes are worth automating today we have worked through in twelve concrete examples.

The order that works

1. Check what is already licensed. In Power Automate under Settings, "View my licenses".
2. Build one workflow that only uses standard connectors. It costs nothing and demonstrates the value.
3. Measure consumption before adding a second.
4. Then licence — and check whether Premium per person or Process per workflow is cheaper.
5. Use the 90-day trial: it includes premium connectors and both attended and unattended RPA, with no purchase decision attached.

Reverse that order and you are buying capabilities nobody has yet shown a need for.

Conclusion

In most Swiss small businesses Power Automate is already paid for and largely unused. What is missing is rarely budget. It is knowing exactly where the included version ends.

It ends at two checkable points: the first premium connector and 6,000 actions per user per day. Everything before that is configuration. Everything after it is an invoice you can calculate in advance.

Knowing both turns automation from a gut call into a decision based on two numbers from your own operation. What that looks like at a larger scale is our process automation work — and whether the business needs in-house IT capacity for it at all is a matter of arithmetic rather than headcount.

Frequently asked questions (FAQ)

Is Power Automate really included free with Microsoft 365?

Yes, within a clearly defined scope: unlimited cloud flows using standard connectors, officially capped at 6,000 actions per user per day. Premium connectors, custom connectors and unattended RPA are not included. Short version in the glossary: Power Automate.

What does Power Automate cost in Switzerland?

Power Automate Premium is CHF 12.10 per user per month and Power Automate Process CHF 121.50 per bot per month, both billed annually and excluding VAT (Microsoft list prices, September 2026). The price in your own tenant may differ if it runs through a partner.

How do I know a workflow needs an extra licence?

By the connector. Power Automate marks premium connectors in the picker, and the check on save reports the missing licence. The second trigger is the action count — visible in the Power Platform admin center per flow and per day.

Is a Process licence worth it for a small company?

In one case only: when a single workflow is used by many people, or has to run unattended. At roughly ten Premium licences per Process licence the threshold is clear — below it, Premium per person is cheaper.

What does ALPENIQ do here?

We start by checking what the existing subscription already covers, and build the first workflow inside it. Licences enter the conversation once the need is measured, not before.