Hi Vektori,
What you're hitting is almost always the publish/approval pipeline rather than the icon upload itself. A Copilot Studio agent surfaced in Teams is technically a Teams app, and once it has been approved in the Teams Admin Center the app metadata (including the icon) is cached at three different layers — Copilot Studio, Teams Admin Center, and the Teams client. Updating only one layer leaves the old icon in place.
The supported end-to-end refresh path
- Update the icon inside Copilot Studio → open the agent → Channels → Teams and Microsoft 365 Copilot → Edit details → upload the new color icon (192×192 PNG) and outline icon (32×32 transparent PNG). These dimensions are required by the Teams app manifest; off-spec icons silently fall back to the default. See Add a copilot to Microsoft Teams and the Teams app manifest schema.
- Publish the agent again in Copilot Studio. Channel/details changes only take effect after a fresh publish — this is the most common reason icons appear "stuck."
- Re-submit to the Teams admin catalog. In the same Teams channel pane, use Availability options → Show to my org by submitting to admin, or download the updated app package and re-upload it in Teams Admin Center. The Microsoft 365 Copilot channel has its own publish step — see Connect and publish agents to Microsoft 365 Copilot.
- Have a Teams admin approve the updated version in Teams Admin Center → Manage apps. Updated app metadata (including the icon) won't propagate to end users until the new version is explicitly published/approved in the catalog. Reference: Manage apps in the Microsoft Teams admin center.
- Clear the Teams client cache on at least one test machine before judging the result. Sign out of Teams, quit fully, delete the contents of
%appdata%\Microsoft\Teams (classic) or %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache (new Teams), then sign back in. Steps: Clear the Teams client cache.
Why manually editing the zipped app package doesn't work
When the agent is managed by Copilot Studio, the authoritative manifest is the one Copilot Studio generates on publish. A hand-edited package re-uploaded through Teams Admin Center will be overwritten the next time the agent is published from Copilot Studio, which is why the old icon keeps coming back. The documented path is to make the change in Copilot Studio's Edit details pane and publish — not to edit the package directly.
About the "Built with Power Platform" / Microsoft 365 Copilot surfaces
Those are separate channels with their own publish/approval cycle. After step 2 above, also re-publish to Microsoft 365 Copilot from the Channels pane, and expect a propagation delay on the Copilot/Teams Store side — this is documented behavior, not a bug. See Connect and publish agents to Microsoft 365 Copilot.
If after all five steps the admin sees the new icon in Teams Admin Center → Manage apps → [your agent] → version history but end users still see the old one, it's a Teams client cache issue and step 5 is the fix. If the admin doesn't see a new version listed, the publish in step 2 or the submission in step 3 didn't go through and that's where to focus.
Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!
Raghav Mishra — LinkedIn | PowerAI Labs
