web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / Copilot Studio agent i...
Copilot Studio
Answered

Copilot Studio agent in Teams: connector calls failing with "missing connection ACL" 403

(0) ShareShare
ReportReport
Posted on by 7

Starting 2026-05-27 ~03:30 UTC, our Copilot Studio agent stopped being able to invoke its custom connector from Microsoft Teams. The agent is reachable in Teams — conversational/system interactions work — but every connector tool call returns:

The connector returned an HTTP error with code 403.
Inner Error: Error from token exchange: Permission denied due to missing connection ACL
 

Setup: Custom connector with x-api-key, maker-provided credentials (I'm the connection owner), "Authenticate with Microsoft" Entra SSO. Agent and connection in the same Default environment.

Behavior:

  • ✅ Copilot Studio test pane works

  • ✅ Microsoft 365 Copilot channel works

  • ✅ Direct API calls work

  • ✅ In Teams, system topics ("Start over," "What can you do") respond fine

  • ❌ In Teams, any prompt that invokes the connector fails at the token-exchange step

  • ❌ The connection owner is also denied (not just end users)

  •  

Tried (none resolved it): republishing, re-adding the agent in Teams, deleting and recreating the connection from scratch (new GUID, same error).

Why I think this is service-side:

Another customer posted an essentially identical error today in a completely different setup — different tenant, managed Prod environment, built-in Azure Blob Storage connector, service principal auth:

https://learn.microsoft.com/en-ca/answers/questions/5903486/copilot-studio-agent-the-connector-azure-blob-stor

Two unrelated tenants, different connectors, different auth methods, same missing connection ACL token-exchange error in the Teams channel within hours of each other points to a Microsoft service-side issue, not per-tenant config.

Questions:

  1. Anyone else seeing this in the last 24 hours?

  2. Is there a related Service Health MO/IR advisory?

  3. Any known workaround?
I have the same question (0)
  • Verified answer
    TS-27052108-0 Profile Picture
    7 on at
    Issue resolved on its own with no configuration changes on our end. No Service Health advisory was ever posted. Strong indicator this was a transient service-side issue at the Copilot Studio connection token-exchange layer affecting the Teams channel specifically.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 244

#2
Romain The Low-Code Bearded Bear Profile Picture

Romain The Low-Code... 221 Super User 2026 Season 1

#3
Vish WR Profile Picture

Vish WR 196

Last 30 days Overall leaderboard