Agent in Teams: "you cannot send messages to this bot"

(0) Share

Report

Posted on by Konrad

I built an agent in Copilot Studio and integrated it into MS Teams. The agent was working fine. But now I suddenly get the message “you cannot send messages to this bot” in the input line. However, I haven't changed anything on the bot itself. I also deleted the chat history and added the bot again via the URL from Copilot Studio. It then accepts the first question (e.g., “Hello bot”), but then the input line immediately turns gray and becomes disabled, and a message appears saying that I can no longer send messages.
What could be the cause? Is the problem to be found in the agent's topics? Or in other configuration parameters?

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Suggested answer

Romain The Low-Code... 2,876 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello : this case is always related to 2 option : "Credits" or "Rights"

1 : When you make agent in the studio it's not using credits copilot, when you go in teams it need some credit allocated to the agent by a Power platform admin.

2 Other it could come from sharing the agent / deploying the agent : user must be in the environnement user to be shared with or org deployed by an admin.

Since i understand you are the maker in copilot studio, it's not a right problem. It seem you don't have anymore credit on you'r agent :)

Was this reply helpful? Yes No
Konrad 85 on at

Like
a
(0)

Report
Copy link

Link copied!

I didn't know that Copilot Studio Agents use Teams credits, but I was wondering where I could set limits or view usage.
Unfortunately, I'm not the Power Platform administrator here at our company. What do I need to tell our administrator, what insight or information do I need, and what can he do? Is there an overview or help section that shows the limits per month for M365 Company Pro users or something similar?

Was this reply helpful? Yes No
Suggested answer

Romain The Low-Code... 2,876 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

hello :) sorry i mad a too quick answer.

It's not "teams credit" : it's copilot credit.

all is explain here : https://learn.microsoft.com/en-us/microsoft-copilot-studio/billing-licensing .

To make copilot studio agent inside copilot studio :

- you have a copilot 365 licence on top of you M365 licence

- or you activate copilot studio trial lience

- or you were given a copilot studio maker licence by an admin.

this allow to create agent in the dev studio.

Then when you want to use it outside of the dev : IA use "credit" : copilot credit.

Using in teams is "outside" of the dev studio so it need credits.

The company need to have one credit pack ( 200 Dollars / month for the smallest one )

If you are starting you'r journey with copilot studio i deeplly recommand this tutorial , it's made from people from this community : https://microsoft.github.io/agent-academy/recruit/

there is a licencing chapter :)

If it answer the question please mark the answer as green answer it's important for the community and search engine :)

Was this reply helpful? Yes No
Konrad 85 on at

Like
a
(0)

Report
Copy link

Link copied!

Many thanks for this insights :) Have a nice weekend.

Was this reply helpful? Yes No
Konrad 85 on at

Like
a
(0)

Report
Copy link

Link copied!

Okay, I had a chance to look at the credits—that's not it. Only 20 out of 25.000 credits have been used so far. So what else could it be that prompts an agent to make this blocking?

Was this reply helpful? Yes No
Suggested answer

Romain The Low-Code... 2,876 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

hello, are those credit allowed to the environnement where the agent is ?

Otherwise when i add this problem it was because the user didn't had anymore access to the agent (change of access in the environnement sharing group members)

I had this problem "one day" for another agent : i desinstalled the agent

: remove conversation history, then search the agent on the "..." of teams at bottom left, and on the agent use the "..." and use unsinstall.

Then to copilot studio side i published and use the new feature "force to publish to new version in the popup", i waited few minutes (coffee time :) ) and then take the link in canal settings to install again the agent.

The "..." uninstall existe only in the web part of teams (or only in the desktop one, sorry i m on phone atm :) )

Hope this help !

Was this reply helpful? Yes No
Suggested answer

Konrad 85 on at

Like
a
(0)

Report
Copy link

Link copied!

I compared the agent's bots.xml and configuration.json with a complete new agent, that works correctly.

Since there where no differences than the publish dates and version numbers, I think the solution was the "Remove agent conversation" in Teams and re-add it via the publish link.

Was this reply helpful? Yes No