PowerLeap Logo

Copilot Studio Friction

Get notified when this record changes

One email when the status or the fix changes — double opt-in, no tracking, unsubscribe in every email.

Your flow doesn't show up as a tool in the agent

Mitigatedsince 8 July 2026

Last verified

Details & related

Assessment

Confidence
Confirmed officialConfirmed by Microsoft documentation or an official statement.
Severity
Blocking
Typical time lost
Hours

Identification

Agent flowsAll channels

Verification & changes

  1. Verified

    Doc check by human: CAT blog post and official flow docs re-read during seed migration; all four visibility conditions still documented.

  2. Change

    Provisionally approved by the Product Owner; external LLM quality review pending.

  3. Change

    Initial record created from the seed dossier (migration wave 1).

Related

Are you in the right place?

  • You built a flow for your agent, but it never appears in the agent's tool list.
  • The tool picker in Copilot Studio does not offer the flow when you select "Add a tool".
  • There is no error message anywhere — the flow is only absent.
  • The flow itself runs fine when you test it in Power Automate.

If instead the flow appears but fails right away with FlowActionBadRequest → see Flow fails with "FlowActionBadRequest". If instead the flow runs but stops after about 100 seconds → see Agent flow fails with FlowActionTimedOut. If instead you can't share a flow with a colleague → sharing an agent flow (record planned).

What's happening

Copilot Studio lists a flow as a tool only when four conditions are all true. The flow must start with the "When an agent calls the flow" trigger and end with "Respond to the agent". The "Asynchronous response" toggle on that respond action must be off. The flow must have been created inside a Power Platform solution, from Copilot Studio. And it must run under the Copilot Studio plan. Each condition is invisible: nothing warns you, the flow is only missing from the list. Picture a job board that lists an ad only when every mandatory field is filled. Incomplete ads never show, and nobody calls you.

For technicians

The official FAQ adds two more discovery traps. The "Flows" page in Copilot Studio shows only agent flows created in Copilot Studio. Power Automate cloud flows must be converted or managed there before they behave like agent flows. Desktop flows can't be called from agent flows at all, documented as of 2026-07-08.

How to fix it

Solution 1

Official workaround

Work through the four visibility checks in order

  1. Open the flow in the flow designer.
  2. Confirm the first step is the "When an agent calls the flow" trigger.
  3. Confirm the last step is the "Respond to the agent" action.
  4. Open the settings of "Respond to the agent" via its "…" menu.
  5. Set the "Asynchronous response" toggle to "Off".

✅ You should now see: a synchronous trigger/respond pair framing your flow.

  1. Confirm you created the flow from Copilot Studio, inside the agent's solution.
  2. If you created it directly in Power Automate outside a solution, recreate it as an agent flow from Copilot Studio.
  3. Confirm the flow runs under the Copilot Studio plan, not a standalone Power Automate plan.
  4. In Copilot Studio, open "Tools" and select "Add a tool".

✅ You should now see: your flow in the tool picker.

Check that it worked

In Copilot Studio, open your agent and select "Tools", then "Add a tool". Search for the flow by name. Expected: the flow appears in the picker, and you can add it to the agent.

If it didn't work

  • You are in a different environment. The picker only shows flows from the agent's environment. Check the environment name in Copilot Studio before anything else.
  • The flow still sits outside a solution. Moving it in afterwards is unreliable. Recreate it from Copilot Studio and copy the steps over.
  • You changed the trigger after creating the flow. Replacing the trigger breaks the required pair. Restore "When an agent calls the flow" as the first step.
  • It is a desktop flow. Desktop flows can't be called from agent flows. Rebuild the logic as a cloud-based agent flow.

Prevent it next time

  • Create every agent flow from Copilot Studio, inside the agent's solution, from day one.
  • Treat the trigger/respond pair as fixed scaffolding: build between the two ends, never remove them.
  • Check the environment name before you build anything new.

Evidence

  • Microsoft statementmicrosoft.github.io

    Microsoft's CAT team lists four reasons a flow is missing from the tool picker: no trigger/respond pair, asynchronous response on, created outside a solution, wrong plan.

  • Official documentationlearn.microsoft.com

    The official FAQ states the Flows page shows only agent flows created in Copilot Studio, and that desktop flows can't be called from agent flows.

  • Official documentationlearn.microsoft.com

    The official doc pairs the 'When an agent calls the flow' trigger with the 'Respond to the agent' action as the required scaffolding of an agent flow.