FlowMakerConnectionBlocked - Getting this error when running our CoPilot Studio Agent

(2) Share

Report

Posted on by BJ-01070631-0 Microsoft Employee

Today onwards , we are facing the below issue when running our CoPilot Studio Agent ( formerly called Power Virtual Agent ).
Error Message: The flow with name <FlowName> is using a maker connection, which is not allowed. Error Code: FlowMakerConnectionBlocked .

Any suggestions on how this can be resolved?

Categories:

General topics

I have the same question (1)

All responses (7)

Answers (0)

Sort by

Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @BJ-01070631-0

My suggestion would be to recreate the connection. However, I have a question or 2.

Note that you cannot have an Autonomous Agent that has a flow that is configured for Maker Connections, which would attempt to prompt the user for credentials, so you need to do #2 below so that your bot can use the flow in autonomous mode

1) was this an existing Flow that you attached as an Action (Tool) into your bot or

2) did you create this custom Action(Tool) so its essentially an "Agent" flow, versus a true flow, (which would be considered a Maker flow) and my guess is the connection is not compatible with your bots configuration, since the Tool.Action should run based on the advanced settings of the Agents activation.

Are you using service principals for instance in your flow, or DID you have a connection that was created by someone whom is no longer in the organization?

When you go into the Flow from Power Automate maker portal, does the flow look like works? Can you trigger it from there as a test?

Was this reply helpful? Yes No
milozhou Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi,

Have you solved this issue? I met the same issue when I migrate the solution to a new environment, even a blank flow could not be called from Copilot Studio side, but running it directly in Power Automate platform works well. I guess it's some DLP policy restriction? Thanks.

Was this reply helpful? Yes No
Suggested answer

Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @BJ-01070631-0

Did my suggestion to recreate the connection work?

The issue is that it is using the "flows" persons connection (hence why its called Maker) and its not valid to use that in your scenario.

@milozhou could be the same for you.

I do not use the connection or create it until I use it in Copilot so I have not yet had that issue.

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey

Was this reply helpful? Yes No
JW-12082156-0 2 on at

Like (0)

Report
Copy link

Link copied!

@Michael E. Gernaey have you found a solution for this. I have the same issue but it only appears in Prod environments. In there, I am not even able to trigger an empty flow that was created from within the agent. I can test it through the test flow feature in MCS, but when the agent tries to trigger it I get this error:

"Error Message: The flow with name [Name] is using a maker connection, which is not allowed. Error Code: FlowMakerConnectionBlocked Conversation"

Was this reply helpful? Yes No
dibhalla Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Did you get any fix for this?

We have set up an Agent that triggers an Agent Flow using a topic. When testing the flow directly, it works fine. However, when calling it from the Copilot Studio Agent, we get the following error:

"The flow with name <FlowName> is using a maker connection, which is not allowed. Error Code: FlowMakerConnectionBlocked."

I tried setting up the connection using a service account and even recreated it, but the issue persists. Interestingly, this problem occurs only in one of our production environments, while the same setup works fine in another production custom environment.

Was this reply helpful? Yes No
Suggested answer

CU25080421-4 Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Modified all the flow to run as run only user, after a new preview release, in production environment, only end user credential will support for running agent in Copilot Studio for security purpose.
Block the use of maker-provided credentials for authentication | Microsoft Learn

Was this reply helpful? Yes No
Suggested answer

Niraj Singh 6 on at

Like (1)

Report
Copy link

Link copied!
In the Power Platform Admin Center, go to Environment → Settings → Features.

There you’ll find the setting Control maker credential options.

By default, this is disabled for maker connections, which means flows can only run using end-user credentials. As a result, each flow must be executed by the "run-only" user.
Find the Microsoft release documentation:
Link: Block the use of maker-provided credentials for authentication | Microsoft Learn

Recommend first trying to run the flow using the SPN account.
If that doesn’t work and the issue continues, ask your tenant admin to enable this setting.

Currently, this restriction applies only to production-type environments.
👉 Hope this helps!
If these suggestions help resolve your issue, please mark the answer as helpful and consider giving it a like.

3 people found this reply helpful.

Was this reply helpful? Yes No