Unanswered

This flow will be turned off in 120 days because the owner doesn't have a premium license. Use the flow checker to keep it up and running.

(0) Share

Report

Posted on by Abhilash M abi

106

We are getting the below error message in every flows. We have "Microsoft Power Apps Developer Plan" and "Microsoft Office E3"

Error:

This flow will be turned off in 120 days because the owner doesn't have a premium license. Use the flow checker to keep it up and running.

Categories:

Using flows

I have the same question (0)

All responses (13)

Answers (0)

Srini007 3,327 Super User 2025 Season 2 on at

Like (0)

Report

Hi @Abhilash

Is your flow has the Premium featured things used? Then you need a premium license

Check below link for you reference

https://learn.microsoft.com/en-us/power-platform/admin/power-automate-licensing/faqs

If you find this reply helpful, please consider giving it a LIKE AND

If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION

Regards,

Srini

Was this reply helpful? Yes No
Abhilash M abi 106 on at

Like (1)

Report

@Srini007 I understood the premium required the additional license but how come it was working till now without any error?

Was this reply helpful? Yes No
FlyingTuga1 28 on at

Like (0)

Report

I have the same issue for 60+ flows, however I have D365 Sales Professional license, which I believe should include connectors to Premium connectors. Or am I wrong?

Was this reply helpful? Yes No
oliverslingsby 12 on at

Like (0)

Report

Hi, we have this same problem, we have been using flows for a long time and there has been no change in our licences but this morning I have had an email saying this same thing for a large number of flows.

Is this an error or has MS changed licencing requirements

Was this reply helpful? Yes No
Thenerdy 58 on at

Like (1)

Report

This might help a few from the link above:

Seems we have the same issue, reading this if you're using D365 and using powerautomate without any references to D365 tables or anything you will have to pay an extra license.

If you include a reference to D365 it should fall under that licensing with powerautomate and they have only just enable these notifications it seems...

More on costs:
https://powerautomate.microsoft.com/en-us/pricing/

Was this reply helpful? Yes No
FlyingTuga1 28 on at

Like (4)

Report

Thanks @ed101 ,

I contacted Microsoft as we couldn’t even edit our flows. According to Microsoft, when the trigger is dataverse there’s no issues (like when record is added, modified or deleted). However we have a lot of flows that run on a schedule and use dataverse/D365 tables, or https requests that are called from buttons on the toolbar and for these we had problems.

the problem gets sorted by associating the flow with one or more apps (click on the flow then on the bottom right corner you can associate it with app(s)). - sorry, no screenshot as I’m on my mobile.

hope this helps everyone.

Was this reply helpful? Yes No
Lewylln 2 on at

Like (0)

Report

This worked for me as well, exact same error, came into work Monday to a lot of emails. Why does associating an app remove the warning though? Doesnt make much sense to me.

Was this reply helpful? Yes No
Thenerdy 58 on at

Like (1)

Report

Thanks @FlyingTuga1 - here's the screen shot for everyone else.

The associating an app:
Seems to be working as the yellow marker disappears for us too.

Does anyone know the implication of association?

Was this reply helpful? Yes No
FlyingTuga1 28 on at

Like (1)

Report

According to Microsoft, if a flow is triggered by a premier connector the Power Apps Premier or D365 license are valid, and there's no need to associate with an app. However, if you have triggers like scheduler or https, then theoretically you would need to purchase the Power Automate Premium license.

This does not make any sense, as we have a lot of scheduled jobs or triggered by buttons on the Command Bar.
So apparently this is the workaround, however I don't understand how this prevent people from associate all the flows to an existing app.

Was this reply helpful? Yes No
oliverslingsby 12 on at

Like (1)

Report

Thanks all, adding an action involving dataverse to the flows appears to do the job based solely on the error across the top of the flow disappearing after this is done, I am adding the reference to the app as well just in case but the error goes before this and after the dataverse action is added even though the action will never be called

Was this reply helpful? Yes No