SharePoint buttons can start Power Automate flows but still need sharing and the right environment
Reviewed by Helen Jones
Microsoft Support now documents a Run Power Automate flow action on the SharePoint Button web part. Page authors choose that action, paste a Flow ID from Power Automate, publish the page, and site visitors see a side panel to confirm connections before the flow runs. The same documentation states that adding the button does not share the flow or grant other people permission to run it. Authors must handle access separately. Community reports from early August 2026 say that in some tenants the Run Flow action only works when the flow lives in the default environment, even when the button is set up correctly on the page.
Until now, starting a departmental flow from a SharePoint page usually meant a link out to Power Automate, a form submission, or a list item change that someone had to remember to trigger. Makers who wanted a simple on-page button had no supported first-party path, so many processes stayed half manual. The button closes that gap in the interface, but it does not close the reliability gap. A published button can still fail for the next person who clicks it if the flow is not shared, if connections need consent, or if the flow sits outside the default environment. The feature moves the click onto the page. It does not remove ownership, permissions, or environment checks from the build.
Analysis
Treat this as a setup trap to clear before you promote any live process, not as a finished trigger. Take one non-critical shared flow you already trust, confirm it is in the default environment and that colleagues can run it, put its Flow ID on a test SharePoint page, and have someone who is not the owner click it once so connection consent and environment limits show up before real users depend on the button.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "SharePoint buttons can start Power Automate flows but still need sharing and the right environment", Collab365 Spaces. 2 sources referenced.