Power Automate Licence Update

You may or may not have seen a message centre post or other Microsoft learn articles recently regarding updates to Power Automate licences.

Essentially, Microsoft seem to be cracking down on flows which are not associated with a properly licenced user with premium connectors, or is not directly linked to a Power App. MS will be turning off flows which are not licenced properly on the 24th October.


Power Apps Premium (aka Per User) licences provide the usage rights for flows that associated with the built app. This means you do not need to buy a Power Automate Premium licence for every user too.

If you have flows which are triggered independently of an app (and use premium connectors), the users will need a Power Automate Premium licence, or you need to buy a Power Automate Per Flow/Per Process licence.


There never was a way to directly associate a flow with an app and if you use ALM, flows in non dev environments are likely owned by service principals.


You can run a script to find all flows which will be suspended here.

If your flows legitimately are associated with a PowerApp, you can follow the process to associate the app here.

You can do this in your dev environments and your downstream environments should have this association included.

You can complete this association en masse using a PowerShell command found here.

It also doesn't appear to mark any flows as suspended when Dynamics first party apps are installed in an environment such as Sales or Customer Service.  This may change later though.

oh the joys of Microsoft Licensing :-)


I had a call with Microsoft on this point and they have supported the information above.  If you have an application and all users have Power Apps Premium, related flows can be associated and no Power Automate Premium is required.

It is important that the flows are linked to a legitimate app and not, for example, a blank Power App as this could constitute multiplexing.

Per Process licences are like Per Flow but include unattended RPA capabilities too.  These would be allocated to individual flows and now service principals or environments.


Popular posts from this blog

Assigning Windows 10/11 Enterprise Subscription Activation Licences to Hybrid Azure AD Joined Devices

Autopilot Hybrid Azure AD Join with Customised First Login Status

Upgrade Samsung Galaxy Ace 2 (I8160) to Android Jelly Bean