Does using a Power Automate flow with HTTP connector still make the Power App premium?

(0) Share

Report

Posted on by Power Platform 1919

2,205 Super User 2026 Season 1

Hi everyone,

As part of my learning and experiments, I am trying to understand the licensing impact when using Dataverse with Power Apps and Power Automate.

I know that if we connect Dataverse directly inside a Power App, the app becomes premium.

But I am testing a different pattern where the app does not use Dataverse directly.

My setup is like this:

• The end user app is a standard canvas app.

• The user submits a request.

• A Power Automate flow runs, and this flow uses the HTTP connector to call the Dataverse Web API.

• The flow uses an application user in Dataverse and an Entra app registration.

• The app itself does not have any Dataverse connections.

When I tested this, the canvas app did not show as premium.

So I want to check if this approach still requires premium licensing for end users, since the HTTP connector is part of the flow.

Can someone confirm if:

This pattern keeps the app non-premium for end users, or

The premium licensing still applies because the flow uses a premium connector.

Thanks for your help.

I have the same question (0)

All responses (5)

Answers (2)

Verified answer

Pstork1 69,129 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Two points to make:

1) Since the HTTP connector is Premium using it in a flow invoked by the Power App will also make the App premium. Even if the designer doesn't enforce the Premium license it is still Premium. There are specific HTTP calls that can be made with things like the SharePoint connector, but they are restricted in what they can do. None of them will let you access Dataverse. So you would need to use the HTTP connector itself, which is Premium

2) More importantly designing things like this to bypass licensing costs is what Microsoft considers Multiplexing. Multiplexing is specifically called out as a violation of the license agreement. So even if the design didn't make the app Premium it would be a violation of the licensing terms to use it as a standard licensed app.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Power Platform 1919 2,205 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @Pstork1,

Thanks for your prompt response and detailed explanation.

I also thought the same, it has to be some type of misconfiguration or bug, which still shows the app as standard even though it is using premium http connector.

So I thought of checking with the community about the same

Was this reply helpful? Yes No
Power Platform 1919 2,205 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Just to add, @Pstork1 I have a additional question.

What if we use custom PCF inside the app, which does the same.

Will that still consider as Multiplexing?

Please note:

I am asking this as part of learning and experimentation

Was this reply helpful? Yes No
Verified answer

Pstork1 69,129 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Using a PCF control would also make the app premium. The best rule of thumb when dealing with multiplexing is to ask yourself why you are designing it that way. If its to avoid licensing costs then its probably multiplexing. Let me give you two scenarios that are similar, but one is multiplexing and the other isn't.

You have an App that needs to send an email with a file stored in Dataverse. To avoid licensing you have the app write a record to a SharePoint list. A flow is triggered by the new item in the list, which then collects the information from the list and the file from Dataverse and sends the email. The flow is premium, but the app is not because it only writes to the SharePoint list. This is Multiplexing.

But lets say you have a list that stores information in a SharePoint list. At the end of every month you have a flow that runs and archives entries that are more than 90 days old to Dataverse. Again the flow is Premium and the app is Standard. But this isn't multiplexing because its doing an administrative task that is not related to the individual actions of the user.

I hope those examples help.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Power Platform 1919 2,205 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @Pstork1,
Thanks for the examples. Now i can see the picture bit more clear and with clarity.

Was this reply helpful? Yes No