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 W...
Copilot Studio
Suggested Answer

Copilot Studio Agent Working Previously, Now Failing in Teams with Consent Prompt

(0) ShareShare
ReportReport
Posted on by Microsoft Employee
Hi,

We are currently working on a Copilot Studio agent within our sandbox environment. The agent was functioning correctly in Microsoft Teams until 6 February 2026. However, after publishing the agent and attempting to add or update it in Teams, we began encountering an error message stating “Something went wrong” during the installation process.

The error says: “There was a problem reaching the app.”


Despite this, the agent was successfully added at one point, and the welcome message was displayed. However, when selecting any of the available options, a consent box appeared (THIS IS NEW AND WE DID NOT ADD/ENABLE THIS). After accepting the consent, the following error message was shown:

“Something went wrong. Please try again.”
 
 
Something_Went_Wrong.png
Retry_error_while_adding_agent_to_Teams.png
Consent.png
I have the same question (0)
  • Valantis Profile Picture
    6,735 on at
     
    i have few question.
     
    did you try remove and readd the Agent to the channel?
    does it work within the web Teams version?
    Does it work with in the https://m365.cloud.microsoft/chat ?
  • VG-09020900-0 Profile Picture
    Microsoft Employee on at
     
    We tried removing and re-adding the Agent to the channel and publishing, and there was no change.
     
    It does not work within the web Teams version either. It gives the same errors.
     
    It does not work within https://m365.cloud.microsoft/chat .
  • RB-10022116-0 Profile Picture
    2 on at
    We seem to be having the same exact issues. And have drastic results in our monthly evaluations. 
  • TM-10022115-0 Profile Picture
    4 on at
    Hello, 
     
    confirming we are seeing this exact same issue in my org.
     
    We published a Copilot Agent a few weeks back and have published multiple revisions.  This worked until today when we started receiving the exact error.  We have performed all steps referenced from the OP.
     
    Could this be related to Issue ID CP1227436: 
     

     

    Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
     
     
    Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
    Issue ID: CP1229864
    Affected services: Microsoft Copilot (Microsoft 365)
    Status: Service degradation
    Issue type: Incident
    Start time: Feb 9, 2026, 2:00 AM EST
    User impact
    Users’ Declarative Agents in Copilot aren't responding to prompts.
    Scope of impact
    Your organization is affected by this event, and some users of Declarative Agents are impacted. This information may be updated as our investigation continues.
    Root cause
    A portion of infrastructure responsible for Declarative Agents populating prompt responses isn't processing requests as efficiently as expected, producing an increase in latency and resulting in impact.

    Current status
    Feb 10, 2026, 2:39 PM EST
    To ensure latency has returned to standard service levels, we’re continuing our extended monitoring to verify the issue is fully remediated.
    Next update by:
    Tuesday, February 10, 2026 at 10:00 PM EST
    Untitled.jpg
  • dmahendranme Profile Picture
    7 on at
    Confirming we are also facing same issue
     
    It was working few hours back and stopped working now. 
     
    Glad we are not alone 
  • Suggested answer
    TM-10022115-0 Profile Picture
    4 on at
    Just wanted to follow up on this as the service appears to have been restored on the MSFT side of things.
     
    I will say that I forced an update of the Teams desktop app this morning, however the issue was originally encountered in both the web and app version of Teams.
     
    Perhaps related to the various CP related tickets referenced by MSFT Service Health over the past week or so.
     
    TM1218513
    CP1227436
    CP1229864
     
     
    Awaiting a true root cause from MSFT engineering.

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