The agent build with copilot studio works well on the "Test" but does not work properly in teams app.
Problem description :
I have created a bot in copilot studio and the bot responds and developed pretty well inside the copilot studio test environment.
Bot specifics :
- The bot has no knowledge uploaded.
- The bot Orchestration is disabled.
- The bot knowledge and web search is disabled too.
- Only topics are configured (basically just a bunch of triggers, conditions, actions etc.)
Version details:
Published version (Teams admin center) : 1.0.28
Installed version (Teams application) : 1.0.28
Result:
The bot works pretty well on the test environment inside copilot studio but in teams it does not work at all (giving weird answers that are not configured in topics).
Example :
The start conversation is configured as displayed above but on the teams I get no message at the conversation start (the trigger is not working inside teams), probably It's because when opening the bot in Teams, you're initiating the chat, not the bot. (This needs to be fixed because we need the bot to send a greeting message rather than user types something).
For example, if an user types "Cancel" the bot on the test environment will respond as displayed below.
When user responds with an answer, for instance with a "Yes". The conversation ends as shown below.
But on the teams app, after installing the bot nothing happens it starts with a blank chat.
When typed "cancel." it responds similar to copilot studio.
But, when the user clicks on "Yes". The response is bogus
(The question is trigger in the middle of the topic after many sequence of questions and if the user clicked yes for this question, on copilot studio test environment , the start message is again sent by the bot - see below).
But when user clicks "Yes" on the teams app then he is given with this response (a response that was used to test a week before and it keeps responding with same answer - this is not happening in the test environment on copilot studio.)
Rather as shown on the topics condition, when user clicks Yes it should be redirected to the conversation start topic which is the welcome message.
Additional details:
I have followed all the instructions on several links provided by microsoft for publishing an agent.
**Please let me know because this app must be released for all the users as soon as possible and with this issue we can't really launch the app outside test environment.
**
I am also attaching the manifest of the app for your reference if you need further details please don't hesitate to contact me and please reach out to me.
P.S: Changed the extension to .txt as .json is not supported file format to attach.
manifest.txt
Regards,
Jay
Microsoft Copilot | Other
2 answers
Sort by: Most helpful
-
-
Karan Shewale 170 Reputation points Microsoft External Staff
2025-05-23T04:09:28.9133333+00:00 Thank you for providing the details of the issue. Based on your description and some common troubleshooting steps, here are a few suggestions you might find helpful:
Troubleshooting Tips:
Welcome Message Not Appearing in Teams
Bots in Teams typically don’t send a greeting message by default. To enable this, you’ll need to implement proactive messaging.
Microsoft provides guidance on this setup here: [https://learn.microsoft.com/en-us/microsoft-365-copilot/extensibility/copilot-studio-agent-builder-publish](https://learn.microsoft.com/en-us/microsoft-365-copilot/extensibility/copilot-studio-agent-builder-publish) **Bot Showing Outdated or Incorrect Responses** This is often due to Teams storing an older version of the bot. You can try the following: Clear the Teams cache. Uninstall and reinstall the Teams app. Confirm your bot's manifest file is the latest and accurately reflects the published configuration. **Differences Between Test and Teams Environments** The test pane in Copilot Studio provides a clean environment, while Teams may retain previous context, permissions, or outdated logic. Ensure old topics or testing artifacts are not still present in your published version. **Manifest File Accuracy** Double-check that the manifest uploaded in the Teams Admin Center is the most recent version and is properly configured.
- Try a Fresh User Test
- Installing the bot on a different Teams user account can help identify if the issue is user specific.
Thanks,
Karan Shewale.
*************************************************************************
If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.
- Try a Fresh User Test