Power Automate per Flow usage problem

(0) Share

Report

Posted on by JasuDK

Hi all!

Hope someone can shed some light to a problem I have 🙂

For the record: Using this license type for the first time.

We have purchased "Power Automate per Flow" -license (the one where you get those 5x licenses in a "bundle").

To my understanding you can use this license type to license flows to use premium connectors without having to license all the users using these flows.

We created a Production environment to which we allocated all those 5x licenses.

Now when we create Flows to this Production environment and try to allocate these licenses to individual flows like this:

(here I am telling a flow to use one of those Per-flow plans)

Now when we put a premium connector like HTTP inside of this flow we get error:

(that HTTP action is a premium feature)

Are we doing something wrong or why doesn't the flow see that it is licensed for premium?

To sum it up:

1. We have a Production environment

2. 5x "Power Automate per Flow" -licenses are allocated to this environment

3. We have created a Flow to Production environment to which we have allocated 1x of those licenses

--> We get error stating that we don't have a premium license when trying to use a premium connector inside this flow

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (1)

Pstork1 68,678 Most Valuable Professional on at

Like (0)

Report

Re: Power Automate per Flow usage problem

Does the maker creating the flow have a premium license? The per App and per Flow licenses are good for the user's you share the flow with to be able to use the flow without a specific premium license, but the maker needs to have their own license in my experience.

Was this reply helpful? Yes No
JasuDK 9 on at

Like (0)

Report

Re: Power Automate per Flow usage problem

Hi @Pstork1 !
Thanks for your reply 🙂

Nope, the user creating the flow has "a standard O365 license" which has the basic PowerApps/PowerAutomate service plans.
This may very well be the cause behind this.

Somehow I interpreted the dreaded licensing guide so that the only license needed would be the "per flow" and the allocation of such license to individual flow(s) would take care of the part where Power Automate checks whether this flow is capable of premium features or not.

Was this reply helpful? Yes No
Verified answer

Pstork1 68,678 Most Valuable Professional on at

Like (0)

Report

Re: Power Automate per Flow usage problem

I think that is your problem. The per Flow and Per App licenses are assigned when an App or Flow are shared. So the flow has to exist before the per flow license can be applied. So in my experience the original maker must have a license that will cover any premium features. After that everyone else will be covered.

Was this reply helpful? Yes No
JasuDK 9 on at

Like (0)

Report

Re: Power Automate per Flow usage problem

Funny thing when you think of it:
In our case the flow goes like this:
1. SPO list gets a new item
2. Automated flow kicks in and does stuff
3. Only premium features in this automated flow are HTTP actions which make GraphAPI calls to Azure AD via oAuth (app registrated in Azure AD with some rights) --> No connections in the flow run under the end user context, they just use the SPO list.

Now under the hood the only function the "per flow" license has is to satisfy the Microsoft's licensing requirements (multiplexing).
Technically the whole thing would work with only 1x "Power Automate per User Plan" (for the user who creates the flow) because end users are not required to use their own credentials in the flow in anyway 😄

I understand that the "per flow" plan does it's job (covers the license usage for all) when your flow has connections where end users context is used. Like "Instant Flows".

But thanks for your answer. I'll mark it as a solution 🙂

Was this reply helpful? Yes No