Answered

Delay in Changes Made to Copilot Studio Agent When Deploying to M365 or Teams

(1) Share

Report

Posted on by PR-10121437-0

Hello. Recently, after making changes a topic that I have in my agent made in Copilot Studio, when deploying the app to M365 channel to test the agent, I can't tell if my agent isn't working properly, or if there is a delay in the changes made to work properly in the agent within M365.

Is it common for changes made to an agent (specifically topics) to take some time before they are able to be recognized in the M365 channel?

If this is expected behavior, roughly how long should I wait before assuming there is an actual issue with the topic logic or deployment?

Categories:

Publish & channel management

General topics

Topic creation & management

I have the same question (0)

All responses (4)

Answers (2)

Sort by

MichaelFP 2,001 Moderator on at

Like
a
(2)

Report
Copy link

Link copied!

For M365 usually goes fast. Have you ticket the options "Force newest version"?

-----------------------------
If my answer helped you, please give me a thumbs up (👍).
If solve your question please mark as answer ✔️. This is help the community.
If you want talk with me just tag me @MichaelFP

Was this reply helpful? Yes No
Verified answer

chiaraalina 2,425 Super User 2026 Season 1 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi

Did you try uninstalling the agent in Teams and reinstalling it? That sometimes helps refresh the deployment.

Also, is it the same behavior in Teams for the web?

Honestly, I’ve had similar issue, sometimes the updates in Teams didn’t show up for several hours, or even a couple of days.

As the comment above mentioned, it works fast for M365.

Was this reply helpful? Yes No
Verified answer

deepakmehta13a 369 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi,

Yes, this is expected behavior. Changes in Copilot Studio don’t always reflect instantly in M365/Teams because of caching and channel sync delays.

Typically, updates should appear within a few minutes, but in some cases it can take 15–30 minutes. If it takes longer, try:

Republishing the agent (with “Force newer version for persistent channels”)

Removing and re-adding the app in Teams/M365

Starting a new conversation session

If after that the changes still don’t reflect, then it’s likely a configuration or logic issue rather than delay.

-------------------------------------------------------------------------------------------------------------------------------------------------

If this helps resolve your issue, please consider marking the response as Verified so it can help others facing a similar scenario.

If you found this helpful, you can also click “Yes” on “Was this reply helpful?” or give it a Like

Was this reply helpful? Yes No
PR-10121437-0 40 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you everyone.

I did already try "Forcing newest version", although that didn't work (at least in less than hours or days) within M365.

I usually deploy my agents to M365 always rather than Teams, although for scalable use I expect it to work for both.

Uninstalling the agent on my M365, then reinstalling, seemed to have activated some of the changes, although not all, in less than 20 minutes, so that's not bad!

Appreciate the input and support.

Was this reply helpful? Yes No