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.

[Abhilash]

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.

[Srini007]

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

[Abhilash]

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

[FlyingTuga1]

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?

[oliverslingsby]

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

[ed101]

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/

[FlyingTuga1]

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. 

[Lewylln]

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. 

[ed101]

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?

[FlyingTuga1]

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.

[oliverslingsby]

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

[u6735118]

I received the message for all my flows several days ago. I have a dynamic 365 and power app premium license. It seems that it automatically choose the Dynamic 365 license which triggering the message. I solve it by making some changes to my flow, even some texts, then save again, the warning disappeared.

[SandeepAdode1]

Is there a way we can get a list of all the flows having this license issue? Maybe a PowerShell script? I got this message for just 5 flows spread across multiple environments, but i suspect more such flows having the same issue and can't go through the tedious job of going through that one by one. I read somewhere that we can get all the flows that needed attention using a PowerShell, but it isn't mentioned anywhere how to do that.

[RamaSpeaks]

Probably someone from Microsoft finds a way to extract more money from customers. It is always a risk involved with SaaS platform and its services as the provider can stop any service and can start charging or increasing existing fees at their will. If customer become more dependent on the platform, then the charges will also be increased at any time. Better to have the conventional method of custom applications developed, running in own server for better security, better cost and better control. SaaS is supposed to be much cheaper than perpetual life time licenses but they become greedy as time passes and start charging perpetual license cost even for per month SaaS cost, dissolving the very USP of it. We spent so much time in creating Flows, but now it says we have to buy Premium License per person.