Technology RadarTechnology Radar

Microsoft AutoGen / Semantic Kernel

multi-agentframework
This item was not updated in last three versions of the Radar. Should it have appeared in one of the more recent editions, there is a good chance it remains pertinent. However, if the item dates back further, its relevance may have diminished and our current evaluation could vary. Regrettably, our capacity to consistently revisit items from past Radar editions is limited.
Assess

In October 2025, Microsoft merged two previously separate frameworks — AutoGen (multi-agent research platform) and Semantic Kernel (enterprise LLM SDK) — into a unified Microsoft Agent Framework. It reached Release Candidate (rc5) on March 20, 2026, with GA targeted for end of Q1 2026.

Buy vs Build

This is a build framework with a strong buy story if your organisation is on Azure. The managed hosting, enterprise SLAs, and Azure integrations are the "buy" angle — you're buying reliability and compliance, not avoiding code.

Why It's in Assess

The unified framework is promising, but it is still in Release Candidate as of late March 2026 — GA is expected imminently (Microsoft confirmed "end of March" target). There is limited production track record outside of Microsoft-aligned teams. The strong case for it is specific: if you're a .NET shop or an Azure-committed enterprise, this is now the obvious choice.

AutoGen brought: event-driven multi-agent orchestration, async execution, human-in-the-loop patterns, production use at Novo Nordisk and other enterprises

Semantic Kernel brought: production-grade LLM SDK, C#/Python/Java support, deep Azure OpenAI integration, plugin architecture

Combined, you get:

  • Multi-language support (C#, Python, Java) — uniquely valuable for heterogeneous enterprise stacks
  • Native Azure integration (Azure OpenAI, Azure AI Search, Azure Functions)
  • Production SLAs with Microsoft support
  • Compliance features important in regulated industries

When to Choose It

  • Your engineering team writes C# or .NET
  • You're committed to Azure infrastructure
  • You need Microsoft support SLAs
  • You're in a regulated industry where Microsoft's compliance certifications matter (HIPAA, SOC 2, ISO 27001)

When to Choose Something Else

  • Python-only stack: LangGraph or CrewAI have more ecosystem momentum
  • Not on Azure: The Azure integration is the key value prop; outside Azure, you lose most of the "buy" benefits
  • Greenfield project: Less documentation and community answers than LangGraph/CrewAI at this point

Key Characteristics

Property Value
Languages C#, Python, Java
License MIT
Hosted option Azure AI Foundry (managed)
Provider Microsoft