Copilot Studio Agent isn't anwering as a Teams Chat but does within Copilot site in MS Teams

(0) Share

Report

Posted on by MR-21080721-0

Hi everyone,

I built a Copilot Studio agent (generative orchestration, "Authenticate with Microsoft") for internal processes and I'm trying to deploy it as a standalone Teams chat bot. I'm stuck and would appreciate any pointers.

Question

What can block a Copilot Studio agent from replying in a Teams 1:1 chat while the same agent works fine in M365 Copilot? Has anyone seen a session stuck at "Submitted" with 0 steps specifically on the Teams channel?

What works
- Copilot Studio test pane: full responses, topics trigger correctly
- Microsoft 365 Copilot: the agent responds correctly. Activity tab shows a completed session with 2 steps and the correct topic

What doesn't work
- Teams personal chat: I added the "Teams and Microsoft 365 Copilot" channel, published, and used "See agent in Teams" > Add. The agent appears in my Teams app bar and I can send messages, but it never replies. Not even the greeting.

What the Activity tab shows
- The first message from Teams did create a session, but with 0 completed steps and status "Submitted". Transcript and activity map are empty.
- Later attempts (including Teams web client) produced no session at all.

So the message reaches the agent, but no orchestration step ever starts, and nothing comes back.

Already ruled out
- Removed and re-added the Teams channel, republished, reinstalled: twice, on two different days. No change.
- Teams admin center > Manage apps: the agent doesn't appear (never submitted for admin approval, installed via personal sideload)
- App permission policies: not applicable, our tenant is on app centric management
- Power Platform admin center: no data policies block the agent
- Microsoft 365 admin center > Agents: status "Available", both Copilot and Teams channels listed, not blocked

Our tenant is not migrated to unified app management, so I checked both admin centers.

Thanks in advance"

Categories:

Publish & channel management

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (3)

Answers (0)

Sort by

bscarlavai33 782 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Session created but stuck at Submitted with zero steps is the signature of the auth handshake dying before orchestration ever starts. The message lands, the agent goes to get a token, nothing comes back, session never advances. That's why the transcript is empty rather than showing a failed topic.

Quickest way to confirm: switch Authentication to "No authentication" in Copilot Studio, republish, test in Teams again. If it answers, that's your culprit.

The usual cause with "Authenticate with Microsoft" is the sideload. A personally uploaded app doesn't carry tenant admin consent, so the token exchange has nothing to consent against. M365 Copilot works because it's already running inside an authenticated context and never needs that handshake.

Submit the app for admin approval in Teams admin center instead of sideloading and it should start answering.

Was this reply helpful? Yes No
Suggested answer

11manish 4,137 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

I would classify this as:

A Teams-channel execution/authorization issue occurring before Copilot Studio orchestration, rather than an agent/topic/generative-orchestration issue.
The Submitted + 0 steps telemetry is the strongest evidence.

Your next priority should be Entra authentication/Conditional Access + agent sharing, followed by a minimal "Hello" agent test. Microsoft specifically documents Conditional Access as a cause of agents being unresponsive on Teams, so that should be checked rather than assuming the Teams app installation is the problem.
And because you're using Authenticate with Microsoft, I would not manually configure an Entra SSO app or add an Authenticate node as a workaround. That authentication mode is designed to handle Teams authentication automatically.
If the minimal agent still produces Submitted / 0 steps for multiple users, while the same published agent works in M365 Copilot, I would treat the case as a Copilot Studio/Teams channel runtime or tenant-side issue and raise it with Microsoft, providing the environment ID, agent/bot ID, affected user, exact timestamp (UTC), Teams client type, session ID when available, and Activity-tab evidence showing Submitted / 0 steps. That evidence will be much more useful to Microsoft than simply reporting "the agent doesn't respond."

Refer:

https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-conditional-access

https://learn.microsoft.com/en-us/microsoft-copilot-studio/configuration-end-user-authentication

Was this reply helpful? Yes No
Suggested answer

Mohsin Ali 467 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @MR-21080721-0 - This seems to be an issue and is already discussed in following thread.

https://community.powerplatform.com/forums/thread/details/?threadid=240fa944-6193-f111-8075-3833c5e85ffd

There were quite some troubleshooting we did, so can you please have a look at it and see if anything works out for you.

Was this reply helpful? Yes No