Agent created in Copilot studio and published in Copilot not updating for users after republishing

Hi Tanya,

This is a common caching issue where published agent updates don't immediately reflect for end users. Here are the solutions:

Why This Happens

• Browser caching of agent configuration
• Microsoft 365 Copilot service caching
• CDN propagation delays for agent updates
• User session persistence keeping old version

Connect and configure an agent for Teams and Microsoft 365 Copilot This article provides detailed guidance on how to connect and configure your Copilot agent for Teams and Microsoft 365 Copilot. It includes steps on publishing your agent, making it available to users, and ensuring it appears in the Teams app store.

https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-add-bot-to-microsoft-teams

Quick Solutions

1. Force Cache Refresh

For users:

• Hard refresh: Ctrl+F5 (Windows) / Cmd+Shift+R (Mac)
• Clear browser cache for microsoft.com domains
• Incognito/Private browsing mode to test
• Sign out and back in to Microsoft 365

2. Publishing Best Practice

In Copilot Studio:

• Channels → Microsoft Copilot
• Unpublish first → Wait 2-3 minutes → Re-publish
• This forces a complete refresh instead of incremental update

3. Version Control Method

Change agent metadata:

• Settings → Details → Description
• Add version number: "v1.1 - Updated July 25"
• Re-publish - this often triggers proper cache invalidation

Systematic Fix

Step 1: Complete Republish 1. Copilot Studio → Your Agent 2. Channels → Microsoft Copilot → "..." → Remove 3. Wait 5 minutes 4. Channels → Add channel → Microsoft Copilot 5. Publish

Step 2: User Communication Send users this message: "Agent updated! Please: 1. Close all Microsoft 365 Copilot tabs 2. Clear browser cache (Ctrl+Shift+Delete) 3. Restart browser 4. Access agent again Updates should now be visible."

Step 3: Verification

• Test in incognito mode yourself
• Ask 1-2 users to test before announcing
• Check different browsers (Edge, Chrome)

Advanced Solutions

Admin-Level Cache Control

Power Platform Admin Center:

• Environments → Settings → Features
• Look for "App refresh" or "Cache management" options
• Reset environment cache if available

Alternative Publishing Strategy

For frequent updates:

• Create staging agent for testing
• Copy to production agent when ready
• Use different agent names for major updates
• Maintain changelog for user communication

Prevention Tips

For Future Updates:

1. Schedule updates during low-usage times
2. Communicate in advance to users
3. Test in private environment first
4. Use incremental rollouts for major changes

User Training:

Teach users to:

• Refresh browser when agents seem outdated
• Check for update notifications
• Report issues when responses seem incorrect

Security Settings Check

Verify these aren't blocking updates:

• Conditional Access policies caching user sessions
• Browser security settings preventing cache refresh
• Network proxy settings caching Microsoft 365 content
• Group Policy restricting browser refresh behavior

Immediate Action Plan

Today:

1. Unpublish → Wait → Republish your agent
2. Test in incognito to verify changes
3. Notify key users to refresh browsers

Going Forward:

1. Document your update process
2. Create user communication template
3. Test update propagation timing in your environment

The unpublish → wait → republish method is most reliable for forcing user cache refresh without requiring individual user actions

Thanks,  

Karan Shewale. 

*************************************************************************  

If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via [Microsoft Teams Developer Feedback] link. Click here to escalate. 

thank you for your detailed solution. However it seems the UI and system has changed alot since July 2025. Would there be any chance you could update this solution and publish again? Just trying to push my luck and thank you in advance.