Power Automate Licence Update

By -

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.

Background

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.

Problem

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.

Resolution

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 :-)

***Update***

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.

Comments

Post a Comment

Popular posts from this blog

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

By -
Image
Introduction Starting with Windows 10, version 1703, Windows 10 Pro supports the Subscription Activation feature, enabling users to “step-up” from Windows 10 Pro to Windows 10 Enterprise automatically if they are subscribed to Windows 10 Enterprise E3 or E5. The Subscription Activation feature eliminates the need to manually deploy Windows 10 Enterprise or Education images on each target device, then later standing up on-prem key management services such as KMS or MAK based activation, entering GVLKs, and subsequently rebooting client devices. It’s important to note that the Windows 10 Enterprise subscription activation is designed to “step-up” a device from Windows 10 Pro to Windows 10 Enterprise. Therefore, your device is required to have a Windows 10 Pro license activated as a baseline. For Windows 10 Enterprise Subscription Activation to function, there a several prerequisites which need to be in place. This blog is aimed for organisations which have Active Directory on premises an
Read more

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

By -
Image
There has been talk of Samsung working on an Android build of Jelly Bean for the Samsung Galaxy Ace 2 (I8160) for quite some time. A couple of leaked versions of the build have been available since the end of February and during March, but these contained various bugs as you might expect. On April 2nd, an official release was available on www.sammobile.com and available for install using KIES or OTA, but only for Portuguese customers on the TMN network.  This was curious as this network didn't actually sell the phone.  It could be a way of getting the early adopters to test this version before the big operators like Telefonica and Vodafone build and release a version themselves. There are many online guides on how to manually download the firmware and apply it to your device, but if you make the direct jump from Gingerbread (2.3) to Jelly Bean (4.1.2) you will likely have RAM issues. The gingerbread versions only allocated around 500MB for RAM whereas Jelly Bean needs more
Read more

Autopilot Hybrid Azure AD Join with Customised First Login Status

By -
Image
Introduction This is my flavour of deploying a customised HAADJ progress status, building on work by Joymalya Basu Roy's detailed article - https://joymalya.com/autopilot-hybrid-azure-ad-join-reworked-with-joy/ . The differences in my version are: Not using Active Setup to run the HAADJ retry process or Splash Screen as I found this didn't work as expected and I didn't want to add a registry item to affect all future logins with a reboot from the HAADJ process. Running the processes under the context of the SYSTEM account, but displaying status to the interactive user. Avoid the HAADJ process running again after the initial success. This provides a customised first login status which prevents the user from using the devices until Hybrid Azure AD Join from the Autopilot process. It's use is primarily for when the User ESP is configured to be skipped. Files This is my version of customised HAADJ which is built on work and guidance in blogs/articles from Michael Niehaus, S
Read more