Why?
In one of my previous blog posts Power Automate: Flows within context of Power Apps, I already explained that Microsoft will enforce Power Automate licensing on Flows using premium functionalities. Here I also explained on how to associate a Flow within context in case Premium Power Apps licensing is enough. Now I recently started getting emails on several accounts with the “Flow turn-off alert“:
However the instructions in this email are not complete… there is another scenario where this Power Automate Flow could run “within context of Power Apps” 🔗. In that case the Power Automate Flows could be scheduled or automated without the need for a Premium Power Automate License, because the context of the premium Power Apps would be enough 🤑.
What?
As the deadline on Power Automate licensing enforcement is closing in on us, Microsoft fortunately created another way to associate a Flow within the context of aPower App. In the previous blog post Power Automate: Flows within context of Power Apps, I already explained the Power Shell way. This post is to explain the new in-product experience 💪👍.
How?
The most up-to-date instructions can be found at Associate flows with apps – Power Automate | Microsoft Learn. You can now just simply:
1) Open the desired Power Automate Flow details page. On this details page there is now a new section on the bottom right: Associated Apps. You can even find a deep link to Learn More about this functionality and its purpose:
2) Use Edit link the new section on the bottom right to associate the Power Automate Flow. We can even associate it with one ore more Premium licensed Power Apps:
This is another great step in empowering No-Code/Low-Code Citizen Developers to achiever more 😎!
