Open-source SDK for building, orchestrating, and deploying single- and multi-agent workflows, unifying AutoGen's orchestration patterns with Semantic Kernel's enterprise plumbing.
- Operator
- Microsoft
- Open source
- Yes
- Payment capability
- Not indicated
- Supports MCP
- Yes
- Supports agent-to-agent protocols
- Yes
- Enterprise-managed
- Not indicated
- Cryptographically signed
- Not indicated
- Independent audit on record
- No public independent audit found
- Operator confirmed this listing
- Not indicated
- Last reviewed
- 2026-09-28
Verification notes: New listing, added this pass. Reached GA (v1.0) on April 3, 2026 — confirmed via Microsoft's own devblog. MIT licensed (github.com/microsoft/agent-framework), supporting Python and .NET. MCP support (discovering and invoking external MCP-compliant tools) ships as stable in 1.0; A2A support for cross-runtime agent collaboration is present but Microsoft's own release notes flag full A2A 1.0 spec compliance as 'coming soon,' so treat A2A as functional but not yet fully mature. AutoGen is now in maintenance mode with a published migration guide pointing here — see that listing. Correction this pass: the 'coming soon' caveat on A2A is partly resolved. Microsoft's own Agent Framework devblog ('A2A v1 Is Here,' dated May 1, 2026) confirms A2A v1 protocol support shipped in the .NET Agent Framework packages specifically, letting a .NET-based agent both call remote A2A agents from any vendor and expose itself to any A2A-compliant client. Microsoft's own Learn documentation doesn't yet confirm equivalent Python-package parity as of this pass, so treat A2A as GA for .NET and not yet confirmed at the same maturity for Python, rather than rounding the whole framework up uniformly. The a2a flag stays true, reflecting that real, documented support exists — just not identically across both supported languages yet. No change to MCP, license, or the AutoGen migration-guide pointer. Correction this pass: the Python/.NET A2A parity gap flagged previously is resolved. An official Microsoft devblog post ('Agent and Workflow Channels,' August 26, 2026) confirms Python-side channel integrations exposing agents through OpenAI, Telegram, A2A, and MCP clients — real, documented Python A2A support, not just .NET. The a2a flag stays true, now reflecting shipped support in both supported languages rather than an open question. No change to MCP, license, or the AutoGen migration-guide pointer. Re-checked 2026-09-28: no further protocol-support changes found since the August 26 post; continued development (MCP-based distributed skills, Foundry hosted agent isolation, a Cosmos DB memory preview) is feature work rather than a change to the flags recorded here.
Suggest a correction to this profile →