Copilot Studio agent updates not reflecting in Microsoft Teams but working in M365 Chat

Question

We are experiencing an issue where updates made to our agent in Microsoft Copilot Studio are not being reflected in Microsoft Teams, even after successful publishing.

Details:

• The agent is developed and published using Microsoft Copilot Studio.
• Changes (topics/knowledge/responses) are working correctly in the Copilot Studio test environment.
• The same updates are also working as expected in M365 Chat.
• However, these updates are not reflected in Microsoft Teams.
• The bot in Teams continues to respond with older logic/content.

Observed Behavior:

• Outdated responses are returned in Teams
• Newly added or modified topics are not triggered in Teams
• Behavior remains unchanged even after 24+ hours of publishing
• Same scenarios work correctly in M365 Chat.

Answer 1

Use the following checks and actions to resolve the mismatch between Microsoft Teams and Microsoft 365 Copilot behavior for the same Copilot Studio agent.

1. Confirm publish and versioning

• In Copilot Studio, verify that the latest version of the agent is saved and successfully published.
• Use versioning for suggested prompts and updates so it is clear which version should be active in Teams and Microsoft 365 Copilot.

2. Account for propagation delay and caching

• Updates to agents and suggested prompts do not appear immediately in Microsoft 365 Copilot or Teams due to caching and asynchronous propagation across regions.
• Even when publishing succeeds, Teams can continue to use older configurations for some time.
• If changes are not visible:
  1. Verify the agent is saved and published.
  2. Start a new chat session in Teams with the agent (do not reuse an existing conversation).
  3. Clear the Teams client cache or sign out and sign back in.
  4. Open the agent from Apps in Teams instead of a previously pinned or cached app.
  5. Allow additional time for global synchronization and app propagation.

3. Republish after configuration changes

• If any configuration (channels, authentication, knowledge sources, topics) was changed after the last publish, republish the agent to Teams.
• Teams app approval and visibility do not guarantee immediate usability; republishing is required after configuration changes, followed by propagation time.

4. Manage session lifecycle in Teams

• Teams conversations can hold on to older state and logic. To ensure the latest behavior is used:
  • Configure and use inactivity triggers and state-clearing options so old sessions do not persist outdated logic.
  • Provide a self-service command (for example, a topic that clears state or restarts the conversation) so users can force the agent to reload the latest configuration.
  • Instruct users to start a new 1:1 chat with the agent after major updates.

5. Validate in Microsoft 365 Copilot web first

• As a best practice, validate changes in the Microsoft 365 Copilot web experience (where they are already working in this scenario) and then focus troubleshooting on Teams-specific behaviors such as caching, propagation, and session persistence.

6. Escalate if the issue persists beyond expected windows

• If the agent still returns outdated content in Teams after:
  • Confirming successful publish,
  • Clearing Teams cache / signing out and in,
  • Starting a new chat from Apps, and
  • Allowing sufficient time for propagation, then open a support ticket with Microsoft Support. Include environment ID, agent ID, and timestamps of publish and test attempts to help investigation.

---

References:

• Configure suggested prompts for Teams and Microsoft 365
• Troubleshoot Store Operations Agent (preview)
• Troubleshoot Personalized Shopping Agent (preview)
• Known issues and limitations for the Employee Self-Service agent
• Deploy agents in Microsoft Teams