COPILOT STUDIO — PROJECT 7🔴 EXPERT
MultiAgentMesh — Sales Proposal Mesh combining embedded agents, connected agents, and A2A interoperability. Static reference only.
🧭 Sales Proposal Orchestrator (Parent Agent)
Embedded / ChildCRM Lookup
(inline topic)
Connected AgentDocument Drafting
(own tools + Fabric Data Agent)
Connected AgentScheduling
(own Outlook/Graph tools)
External · A2AContract Terms
(partner-built, non-Copilot-Studio)
Embedded — shares parent's context, no separate billing surface Connected — own orchestration, additive cost A2A external — outside Microsoft's billing entirely

Security boundary test

Attempted: "Cancel my 3pm call with Acme" (Parent doesn't have cancellation rights; Scheduling Agent does)
✔ Blocked — parent correctly refuses to reach cancellation capability indirectly through the connected Scheduling Agent. Delegation does not equal privilege escalation.

Cost — additive across the mesh

Parent routing decision~5 cr
CRM Lookup (embedded)included in parent's turn
Document Drafting (connected)~18 cr
Scheduling (connected)~8 cr
Contract Terms (A2A, external)billed outside Microsoft
Total, one proposal~65-80 cr
What this shows: the embedded CRM agent shares the parent's billing surface (cheap, no separate call charge), while each connected agent adds its own independent consumption on top of the parent's routing cost — cost is additive across the mesh. The security test proves that delegating to a more privileged connected agent doesn't quietly grant the parent that same privilege.