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 / Agent not working in t...
Copilot Studio
Answered

Agent not working in teams for all users

(0) ShareShare
ReportReport
Posted on by 2
Hello,
 
I have an agent built on the new version of Copilot studio.
 
The agent is currently deployed on Teams and Copilot 365 for 3 users.

For 2 of them it works fine on both Teams and Copilot 365, but for 1 user it only works on Copilot 365, when the user talks to the agent in Teams the bot appears to be "thinking" but then it doesn´t respond anything.
 
I´ve had this problem with another agent that only uses a Dataverse MCP.
 
Any fixes? 
 
Thanks everyone,
 
António.
I have the same question (0)
  • sannavajjala87 Profile Picture
    515 Super User 2026 Season 1 on at
    Hi António,
    Thanks for sharing the details , I’ve seen this kind of behavior before, and it’s usually tied to a user-specific issue rather than the agent itself, especially since it works fine for other users and in M365 Copilot.
    Based on what you described, the difference between Teams and Copilot execution context is often the key factor. Teams runs the agent slightly differently, so if your agent is using Dataverse MCP or any external tools, that specific user might not have the same connection state or permissions fully established in Teams.
    A few things I’d recommend checking:
    • First, confirm whether the user has the same Dataverse security roles and access to the underlying tables/entities used by the agent. Since you mentioned a similar issue with another agent using Dataverse MCP, this is a strong indicator of a permissions mismatch.
    • Ask the user to trigger the connection flow again directly in Teams. Even if it works in Copilot, Teams may require separate consent/connection initialization, and sometimes it fails silently instead of prompting.
    • Have the user start a completely new chat session with the agent (instead of continuing an existing one), or remove and re-add the app in Teams. This helps clear any stuck session state.
    • It’s also worth trying basic client-side resets like signing out/in of Teams, restarting the client, or testing in Teams web vs desktop to rule out caching issues.
    In most cases, this ends up being either a user-level permission gap or a connection/token issue specific to Teams rather than a problem with the agent configuration itself.
    Hope this helps point you in the right direction , let me know what you find.
  • ac21211 Profile Picture
    2 on at
    @sannavajjala87 
    Thanks for the answer
     
    For the first agent the only tool/knowledge I have is one sharepoint file.
     
    We´ve deployed new versions of the agent, reinstalled it on Teams, reset Teams completely and nothing seems to fix the problem.
     
    Regarding the Dataverse permissions, the user can talk to other agents that are in the same enviornment with no problem.

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 May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 277

#2
11manish Profile Picture

11manish 206

#3
sannavajjala87 Profile Picture

sannavajjala87 156 Super User 2026 Season 1

Last 30 days Overall leaderboard