Microsoft plans to let agents published to Agent 365 act as connected agents inside Microsoft 365 Copilot Chat and declarative agents, according to a new Microsoft 365 roadmap entry. The feature, Roadmap ID 567670, is listed as in development with general availability targeted for August 2026.
The change is aimed at organizations building multi-agent workflows rather than single-purpose Copilot extensions. Agents already published to Agent 365 are managed through the Microsoft 365 admin center; once the new capability arrives, compatible agents can be selected as connected agents by people building solutions in Agent Builder or Copilot Studio.
Microsoft says an Agent 365 agent must implement the Agent2Agent (A2A) protocol to be eligible. A2A is an interoperability protocol for agents to exchange tasks, context and results, allowing one agent to delegate a job to another rather than merely call a conventional API endpoint.
That requirement matters because publishing an agent to Agent 365 alone will not make it automatically available as a connected component. Developers will need to expose the necessary A2A capabilities, while administrators will still control the published agent through the Microsoft 365 admin center.
Microsoft’s Copilot Studio documentation already describes A2A-connected external agents as part of its broader multi-agent model. The upcoming roadmap item appears to extend that model into Microsoft 365 Copilot Chat and declarative-agent scenarios, linking centrally managed Agent 365 agents with builders’ custom agents.
The roadmap lists Android, desktop, iOS and web as supported platforms, with worldwide availability in Microsoft’s standard multi-tenant cloud. It is marked for the General Availability release ring, though Microsoft’s roadmap dates are targets rather than firm delivery commitments.
There is no action for end users yet. Admins and developers planning around the feature should identify which existing Agent 365 agents could be useful as reusable services, then verify that their implementations support A2A before the planned August rollout.
The change is aimed at organizations building multi-agent workflows rather than single-purpose Copilot extensions. Agents already published to Agent 365 are managed through the Microsoft 365 admin center; once the new capability arrives, compatible agents can be selected as connected agents by people building solutions in Agent Builder or Copilot Studio.
A2A support is the key requirement
Microsoft says an Agent 365 agent must implement the Agent2Agent (A2A) protocol to be eligible. A2A is an interoperability protocol for agents to exchange tasks, context and results, allowing one agent to delegate a job to another rather than merely call a conventional API endpoint.That requirement matters because publishing an agent to Agent 365 alone will not make it automatically available as a connected component. Developers will need to expose the necessary A2A capabilities, while administrators will still control the published agent through the Microsoft 365 admin center.
Microsoft’s Copilot Studio documentation already describes A2A-connected external agents as part of its broader multi-agent model. The upcoming roadmap item appears to extend that model into Microsoft 365 Copilot Chat and declarative-agent scenarios, linking centrally managed Agent 365 agents with builders’ custom agents.
What it changes for Microsoft 365 tenants
For IT teams, the practical benefit is reuse. An organization could publish and govern a specialist agent centrally, then allow approved builders to attach it to other agents that need its particular capability. That avoids recreating the same integration, instructions and controls in every Copilot Studio project.The roadmap lists Android, desktop, iOS and web as supported platforms, with worldwide availability in Microsoft’s standard multi-tenant cloud. It is marked for the General Availability release ring, though Microsoft’s roadmap dates are targets rather than firm delivery commitments.
There is no action for end users yet. Admins and developers planning around the feature should identify which existing Agent 365 agents could be useful as reusable services, then verify that their implementations support A2A before the planned August rollout.
References
- Primary source: Microsoft 365 Roadmap
Published: 2026-07-17T22:12:56.6746119Z
Loading…
www.microsoft.com - Official source: support.microsoft.com
Loading…
support.microsoft.com - Official source: learn.microsoft.com
Loading…
learn.microsoft.com - Official source: microsoft.github.io
Loading…
microsoft.github.io - Official source: developer.microsoft.com
Microsoft 365 Copilot | Extend and Customize Copilot
Extend, enrich, and customize Microsoft Microsoft 365 Copilot. Explore Copilot extensibility options such as agents, API plugins, and Copilot connectors to expand AI-powered productivity, skills, and creativity.developer.microsoft.com - Official source: adoption.microsoft.com