Power Automate Flows Created Outside Copilot Studio Not Appearing in Tools

 Update: I found the root cause.

After quite a bit of troubleshooting, the issue turned out to be related to the workflow's Plan, not the trigger, response action, environment, solution membership, or asynchronous response settings.

Here's what I found:

• Workflows created directly in Power Automate are assigned the plan:  The user running the flow
• Workflows created from Copilot Studio are assigned the plan:  Copilot Studio

In my case, the flow created in Power Automate worked correctly and could be added to the agent, but it did not appear in the Global Tools directory in Copilot Studio. The flows created from within Copilot Studio did appear.

Once I changed the workflow's Plan to Copilot Studio, the flow immediately appeared in the Global Tools directory.

One important note: changing the Plan to Copilot Studio appears to be a one-way operation and cannot be reverted.  Maybe save the workflow before changing.  Hopefully this saves someone else a few moments of troubleshooting.

This of course raises more questions for me about Consumption/billing, Tool discovery by the orchestrator, Environment export behavior and Future agent capabilities.  

 I am experiencing the same issue and wanted to share what I've found so far.

I initially created a flow directly in Power Automate (https://make.powerautomate.com/). After that, I created a Copilot Studio agent (https://copilotstudio.microsoft.com/) and successfully added that flow as a tool. As the agent evolved, I created several additional flows directly from within Copilot Studio.

Later, when I reviewed the Tools directory in Copilot Studio, I noticed that only the three flows created through Copilot Studio were listed. The original flow, which was created in Power Automate and successfully added to the agent, was not present in the Tools directory.

To troubleshoot, I verified the following:

• Flow starts with "When an agent calls the flow"
• Flow ends with "Respond to the agent"
• Flow is in the same environment as the agent
• Asynchronous response is turned off
• Flow is published and functioning correctly

I also tested moving the flow into a solution, but that did not make a difference.

At this point, I'm leaning toward the possibility that flows created directly in Copilot Studio receive additional metadata or registration information that enables them to appear in the Copilot Studio Tools directory, whereas flows created directly in Power Automate do not. That is the next area I plan to investigate.

If anyone has found a way to make Power Automate-created agent flows appear in the Copilot Studio Tools directory, I'd be interested in hearing about it.

Good luck, and I'll update this thread if I discover the root cause.

Hello Adhonai_KOUKA​ , I've just tried to replicate your setup. It worked for me. Sharing my results and observations:-

• A flow created in Power Automate can indeed be used in Copilot Studio (it doesn't have to an agent flow created straight within Copilot Studio)
• The flow once created and added to solution in Power Automate appeared immediately in Copilot Studio - there was no lag or sync time

Looks like you've done all the right things e.g. the trigger, last action, environment. May be worth checking the below points

• In the Power Automate flow, in "Respond to the agent" action settings > Asynchronous response > Off
• In the Power Automate solution, "Publish all customizations" is clicked.
  • Note that in my case, the flow is in a separate solution of its own. For the agent, I have not even created a solution at this point.
• In Copilot Studio, look for the flow under "Add tool" > "Workflows" (not in "Add new - Workflows)

If this is still not working, I'd recommend to check if this is some kind of incompatibility with the actions inside the flow. In my case, it is a very simple flow that I set up just to test this scenario.

Below is the reference I used (probably you've done the same)

https://learn.microsoft.com/en-us/microsoft-copilot-studio/flow-modify-use-with-agent