Add a Power Automate agent flow as a Copilot Studio tool

Copilot Studio can call a Power Automate agent flow as a tool. This integration is different from publishing a general remote Model Context Protocol (MCP) server: an agent flow is added to its Copilot Studio agent through the supported flow trigger and response action.

Add an agent flow to Copilot Studio

The flow must use the When an agent calls the flow trigger and a Respond to the agent action. Configure the response to run synchronously, publish the flow, and keep it in a solution in the same Power Platform environment as the agent.

In Copilot Studio, open the agent’s Tools page, select Add a tool, and choose Flow. Select the published agent flow and review its description so the orchestrator can determine when it applies. If a flow isn’t listed, verify that it has the required trigger and response action.

Design for the response limit

The flow must return a response to the agent within the 100-second action limit. Keep the work needed for the answer, such as required queries and result data, within that limit, and test with representative data. Actions placed after Respond to the agent can continue after the agent receives its response, up to the flow’s run-duration limit. That can help separate a short user-facing response from longer follow-up work, but it doesn’t make the agent wait for that follow-up to finish.

For example, an order-status flow could accept an order number and return a small set of fields the agent needs to explain the status. Give the flow a clear description, validate its input, and verify that the returned values support the answer. For actions that change records or trigger a consequential process, use the appropriate permission checks and confirmation steps.

When you need an MCP endpoint

Adding a Power Automate agent flow to Copilot Studio does not create an MCP endpoint for other clients. Microsoft documents remote MCP servers from Azure Logic Apps Standard workflows as a separate preview feature. If the requirement is for an MCP client such as Visual Studio Code to connect to a remote workflow server, evaluate that Logic Apps feature and its preview terms rather than treating an agent flow as an MCP server.

Sources

• Add an agent flow as a tool to an agent, Microsoft Learn
• Modify an existing flow to use with an agent, Microsoft Learn
• Create remote MCP servers from Standard workflows, Microsoft Learn