Unanswered

MissingAdequateQuotaPolicy when activating a Solution Flow via a PowerApps license

(4) Share

Report

Posted on by aussiejedi

We have a Power Automate Flow that is shipped as part of a Solution and which is associated with a Model Driven PowerApp that is also part of the Solution.

According to the licensing FAQ, (https://docs.microsoft.com/en-us/power-platform/admin/powerapps-flow-licensing-faq#are-full-power-automate-capabilities-included-in-power-apps-licenses) for Flows to be covered by a PowerApps license, 'flows will need to run within the context of the Power Apps application, which refers to using the same data sources for triggers or actions as the Power Apps application'.

Our PowerApp is model driven and so uses CDS as the data source. Our Flow is also configured with a Common Data Service (current environment) trigger - and so uses the same data source as the PowerApp.

To our understanding, the licensing for the Flow should be covered under the PowerApps license. However, a user who has just a PowerApps license is unable to 'Turn on' the Flow, or edit the Flow.

How can Flows whose licensing emanates from a PowerApps license be edited or activated by users with a PowerApps license?

Thanks,

David

Categories:

Using connectors

I have the same question (0)

All responses (3)

Answers (0)

Sort by

KymDupuis Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

When you say "However, a user who has just a PowerApps license is unable to 'Turn on' the Flow, or edit the Flow." this seems to suggest that you want those users not only to "use" the flow but have "ownership" or "admin rights" over that flow.

The power apps license gives allows users to trigger and interact with flows created by other after they have created the connection when they launch the app. This happens without additional intervention. They can also create new flows in this environment using premium connectors, assuming they have the "environment maker" security role.

However, the "turn on" and "modify" features are only available to the flow "owner" or to a user with "environment admin role" through the solution.

Does this help?

Was this reply helpful? Yes No
m3ngi3 725 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @KymDupuis,
I created a Solution with a Model Driven App as well as two Flows in it.
According to the license guide as long as the flow touches the custom tables from this solution --> the flows are to be considered "within the context" of the "app" and I can confirm that in DEV Environment the scheduled flows have been running successfully for weeks now (SQL Connector as well as Current Environment Dataverse Connector). No licensing issues in DEV Environment at all...

Today I exported the solution from DEV and imported into PRD Environment with sufficient Per App Passes assigned to it. I used a System Admin Account of PRD Environment to import solution and create the connections for the solution aware connection references:
...but:

You happen to to have any ideas? (this account is able to open the Model Driven App without any licensing notification which from my point of view extra confirms that there are enough App Passes assigned to PRD Environment)

Was this reply helpful? Yes No
PriyaKodukula Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

If automated or scheduled cloud flows are created to support the app and are in context of an app, link the flow to the app(s) using a PowerShell script. Once the flow is linked, a dependency is established between the app and the flow and they can be managed together. If the linked app is deleted or unused, the flow will be turned off.

Was this reply helpful? Yes No