Associate in context flows to an app

9th February 2023

In today’s post, I’m going over how you can associate those flows that fall within the context of a Power Apps solution, to those apps!

Lets talk licensing… YUP!

So, if you purchase and use Power Apps premium licensing, there are a number of Power Automate capabilities which are premium that you can take advantage of within the scope of your Power Apps license.

If you’re developing a Power Apps solution, where you have flows which have a design intention of supporting the power apps solution, these flows can sometimes be considered within the context of an app, where your Power Apps premium licensing covers these flows.

For more information on what is covered within a Power Apps license for Power Automate, check this out.

What Power Automate capabilities are included in Power Apps licenses?

So, for those flows which are licensed by a Power Apps license because they fall within the context of an app, we need to associate these to an app to create a dependency between the app and flows.

Configuring PowerShell for working with Power Apps

To find out how to configure PowerShell for working with Power Apps, check out this previous post where I explained it…

Hero and Featured apps in Power Apps Mobile – Low Code Lewis

Associating in context flows to an app

Now we’re ready to associate an in context flow to an app. You can do this using the following command.

Add-AdminFlowPowerAppContext -EnvironmentName <String> -FlowName <String> -AppName <String> [-ApiVersion <String>] [<CommonParameters>]

You can find your environment name and flow name in a flow url. These are GUIDs.

The GUID you will find after environments/ is the environmentName and the GUID you see after flows/ is the flowName, then you can find your appName GUID in the details of your app under App ID.

Run that command and you’ll tie your flows to the context of your app!

Removing flows from the context of an app

If you now want to remove the dependency between a flow and an app, you can use this command to remove app context from the flow in question 🙂

 Remove-AdminFlowPowerAppContext -EnvironmentName <String> -FlowName <String> -AppName <String> [-ApiVersion <String>] [<CommonParameters>]

Posted in Power Apps, Power Automate

Leave a Reply

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

This will close in 0 seconds