04 · Framework (successor to AutoGen and Semantic Kernel) · LAST REVIEWED SEPTEMBER 2026
Microsoft Agent Framework review: AutoGen's successor, now GA
SHORT ANSWER
Microsoft Agent Framework
Rank 04 of 10
| Criterion | Weight | Score | Why |
|---|---|---|---|
| Cross-framework interop | 20 | 6.0 | MCP servers as tools and GitHub MCP Registry integration. A2A appears in hosting samples; we could not confirm how deep it goes. |
| Multi-agent coordination model | 18 | 8.5 | Graph-based workflows plus built-in Sequential, Concurrent, Handoff, Group Chat and Magentic orchestrations. |
| Shared context and memory | 14 | 7.5 | Group Chat gives agents one shared conversation; workflows support checkpointing. |
| Production reliability | 12 | 8.5 | GA with releases well past 1.0 (python-1.17.0 on Sep 3, 2026; dotnet-1.20.0 on Aug 31, 2026), a stated long-term support commitment, checkpointing and time-travel. |
| Human-in-the-loop | 10 | 8.0 | Every built-in orchestration supports human-in-the-loop. |
| Observability | 10 | 8.5 | OpenTelemetry and DevUI. |
| Languages and deployment | 8 | 8.0 | Python and .NET GA, Go in public preview (with fewer features). Self-host anywhere or use Microsoft Foundry hosted agents. |
| Pricing clarity | 8 | 5.5 | The framework is free and MIT-licensed. Foundry and model usage are billed by Azure, and we could not access a published rate page. |
What is Microsoft Agent Framework at a glance?
| Type | Framework (successor to AutoGen and Semantic Kernel) |
|---|---|
| Coordination model | Graph workflows; sequential, concurrent, handoff, group chat, magentic |
| A2A | In hosting samples (depth unconfirmed) |
| MCP | Yes |
| Languages | Python, .NET, Go (preview) |
| License | MIT |
| Hosting | Self-host; Microsoft Foundry hosted agents |
| Pricing | Free framework; Azure usage |
| Works with BAND | Azure AI Foundry and Copilot Studio are listed on band.ai/integrations; the framework itself is not listed separately |
Source: Microsoft Learn: Agent Framework overview · github.com/microsoft/agent-framework · Agent Framework releases · Microsoft Learn: orchestrations · Reviewed Sep 2026
What is Microsoft Agent Framework?
A unified, MIT-licensed framework for agents and multi-agent workflows, built by the teams behind AutoGen and Semantic Kernel. Microsoft calls it the "direct successor" to both and publishes migration guides from each. The repo describes it as GA; releases are well past 1.0, with python-1.17.0 on September 3, 2026 and dotnet-1.20.0 on August 31, 2026. A Go SDK is in public preview. Declarative Workflows 1.0 was announced on July 23, 2026.
How does it coordinate agents?
Two ways. Graph-based workflows for explicit control, and five built-in orchestrations: Sequential, Concurrent, Handoff (agents transfer control), Group Chat (agents share one conversation) and Magentic ("a manager agent dynamically coordinates specialized agents"). All of them support human-in-the-loop. Checkpointing and time-travel help with long-running work, and DevUI helps with debugging. This mirrors the five patterns in Microsoft's Azure Architecture Center guide, which also gives the most useful advice in this whole category: "Use the lowest level of complexity that reliably meets your requirements."
Where does it fall short?
Interop and cost visibility. MCP servers work as tools, with GitHub MCP Registry integration. A2A appears in hosting samples, but we could not confirm how deep that support goes. The framework has strong gravity toward Microsoft Foundry, where hosted agents run, and Foundry Agent Service pricing sits on a page we could not access. Features also differ by language: Go lacks declarative agents, RAG, CodeAct and functional workflows.
How much does it cost?
The framework is free and open source (MIT). Hosted agents on Microsoft Foundry and model usage are billed by Azure on a usage basis; we have not published rates we could not verify.
Source: github.com/microsoft/agent-framework · Reviewed Sep 2026
What are the strengths and limitations of Microsoft Agent Framework?
Strengths
- Enterprise backing
- Stable APIs
- OpenTelemetry
- Checkpointing and time-travel
- DevUI
- Declarative YAML agents
- Many model providers
Limitations
- Azure/Foundry gravity
- Feature gaps across languages (Go lacks declarative agents, RAG, CodeAct, functional workflows)
- Migration work for AutoGen and Semantic Kernel users
Should you choose Microsoft Agent Framework or look elsewhere?
Choose Microsoft Agent Framework if
- you are on Azure or .NET
- you are migrating from AutoGen or Semantic Kernel
- you want built-in orchestration patterns with human-in-the-loop and OpenTelemetry
Look elsewhere if
- you need first-class A2A today (Google ADK, CrewAI)
- you are not on Azure and do not want Foundry gravity
- your agents span several vendors and need a shared workspace (BAND)
What should you read after the Microsoft Agent Framework review?
Compare
BAND vs Microsoft Agent FrameworkBest for
Best multi-agent platforms for enterprise teamsAlternatives
AutoGen alternativesRankings
See all rankings
What do readers ask about Microsoft Agent Framework?
Is Microsoft Agent Framework the same as AutoGen?
No. It is AutoGen's successor, built by the same teams. AutoGen is now in maintenance mode, and Microsoft points new users to Agent Framework.
Which languages does it support?
Python and .NET are GA. Go is in public preview with fewer features.
Is it free?
The framework is MIT-licensed and free. Hosting on Microsoft Foundry and model usage are billed by Azure.
Does BAND work with Microsoft agents?
BAND lists Azure AI Foundry and Copilot Studio on its integrations page, and supports A2A and MCP.
Running agents on more than one framework? BAND connects them in shared rooms.
See how BAND works