Copilot Agent Publication To Teams Store

Question

We have created a simple agent in Copilot Studios to answer org related question base on org KB. While logical changes make in copilot studioes show up in teams any changes made to the agent details or the change in version number dose not come into effect no matter what we do. I have republished the application serveral times. Deleted the app from teams admin center and resubmitted it servarl times as well. The changes just dont appear. I have also clear teams cashes and other app data in the hopes to see a change to the details. The version number dose not change, the description dose not change, the icon and logo do not change. Please help any as i dont know what to try next to fix this issue.

Answer 1

Hello @Hassan Askari,
After publishing a Copilot Studio agent to Teams, logic or KB changes may reflect, but agent metadata like version, description, icon or logo often does not update due to Teams app packaging, admin approval requirements, and backend caching. Updating app details typically requires resubmitting the agent for admin approval, and republishing alone may not apply these changes in Teams. In cases where the ZIP package was manually uploaded, Teams also requires a higher version number in the manifest and a correctly structured package (manifest + icons at root) for updates to reflect. Additionally, Teams may continue to show older app details due to caching or propagation delays, even if publishing was successful.

Answer 2

Changes to agent details (icon, description, version, etc.) and how they appear in Teams and the Teams Store are controlled by the publication and admin-approval flow, plus some known caching behavior.

Use the following checks and steps:

1. Confirm which changes require re-approval
   • Updating agent details (icon, descriptions, name, etc.) requires a new admin approval. After changing these details in Copilot Studio, submit the agent again for approval.
   • Content-only changes (topics, logic, KB, etc.) can be republished without re-approval.
   • From the guidance: “You must submit a new approval request to update the icon and descriptions for agents that were previously approved… A new approval is only required if you modify the agent details.”
2. Verify admin approval is complete
   • After publishing to the Microsoft 365 Copilot and Teams channel with Organization (tenant) scope, the agent appears as a requested agent in the Microsoft 365 admin center / Copilot Control System.
   • An admin must approve the updated agent. Until that approval is completed, the Teams app store will continue to show the previously approved version.
   • If the agent is Organization scope and “doesn’t appear” or doesn’t update, check:
     • Admin approval status in the Microsoft 365 admin center.
     • That app policies in the tenant allow users to access the app.
3. Ensure access settings are not tightened after submission
   • After submitting the agent for admin approval, do not change the agent’s access setting to be less than “everyone in your organization.” Doing so can cause users to be unable to chat with the agent after installing it from the Teams app store or Microsoft 365 Agent Store.
4. Handle Teams caching issues
   • There is a known limitation where Teams can keep using a previously published version of the agent, even after republishing. This can affect configuration and what users see.
   • Workaround to force refresh:
     1. In the Microsoft Teams admin center, locate the agent app, disable it, wait a few seconds, then re-enable it.
     2. In Copilot Studio, turn off the Teams channel for the agent, save, then turn the Teams channel back on.
     3. Republish the agent so the latest version is available to Teams.
   • After that, sign out and back in to the Teams desktop app, or refresh the browser if using Teams web, to clear client-side cache.
5. Confirm the agent status in Copilot Studio
   • On the Publish page in Copilot Studio, open Make the agent available to others and check the status:
     • It should move from “Submitted” to “Approved” after admin action.
     • Once status is Approved, open the agent from there and share the approved version’s link to verify that the updated icon/description/version are present.
6. Validate scope and discovery behavior
   • For Organization (tenant) scope agents: once approved, they appear under Built by your org in the Teams app store and in the Microsoft 365 Copilot Agent Store.
   • If the app is marked Approved but doesn’t appear or doesn’t show updated details under Built for your org, this is typically a Teams caching issue; use the disable/enable and channel toggle steps above.
7. If the issue persists
   • If, after following the above (re-approval, Teams admin disable/enable, channel toggle, republish, and client sign-out/sign-in), the version and details still do not update, collect:
     • Agent ID
     • Time of last publish
     • Tenant and app details
   • Then contact Microsoft Support, referencing that Teams is serving a stale agent configuration despite re-approval and republish.

---

References:

• Connect and configure an agent for Teams and Microsoft 365
• Publish agents to Microsoft 365 Copilot and Microsoft Teams
• Assign and deploy agents for Microsoft 365 Copilot
• Publish agents for Microsoft 365 Copilot