In February 2024, the Semantic Kernel team at Microsoft published a short roadmap post ahead of Build 2024. It set three priorities for the spring: bringing Python and Java to V1.0 parity with the .NET SDK, expanding model connectors, and building first-class agent support. As an MVP who has tracked Semantic Kernel since its early experimental releases, I found it worth revisiting this roadmap now, with more than two years of hindsight, to see how the plan held up against what actually shipped.
This is not a criticism of the original post. Roadmaps are meant to be directional, not contractual. But comparing stated intent against delivered reality tells you a lot about how a fast-moving AI SDK actually evolves, and it is useful context if you are deciding whether to build production systems on Semantic Kernel today.
What the roadmap promised
The February 2024 post organized its plans into three buckets. First, V1.0 parity: Python and Java were to reach Beta or Release Candidate status by March 2024, with full V1.0 launch targeted for Build in May. This mattered because the .NET SDK had already committed to no breaking changes on non-experimental features, and the team wanted the same production confidence extended to Python and Java developers.
Second, more connectors. The post named Gemini, Llama-2, Phi-2, Mistral, and Claude as models the team planned to support across Hugging Face, Azure AI, Google AI, Bedrock, and local deployments. It also promised less opinionated memory connector abstractions and groundwork for multi-modal connectors covering audio, images, video, and documents.
Third, and most ambitious, first-class agent support. At the time, Semantic Kernel had only an experimental agent implementation built on the OpenAI Assistants API. The roadmap said the team would abstract the agent interface to work with any model, drawing on research from the Autogen team so that agents could eventually collaborate as a team rather than operate in isolation.
What actually shipped by Build 2024
The V1.0 parity commitment held up well. Microsoft announced general availability for both Semantic Kernel Python and Semantic Kernel Java at Build 2024 in May, right on the timeline the roadmap laid out. Both SDKs picked up the improvements .NET developers already had, including automatic function calling and YAML-based prompt and agent assets that could move between languages. For a project juggling three SDKs in parallel, hitting a stated deadline like this is not something to take for granted.
The connector story played out less cleanly, which is normal for this part of the roadmap. New model integrations arrived steadily over the following months rather than as a single spring milestone, and the pace tracked the broader model landscape rather than a fixed release date. If you were waiting for a specific connector named in the post, checking the current connector list in the Semantic Kernel repository is still more reliable than treating a two-year-old blog post as current documentation.
The agent story took a turn nobody wrote down in February 2024
This is where the roadmap undersold what was actually coming. The February post framed agent support as an extension of Semantic Kernel itself, informed by Autogen’s research but still living inside the Semantic Kernel SDK. That is not how it played out.
Microsoft spent the next year and a half working through the fact that it had two overlapping agent frameworks. Autogen, which came out of Microsoft Research, was strong at experimental multi-agent orchestration but was not built for production hardening. Semantic Kernel had the enterprise scaffolding, things like thread-based state management, telemetry, and content moderation hooks, but its own agent abstractions were still catching up. Rather than keep evolving Semantic Kernel’s agent layer in isolation, Microsoft merged the two projects.
The result, called Microsoft Agent Framework, entered public preview in October 2025 and reached V1.0 in April 2026. It combines Autogen’s orchestration patterns with Semantic Kernel’s production features, and Microsoft has positioned it as the long-term successor to both Semantic Kernel and Autogen. Both original projects moved into maintenance mode: they still receive bug fixes and security patches, but new feature investment now goes into Agent Framework.
What this means if you are building on Semantic Kernel today
If you already have a Semantic Kernel application in production for prompt orchestration, function calling, or planning, nothing breaks. Maintenance mode means continued patches and stability, and the V1.0 guarantees around non-experimental features still apply. There is no forced migration deadline.
If you are starting a new project that needs multi-agent orchestration, it is worth evaluating Microsoft Agent Framework directly rather than building on Semantic Kernel’s older experimental agent APIs. Microsoft has published migration guidance for teams moving existing Semantic Kernel and Autogen projects across, and starting on the framework that is actively receiving feature investment saves you a migration later.
The broader lesson from comparing this roadmap to what shipped is not that Microsoft failed to deliver. The core SDK parity work landed on schedule. What changed is the shape of the bigger architectural bet: instead of Semantic Kernel absorbing agent capability piece by piece, Microsoft folded two frameworks together into something new. When you are choosing an AI SDK to build on, watch for these consolidation moments. They matter more to your long-term maintenance burden than whether a specific connector shipped on time.
Leave a Reply