Copilot Studio

Copilot Studio agent works in Microsoft 365 Copilot but does not respond in Microsoft Teams

(1) Share

Report

Posted on by ML-28041305-0

Hello Microsoft Support team,

We are reporting an issue with a Microsoft Copilot Studio agent published to Microsoft Teams in our customer’s tenant.

Summary

We have created and published a Copilot Studio agent inside the customer’s Microsoft tenant. The agent uses SharePoint as a knowledge source and works correctly when used from Microsoft 365 Copilot. However, when the same agent is opened from Microsoft Teams, it does not respond at all.

The Teams app appears correctly in Teams, has been approved in Teams Admin Center, and can be found/opened by users. However, once opened, the agent does not show the initial greeting message and does not respond to any user message.

This behavior also occurs with a brand-new test agent that only contains a simple ping → pong topic, so the issue does not appear to be related to SharePoint, knowledge sources, prompts, generative answers, or agent logic.

Environment / configuration

Please find below the current setup:

Agent created in Copilot Studio inside the customer tenant.
Authentication is configured as Authenticate with Microsoft.
The agent is not configured as multi-tenant.
The agent is published to Microsoft Teams and Microsoft 365 Copilot.
The Teams app is visible in Microsoft Teams.
The Teams app has been approved/allowed in Teams Admin Center.
The same agent works correctly in Microsoft 365 Copilot.
The issue only happens in Microsoft Teams.

Troubleshooting already performed

We have already tried the following:

Confirmed that the main agent works correctly in Microsoft 365 Copilot.
Confirmed that the user can use the agent successfully in Microsoft 365 Copilot.
Created a brand-new minimal Copilot Studio agent with only a ping → pong topic.
Published the new test agent to Microsoft Teams.
Opened the agent from Teams using a private/incognito browser session.
Tested the agent as a personal Teams app, without making it broadly available to the whole organization.
Confirmed that Teams still shows no greeting message and no response to ping.
Checked that authentication is set to Authenticate with Microsoft.
Asked the tenant admin to enable Let users interact with custom apps in preview under Teams org-wide app settings.
Retested after enabling that setting, but the issue persisted.
Compared the behavior with another tenant, where a similar Copilot Studio agent does respond in Teams, even when the user lacks sufficient usage capacity/license. In that tenant, Teams at least invokes the agent runtime and returns a controlled error message. In this customer tenant, Teams does not invoke the agent at all.

Request

Could you please help us investigate why Copilot Studio agents are not being invoked from Microsoft Teams in this tenant?

Thank you.

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Nivedipa-MSFT Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!
Hello ML-28041305-0,
Possible cause: Teams is unable to access the bot runtime, which is often due to issues with channel registration, authentication/consent, or DLP settings in the customer’s tenant.

Recommended checks:

In Copilot Studio, review Analytics/Sessions to see if any Teams sessions are recorded. If none, the request isn’t reaching the bot.

Go to Channels → Teams, then remove, re-add, and republish the Teams channel.

Check Entra ID sign-in logs by filtering for the bot’s app to look for any failed or blocked token requests (including Conditional Access issues).

Verify Power Platform DLP policies to ensure the environment isn’t in a group that blocks the Teams connector.

Re-upload the Teams manifest from Copilot Studio in the Teams Admin Center, as the previous package might be outdated.

If you found the information above helpful, I would appreciate it if you could share your feedback.

Your feedback is important to us. Please rate us:

🤩 Excellent 🙂 Good 😐 Average 🙁 Needs Improvement 😠 Poor

Was this reply helpful? Yes No
Suggested answer

Valantis 4,803 on at

Like (1)

Report
Copy link

Link copied!

Hi @ML-28041305-0,

Nivedipa's checks are good starting points. Adding some more specific diagnostic guidance based on your exact symptoms.

The fact that M365 Copilot works but Teams doesn't even for a brand-new ping-pong agent tells us the bot runtime and agent logic are fine. The failure is happening in the channel delivery layer between Teams and the Azure Bot Service, not in Copilot Studio itself.

Step 1: Check Analytics sessions first. If zero Teams sessions appear, Teams messages are not reaching the bot at all. This is the key diagnostic.

If zero sessions: the issue is in the Teams channel registration or the Azure Bot Service Teams channel configuration. Go to portal.azure.com, find the Azure Bot Service resource created for this agent (search for bot registrations in the tenant), and verify:
- The Teams channel is enabled under Channels
- The messaging endpoint is correct and reachable
- The bot App ID matches what's in the Teams app manifest

Step 2: Check the Teams app manifest specifically. When Copilot Studio publishes to Teams, it generates a manifest with a specific Bot ID. If that ID doesn't exactly match the Azure Bot Service registration, Teams silently drops all messages without returning any error to the user. Download the manifest from Copilot Studio (Channels > Teams > Download manifest) and verify the bot ID inside the manifest JSON matches the App ID in the Azure Bot Service resource.

Step 3: Corporate firewall or proxy. Microsoft docs confirm that firewalls that perform traffic inspection can block Bot Framework message delivery. Since M365 Copilot uses a different endpoint than the Teams Bot Framework channel, this would explain why one works and the other doesn't. Ask the customer's IT team to verify that the Bot Framework endpoints (*.botframework.com, *.bot.framework.com) are on the firewall allowlist.

If all of the above checks out and Teams still doesn't invoke the bot, this needs a Microsoft support ticket with the Agent ID, Environment ID, Azure Bot Service resource ID, and a timestamp of a failing interaction. At that point only Microsoft can check the Bot Service logs on their side.

Ref: https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-add-bot-to-microsoft-teams

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No