← Al Davies, 250 High Street

Power Automate HTTP action says premium: do you need to pay?

Short answer: if the HTTP action in your flow shows the premium label, plan on a premium license. Microsoft's licensing FAQ says: "Users with the free plan or one of the Microsoft 365 license plans can only access standard connectors." For SharePoint work, check the action Send an HTTP request to SharePoint first. It belongs to the SharePoint connector, which Microsoft lists as Standard.

What Microsoft's pages say

The plain HTTP action is not on Microsoft's connector pages. Here is what Microsoft's pages, and one forum reply, say.

Which actions are not the same thing

Two actions have similar names. They are not in the same tier.

  1. HTTP: a general action that calls any web address. The forum reply above calls it premium.
  2. Send an HTTP request to SharePoint: part of the SharePoint connector. Microsoft's SharePoint connector page lists its class as Standard for Power Automate. Microsoft describes the action as "Construct a SharePoint REST API to invoke," and adds that it "may execute any SharePoint REST API you have access to. Please proceed with caution."

If the call only touches SharePoint, the second action may be enough. See "Send an HTTP request to SharePoint in Power Automate".

What the warning means in the designer

When a flow includes a premium connector, the person who owns or runs the flow needs the right license. The warning is Power Automate telling you about that rule. It does not change the flow. Our advice, not a Microsoft rule: read the warning before you share the flow with others, because the next section changes who needs the license.

Who needs the license

Microsoft's licensing FAQ gives these rules:

For an instant flow, Microsoft offers a second path: "instead of licensing every user, you can license the flow with a Process license." Microsoft's license types page says an assigned Process license "lets it use premium and custom connectors, no matter what license the owning or triggering user has," and that "Flows must be in a solution for a Process license to be assigned."

Microsoft's licensing overview says terms can change, and sends you to the Power Platform Licensing Guide and your licensing agreement for current terms. For a small team, see "Power Automate license for a small team".

No-cost swaps with standard SharePoint actions

Our advice, not a Microsoft rule: before you add HTTP, check whether a standard action does the job. For a SharePoint list, the SharePoint connector is Standard, and its actions cover list work.

  1. To read rows, use Get items. A list longer than 100 rows needs Top Count and Pagination set. See "Power Automate Get items only returns 100 rows".
  2. To change a row, use Update item.
  3. To read one row, use Get item.
  4. To create a row, use Create item.
  5. For a call that only SharePoint REST can do, use Send an HTTP request to SharePoint.

Exact names may differ on your screen.

Check your own flow

  1. Go to https://make.powerautomate.com and open the flow.
  2. Look at every action card. Note any that show a premium warning.
  3. Find out who owns the flow and whether it is automated, scheduled or instant.
  4. Ask your admin which Power Automate license that owner has. Microsoft says admins can see assigned licenses in the Microsoft 365 admin center at https://admin.microsoft.com/.
  5. If the owner has only a Microsoft 365 license and the flow has a premium action, either swap the action or ask your admin about a license.

A flow that already runs

Some flows may run for a while before anyone notices a license gap. Our advice, not a Microsoft rule: do not treat a flow that runs today as proof that it is covered. Ask your admin to confirm the owner's license.

If a flow stops after a license or connection change, see "Power Automate connection expired, flow failing" and "Power Automate flow turned off automatically".

When to get help

You can build all of this yourself in Microsoft 365. If you would rather have it built and tested for your team, I do that. A tracker like this is a fixed price: $5,000 for one, built in 2 weeks. See "What a SharePoint tracker costs to build". Bring one example of the problem to a free call.

Tell me what's still manual

I am Al Davies. I run 250 High Street LLC and build SharePoint trackers and Power Automate flows for operations teams. I work remotely. The first call is free, and I will not try to sell you anything.

See trackers I built: Tools I built

FAQ

Is the HTTP action premium in Power Automate?

A forum reply on Microsoft Q&A, from a moderator labeled Microsoft External Staff, says it is. That reply was about Copilot Studio, and Microsoft's connector pages do not list the plain HTTP action. Check the label on the action in your own flow.

Can I use the HTTP action with a Microsoft 365 license?

Microsoft says the free plan and Microsoft 365 license plans can only access standard connectors.

Is Send an HTTP request to SharePoint premium?

Microsoft's SharePoint connector page lists the connector as Standard for Power Automate.

Who needs the premium license for a scheduled flow?

Microsoft says that for an automated or scheduled flow with a premium connector, only the flow owner needs a Premium license.

Can one license cover a flow instead of every user?

Microsoft says a Process license assigned to a flow lets it use premium connectors regardless of the owner or trigger user. The flow must be in a solution.

Sources