[Content request]: Details on Power Automate Flows aren't fully supported as actions in declarative agents

[cristianoag]

Issue type

Update to existing content

Details

The documentation refers that Power Automate Flows as actions in declarative agents might not run reliably and might not return results. In fact they cannot be selected on the current interface and that is causing confusion with some customers. The issue is 100% reproduceable.

While creating a new M365 Copilot Declarative Agent using Copilot Studio, I followed these steps:

1. Navigate to Agents, select Copilot for Microsoft 365, and click Add to create a new agent.
2. Complete the basic configuration and create the agent.
3. Open the newly created agent’s properties, click Add an Action, select New Action, and choose New Power Automate Flow.

Everything proceeds as expected. I then create a simple Power Automate flow that receives a few parameters and sends an email, for example. After publishing the flow, I test it successfully everything works as expected.

However, when I return to the Add Action interface in Copilot Studio to select the newly created flow, it does not appear in the selection list. The counter indicates that one action is available under the Flow type, but I am unable to pick and select the flow I just created.

So it is not that the agents might not run reliably and not return results. They cannot even have power automate flows as agents. Can we please fix the text to mention that??

Subject matter expert

Lauragra

Priority

P3 - The request is medium priority and is not blocking.

Target publish date

No response

Approximate size of the work item

None

Additional details

No response

[cristianoag]

Suggestion for the text on the documentation:

Power Automate Flows in Declarative Agents – Known Limitations
Power Automate Flows are not fully supported as actions in declarative agents. As a result:

• Flows may not run reliably or may fail to return results when triggered.

• In some cases, newly created flows may not appear in the Add Action interface within Copilot Studio, even if the action counter reflects their presence.

Workaround

Currently, there is no direct workaround to ensure that flows consistently return results. However, you may improve trigger reliability by editing the description of the flow on the Flow details page outside of Copilot Studio before publishing.

This issue affects flows linked from any content source, including: SharePoint, Microsoft Graph connectors, Plugins

[KatyKoenen]

Pinged the Power Automate team internally to coordinate content updates.

[KatyKoenen]

The Power Automate team agreed to add a Known limitations section to the article Use Power Automate flows as plugins in Copilot for Microsoft 365 (preview)