Microsoft 365 Copilot
Let Copilot Studio agents hand questions and tasks to your organisation's specialists and teams, as the person asking.
A Copilot Studio agent (and so Microsoft 365 Copilot and Teams) can call your organisation's agents over Agent2Agent (A2A). A person asks Copilot something; Copilot hands it to one of your specialists or teams; the work runs on that person's own AI Workbench, or a node they let run their work, as them. Your policy, tool rules, data protection and approvals apply exactly as if they had asked in the workbench, and the run reaches Microsoft Agent 365 with Copilot as its caller.
Enterprise only. Needs AI Workbench 0.59.0 or later on the machines that do the work.
Allow it
- Open Policies, choose the policy for the projects, and open Microsoft 365 Copilot.
- Turn on Copilot may call our agents.
- Optionally list Only these Copilot agents (their Entra application ids), and choose whether A person approves: never, before the work starts, or before its changes merge.
- Publish the policy.
Make an agent callable
On a project's Overview, the Microsoft 365 Copilot panel lists the project's teams and their agent members. Make callable gives one an address. A team takes a task to a plan, the work and a review; a specialist answers in a conversation.
Administrators, and the project's owners, make agents callable. To keep it to administrators, open Settings, Microsoft 365 Copilot, and choose Administrators only.
Connect it in Copilot Studio
- Set up the Entra side once: the
Agents.Invokescope and an app for Copilot Studio's connection. See Microsoft setup, section 4c. - In Copilot Studio, open your agent, then Agents, Add an agent, Connect to an external agent, Agent2Agent.
- Give the agent's address from the panel, and an OAuth 2.0 connection to Microsoft Entra ID asking for the scope the panel shows.
What the person sees
- In Copilot: progress, any question the agent asks (answer it there or in the workbench's Inbox), and the result with the branch or files it made.
- In AI Workbench: the conversation or run, marked "Asked from Microsoft 365 Copilot".
What you see
The panel lists the tasks asked lately: which agent, who asked, and how it went. Never what was asked. Every call is in Audit (a2a.message, a2a.reply, a2a.cancel); refused calls are warnings, so a connected Microsoft Sentinel receives them.
When a call is refused
| Copilot shows | Why |
|---|---|
| The organisation's policy does not let Microsoft 365 Copilot call its agents | The policy for the project does not allow it, or not from this Copilot agent |
| You are not a contributor on the project | The person asking is not a contributor or owner on the project |
| None of your workbenches is connected with this project | Open AI Workbench on the project (or let a node run your work) and ask again |
| The workbench said: … | The workbench refused it, for example a member disabled in the agent registry |
Microsoft Agent 365
Give every enterprise team an Entra agent identity and a card in the Agent 365 registry, and see its runs and tool calls in Agent 365 observability.
Microsoft Purview
Make your tenant's sensitivity labels the data-protection rule on every workbench, ask Purview itself before a prompt leaves, and apply encrypting labels through SharePoint.