Error creating a Simple Agent Flow "does not have permission to call route"

(2) Share

Report

Posted on by CB-12061822-0

So in Copilot Studio I've created a new blank Agent and am adding an Agent Flow.

When I go to add any action that interacts with Connections such as the Excel Get Worksheets Action I can't set any properties as I get this error

User with object id 'xxxxx' and scopes 'Flows.Manage.All, Flows.Read.All' does not have permission to call route 'GET/HTTPS:/PROVIDERS/MICROSOFT.POWERAPPS/CONNECTIONS'

This looks like an internal plumbing issue?

I'm admin in both Power Platform and CoPilot Studio.

I've found the 'Power Virtual Agents Service' and the 'Microsoft Flow Service' Service Principals but there is no visible way to assign permissions between them.

Anyone seen this before?

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (2)

Answers (0)

CU11070653-1 on at

Like (0)

Report

The error you're seeing typically stems from missing or geometry dash misconfigured permissions between service principals, especially when trying to access connections like Excel Online.

Was this reply helpful? Yes No
Suggested answer

DAnny3211 134 on at

Like (0)

Report
Hi, The error you're encountering — *"does not have permission to call route 'GET/HTTPS://PROVIDERS/MICROSOFT.POWERAPPS/CONNECTIONS'"* — typically points to a **missing or insufficient permission assignment** for the service principal that Copilot Studio uses to interact with Power Platform connectors. Here are a few steps to help resolve the issue: 1. **Check service principal permissions**: Ensure that the **Power Virtual Agents Service** and **Microsoft Flow Service** principals have the necessary API permissions in Azure AD. Specifically, they may require delegated or application-level permissions to access Power Platform resources like connections. 2. **Environment role assignments**: Even if you're an admin, verify that the **Copilot Studio agent** is operating in an environment where the required **connections are available and shared**. The agent must have access to the connection references, and these must be shared with the environment or user context under which the agent runs. 3. **Connection ownership**: If you're using a connection created by another user, ensure that it's shared with you or the environment. Alternatively, try creating a new connection under your own user account and use that in the agent flow. 4. **Known limitations**: There are some known limitations when using certain connectors in Copilot Studio, especially when the agent is trying to access resources across different environments or tenants. These scenarios may require additional configuration or support from your Azure/Power Platform admin. For further guidance, you may refer to: - Manage service principals in Power Platform - Copilot Studio and Power Automate integration - Power Platform environment roles and permissions Thanks and best regards, Daniele **Note: This response was prepared with support from Copilot to ensure clarity and completeness.**

Was this reply helpful? Yes No