Authorization 403 Error When Workflow Is Invoked from Copilot Studio Agent

(0) Share

Report

Posted on by RS-22071500-0

Authorization 403 Error When Workflow Is Invoked from Copilot Studio Agent

The workflow runs successfully when tested directly in Power Automate.

However, when the same workflow is invoked through a Copilot Studio agent action, the execution fails with:

"You don't have permission to use this tool. You're signed in, but access to this resource is blocked. Error details: Authorization - 403."

The issue appears only when the workflow is called from the agent.

Requesting assistance to verify:
- Copilot Studio action permissions
- Connection references
- Environment security roles
- User context permissions
- SharePoint/List access

need your assistance my emp id 652344

error issue(bot)....

Categories:

Bot administration

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Sayali-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hello RS-22071500-0,

This 403 Authorization error usually indicates that the workflow is being executed under a different identity when called from the Copilot Studio agent than when it is tested directly in Power Automate. Since the flow runs successfully during manual testing, the workflow logic is likely valid and the issue is more likely related to permissions, connection references, or access rights of the user invoking the agent. Verify that the action is properly shared, all connection references are authenticated and configured correctly, the user has the required security roles in the Power Platform environment, and the user has permission to access any SharePoint sites, lists, libraries, or other resources used by the flow. Reviewing the flow run history and the detailed 403 error information should help identify the specific resource or permission that is being blocked.

Was this reply helpful? Yes No
CU17101014-0 6 on at

Like
a
(0)

Report
Copy link

Link copied!

hi, I have the same issue. I try with a very basic workflow (echo) so it'snt related with connectors

Was this reply helpful? Yes No
SC-29071900-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

hi - did anyone get a resolution for this? I have the same issue plus a similar issue with calling a new design agent from a PA flow

Was this reply helpful? Yes No