Power Automate "service plan adequate" error: which licence fixes it

You try to save a cloud flow, turn it on or off, or import it, and Power Automate refuses with this message: "The user does not have a service plan adequate for the non-Standard connection." The flow uses at least one premium connector, and the account making the change has no licence that covers it. Per Microsoft's licensing deep dive, a Microsoft 365 licence doesn't cover premium connectors, and a Power Apps or Dynamics 365 licence covers them only for a flow that belongs to the app. The fix is a licence for the person, a capacity licence for the flow, or a 90-day trial. This guide shows how to check what you have, which fix suits which flow, and the cases where Microsoft's pages say different things.

When does the message appear?

• Save is refused Saving, Save as, turning the flow on or off, or importing it failsThe account doing it needs a premium entitlement.
• Shared flow A co-owner or run-only user can't edit or run a flow you sharedEach of them needs one, or the flow needs a Process plan.
• Used to work The same person could save the flow beforeLook for an expired trial or licence.
• Suspended A flow with an attended desktop flow step is suspended after savingThe owner needs a licence with attended RPA.

Why you see it

Microsoft's troubleshooting article lists what sets the message off on a flow with premium connectors: importing the flow, turning it on or off, saving it or saving it under a new name, and any other lasting change to it. The check is on the person doing that action.

The troubleshooting article ties the message to flows that use premium connectors. Microsoft's licence pages set out who gets what:

• Power Automate Free, which every work or school account gets, covers standard connectors only. It also can't share flows.
• Microsoft 365 licences include standard connectors but not premium or custom ones.
• Power Automate Premium and the trial include standard, premium and custom connectors.

So a person with only Microsoft 365, or only the Free licence, sees this message as soon as they save a flow that contains a premium connector.

1. Step 1Someone saves or turns on a flow with a premium connector
2. Step 2Power Automate checks that person's entitlements
3. Step 3No premium entitlement, so the change is refused
4. Step 4Premium for the person, or a Process plan for the flow
5. Step 5The same change goes through

Where Microsoft's pages differ

The troubleshooting article for this message (dated March 2021, last updated in March 2024) says plainly that Power Apps and Dynamics 365 licences aren't sufficient, and Learn's trigger troubleshooting page (August 2026) repeats that. The licensing deep dive, updated in October 2026, is the newer page and the one that sets out the licence rules, so this guide follows it. It says a Power Apps Premium or Dynamics 365 licence does include premium connectors for a cloud flow that is in context of the app the licence comes from and associated with it. A flow that has nothing to do with the app needs Power Automate Premium. For a flow that isn't tied to an app, all three pages agree.

The pages also differ on Microsoft 365. The deep dive's comparison table lists premium connectors as not included with a Microsoft 365 licence, and the opening section of Learn's licensing FAQ says the same. The FAQ's own table of seeded licences, updated in September 2026, makes one exception: Dataverse for Teams environments. This guide follows the newer deep dive. If your flow is in a Dataverse for Teams environment, read the FAQ's table as well.

Microsoft's enforcement page adds that some flows count as in context automatically: a Power Apps licensed user's flows that are triggered from a canvas app, or that use Dataverse's trigger for a selected record in a model-driven app. If your flow exists to support an app, associating it with that app may be the right answer rather than a new licence. Learn doesn't say whether associating a flow clears this message at save time, so check it in your own tenant.

Check your licence first

Microsoft's licence types page says you can see your own entitlements in the Power Automate portal: open the settings menu and choose the option to view your licences. Per that page, the list shows three things:

1. The user licences you hold, such as Free, Premium or a trial.
2. The capacity licences and add-ons in the current environment, such as Process licences.
3. What you're entitled to in this environment, each with a green check mark.

If you hold only Free or a Microsoft 365 licence, one of the fixes below is needed. An admin can also see licences in the Microsoft 365 admin center, on its licences page under billing.

Who needs the licence

The person who sees the message needs the entitlement for that change. Who needs it for the flow to keep running depends on the flow's type. The first two rows come from Microsoft's licensing FAQ; the co-owner row comes from the troubleshooting articles and the licence types page:

Two more points from the FAQ. People who only respond to approval requests don't need Premium. And whose connections the flow uses doesn't decide who needs a licence; the flow's type does.

The three fixes

The troubleshooting article still names the "Per User" and "Per Flow" plans. Those are legacy names. Microsoft's licensing deep dive says Power Automate Premium replaced the Per-user plan and Power Automate Process replaced the Per-flow plan. Licences already bought under the old names still work, but Microsoft says not to renew them. Another Learn troubleshooting page, on triggers, gives the same mapping in brackets.

Power Automate Premium: licence the person

