Announcements
Teams chat, there’s only one persistent conversation thread between a user and a bot/agent. Deleting chat history or “resetting” does not create a new conversationId.Teams is designed to reuse the same conversationId for that bot–user pair, and even reinstalling the app won’t fire a new ConversationStart or create a new 1:1 thread.
This is by design for Teams’ persistent conversations (see Teams deployment guidance for Copilot Studio agents) and Bot Framework guidance to create the conversation only once and then store/reuse the conversationId:
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/
Hi,
In Microsoft Teams, a 1:1 chat between a user and a bot/agent is maintained as a single persistent conversation thread. Because of this design, actions like deleting the chat history or resetting the conversation do not generate a new conversationId. Teams continues to reuse the same conversationId for that user- bot pair and even reinstalling the app does not create a new thread or trigger a new ConversationStart event.
conversationId
ConversationStart
However, if your goal is to make the agent behave like a newly started conversation, you can achieve this from the Copilot Studio side by clearing the conversation context.
In our implementation, we handled this by Reset Conversation topic generally called by Start Over Topic. This redirects the flow to a dedicated topic responsible for resetting the session state.
Inside the Reset Conversation topic, we change the Clear variable values action which is default set to "Global variables for the current session" and select “Conversation history for the current session”. This removes the conversation context that the LLM uses to maintain continuity in the dialogue.
Once the conversation history is cleared, the agent no longer has access to the previous context, so the next user message is processed as if it were the first message in a new chat. As a result:
The same topics can trigger again just like they do in a fresh conversation
The agent provides the same responses as it would in a newly started chat in Copilot Studio test or the M365 Copilot interface
Previous conversation context no longer influences the response
So, while the Teams conversationId itself cannot be changed, clearing the conversation history for the current session effectively makes the agent behave like a brand-new conversation from the bot’s perspective. Additionally, if your agent uses variables that persist across the session, you can also clear Global variables for the current session in the same action. This ensures that any stored state or values do not carry over into the next interaction. Clearing both the conversation history and session/global variables can help guarantee a completely clean restart of the agent’s logic and behavior.
Just wanted to check in and see if everything is working now. If you still need any help, feel free to let me know.
Also, if the issue is resolved, it would be great if you could mark the answer as solved so others with the same question can find it easily.
Thanks and have a great day!
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.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Valantis 291
Vish WR 175
Romain The Low-Code... 146 Super User 2026 Season 1
