SharePoint Button Web Part "Run Flow" Action Only Works in the Default Environment

Hello! I was setting up a new workflow for a customer and encountered a limitation with the button web part's "Run Power Automate Flow" option.

Background

The SharePoint Button web part has a built-in action type: Run Power Automate Flow, which accepts a Flow ID. This is a clean option for giving users a one-click way to trigger an instant/manual flow directly from a SharePoint page.

The Finding

When configuring the Button web part with Run Power Automate Flow, it appears that the flow must reside in the Default Power Platform environment for this action to work. Flows in non-default (department-level) environments fail silently with the following error:

Could not find flow '<flow-id>'.

Testing Approach

To isolate the variable, I did the following:

1. Took an existing instant flow and exported it from a department-specific environment, then imported a copy into the Default environment — so the logic was identical.
2. Created two Button web parts on the same SharePoint page:
   • Button A → Flow ID from the department-level environment copy
   • Button B → Flow ID from the Default environment copy
3. Both buttons were configured identically, with the only difference being which environment hosted the flow.

Result:

• ✅ Button B (Default environment) — triggered successfully
• ❌ Button A (department-specific environment) — returned "Could not find flow '<id>'"

The account I used for testing is the same one that created the workflows and also has site collection admin rights, so permissions should be a factor.

Related Behavior

This appears to be consistent with a known behavior of running an instant flow from a SharePoint list (from the List menu , "Integrate" -> "Flows" -> <workflow name>), where instant flows with manual SharePoint triggers must also reside in the Default environment to function correctly.

Both surfaces appear to share the same environment scope constraint when resolving flows by ID from a SharePoint context.

Questions for the Community / Microsoft

1. Is this a documented platform constraint for the Button web part's Run Power Automate Flow action?
2. Is this constraint expected to change, or is it by design?

Workarounds

In this case, I found two decent workarounds:

1. Instead of configuring the Button web part action as Run Power Automate Flow, it can be configured as Open Link, and then use the flow's direct run URL:
   https://make.powerautomate.com/environments/<environment id>/flows/<flow id>/run
2. Also using the direct run URL, enter that into a navigation link or regular hyperlink on the SharePoint page to launch the workflow run page. 

Any insight from the community or the product team would be appreciated — especially if there's a documented reference I may have missed.

Thanks!