Premium is a user licence. Microsoft's licence types page says it lets the user create, run and share unlimited cloud flows with standard, premium and custom connectors, within action limits, and also covers attended desktop flows. It's bought from Microsoft's pricing page, or by an admin in the Microsoft 365 admin center. For prices, see Microsoft's pricing page; our Power Automate licensing guide compares the options.

Choose Premium when one person builds or owns premium flows, or when a small, known group runs an instant flow.

Power Automate Process: licence the flow

Process is a capacity licence. Assigned to a cloud flow, it lets that flow use premium and custom connectors whatever licence its owner or the person running it has. Each Process licence gives the flow 250,000 actions a day. The steps, per Microsoft's documentation:

1. The flow must be in a solution. Only solution flows can be given Process capacity. To add an existing flow, open the solution in the Solutions area and add the existing cloud flow to it. Our guide to moving a flow into a solution covers the errors that step can raise.
2. An admin assigns Process capacity to the environment the flow is in.
3. On the cloud flow's details page, edit the flow's details, change its plan to the Process plan, and save.

Choose Process when many people run the same premium flow, or when the flow needs to keep working without depending on one person's licence. Microsoft's licence types page adds a limit: capacity licences don't replace user licences, because some essential tasks, such as creating automations, are available only to licensed users. And the FAQ says a Process plan doesn't replace the Power Apps or Dynamics 365 licence people need to use an app.

The 90-day trial

Per Microsoft's licensing deep dive, a user can start a Power Automate trial from inside the portal, and it lasts 90 days. The licence types page says it gives the same capabilities as Premium, except AI Builder credits and storage. After it ends, the troubleshooting article says, you need a paid plan to run or edit flows with premium connectors.

Things that can stop the trial:

• Admins can turn self-service trials off with PowerShell. Microsoft says doing so also removes the existing trials of that type from every user in the tenant.
• The self-service trial isn't available in government clouds (GCC).

Global admins have another option: admin-managed trials of Premium, Process or Hosted Process, started in the Microsoft 365 admin center. They last 30 days and can be extended once.

It used to work

If the same person could save the flow before, the troubleshooting article says their licence may have expired. A trial that ran out is the common case.

Microsoft's enforcement page (September 2026) covers what happens to premium flows whose owner's trial or licence has expired, or whose owner has left. Admins are emailed and pointed to a licence report. They have 90 days to act. After that, creating, copying and restoring environments is disabled; after a further 90 days, other actions can follow, including suspending flows. Instant flows are judged at run time on the licence of the person who runs them, unless the flow has a Process plan.

Learn's licensing FAQ, updated the same day, describes a much faster step for the same two cases: the flow is slowed down, all its owners are notified, and it's turned off after 14 days if nobody acts. Neither page explains how the two timelines fit together, so don't count on the longer one; fix the licence as soon as the owners are notified.

If the owner left, our guide to changing a flow's owner covers handing the flow to someone licensed. For the Power Apps side of licence notices, see This app requires a valid Power Apps license.

A related case: suspended for attended RPA

A different message, with the same root cause, appears for cloud flows that run a desktop flow in attended mode. Microsoft's troubleshooting article for it describes:

• After you save the cloud flow, its status is suspended, it can't be triggered, and its run button is deactivated.
• The cause is that the owner has no licence with attended RPA. The flow checker shows the details and offers to start a 90-day trial, ask an admin for a licence, or buy one.

That article (dated May 2023) also suggests giving the flow a per-flow plan from the flow's details. Microsoft's licence types page, updated in September 2026, says otherwise, and this guide follows the newer page: when a cloud flow under a Process licence starts an attended or unattended desktop flow, the user whose connection runs the desktop flow still needs Premium, or another user licence that covers desktop flows. Its comparison table lists attended RPA under Premium, not Process. So for an attended step, plan on Premium for the person whose connection runs the desktop flow (in the 2023 article's case, the owner); a Process plan alone won't cover it. Our guide to whether Power Automate Desktop is free explains which desktop features need which licence.

The steps in this guide follow Microsoft's documentation as of 28 October 2026; we haven't run them in a tenant.

Sources

• Microsoft Learn: User doesn't have a service plan adequate for the non-Standard connection error
• Microsoft Learn: Types of Power Automate licenses
• Microsoft Learn: Deep dive on specific licenses
• Microsoft Learn: Power Automate licensing FAQ
• Microsoft Learn: When premium flows are subject to license enforcement
• Microsoft Learn: Process capacity
• Microsoft Learn: Troubleshoot common problems with Power Automate triggers
• Microsoft Learn: Cloud flow suspended due to missing the attended RPA capability