The April 2025 update focused on the release of the Multi-Agent Orchestration engine and the introduction of Agent-to-Agent (A2A) connectivity, allowing agents to work together as a unified system.
Real-time User Journey: Collaborative Multi-Agent Resolution
The core journey introduced this month involves “handoffs” between specialized agents to solve a complex user request:
- Request: A user asks a general “HR Agent” in Teams, “I’m traveling to London for a client meeting next week; can you handle my travel booking and ensure it complies with our latest policy?”
- Orchestration: The HR Agent realizes it doesn’t have booking permissions. Using the new Orchestration Engine, it identifies a specialized “Travel Booking Agent” and a “Policy Compliance Agent.”
- Collaborative Execution: * The Policy Agent retrieves the travel policy from SharePoint and provides the budget limits to the Travel Agent.
- The Travel Agent searches for flights and hotels that fit those limits.
- Verification: The agents pass data back and forth to confirm the hotel choice is within the allowed budget.
- Completion: The primary HR Agent returns to the user with a single message: “I’ve found a flight and hotel that comply with our policy. Would you like me to book them?”
Step-by-Step: How to Enable Multi-Agent Connectivity
To allow your agents to communicate with one another using the new protocol:
- Step 1: Open Copilot Studio: Navigate to your primary agent.
- Step 2: Enable Orchestration: Go to Settings > Generative AI and toggle the orchestration mode to “Generative (Preview)” or “Multi-agent.”
- Step 3: Register Sub-Agents: Go to the Actions or Tools tab and select “Add an Agent.” You can now select other agents published within your environment.
- Step 4: Define Descriptions: Ensure each sub-agent has a highly detailed Instructional Description. The orchestrator uses these to “know” which agent is the expert in travel, finance, or technical support.
- Step 5: Configure Permissions: Set up Delegated Authentication so the sub-agents can act on behalf of the user who started the original chat.
- Step 6: Test & Publish: Use the “Test” pane to watch the “Conversation Map” and see how the orchestrator routes the logic between agents.
Infographic: The April 2025 Feature Set
The April update brought several tools to manage complex AI ecosystems:
| Feature | What it Does | Impact on Business |
| Multi-Agent Orchestration | Allows a “Master Agent” to manage “Sub-Agents.” | Reduces the need for users to know which specific bot to talk to. |
| A2A Protocol Support | Open standard for agent-to-agent communication. | Enables agents to talk across different platforms (e.g., Copilot to custom Azure bots). |
| Conversation Maps | Visual debugging tool for orchestration. | Helps developers see exactly where a handoff happened or failed. |
| Knowledge Handoff | Context is passed between agents during a handoff. | The user doesn’t have to repeat their information to the second agent. |
References
GM Dynamics & Agentic AI Consulting 