Building and customizing solutions using Microsoft 365 Copilot APIs and tools
Hello Blanco, Susana ,
The issue is likely caused either by a governance/visibility change (agent no longer assigned or visible in M365 Copilot) or an overwrite during publishing, as Copilot Studio currently has no rollback or version restore capability. Recovery options are limited—check admin logs and agent catalog to confirm if it still exists, attempt to recover knowledge sources if stored in Dataverse, or rebuild/redeploy using a backup (e.g., Copilot Studio copy).
As a workaround, you can republish your older Copilot Studio agent to Microsoft 365 Copilot via the Channels feature, though it won’t include recent changes.
If you have a Copilot Studio copy (even a month old), the supported path is:
A. Microsoft confirms publishing from Copilot Studio to M365 Copilot is GA and is done via the agent’s Channels experience (Teams/M365).
High-level flow:
- Open the agent in Copilot Studio
- Go to Channels
- Choose Microsoft 365 Copilot (or “Teams + Microsoft 365” depending on your UI)
- Submit/publish
B. Microsoft describes that admins can then review/approve/manage the agent in the Microsoft 365 admin center / Teams admin center.
The publishing model includes governance: admins review and approve, and the agent appears in the Agent Store/catalog for users to add/pin.
If your agent doesn’t show up, it’s often because it’s:
- not yet approved
- not assigned to you/a group
- not enabled via the relevant admin policies
Reference Document-
1.https://learn.microsoft.com/en-us/microsoft-365/copilot/agent-essentials/m365-agents-admin-guide
2.https://www.microsoft.com/en-us/microsoft-copilot/blog/copilot-studio/publish-your-microsoft-copilot-studio-agents-to-microsoft-365-copilot/
3.https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-edit-source
4.https://www.microsoft.com/en-us/microsoft-copilot/blog/copilot-studio/publish-your-microsoft-copilot-studio-agents-to-microsoft-365-copilot/