Microsoft Agent Framework ships Python, .NET updates
October Releases Bring MCP 2.x Breaking Changes
Microsoft released two major versions of its Agent Framework in October 2026, advancing the open-source developer toolkit for building autonomous agents. Python 1.23.0 shipped on October 22, 2026, followed by .NET 1.26.0 on October 23, 2026, according to Microsoft Foundry.
Both releases introduced breaking MCP 2.x compatibility changes, marking a significant shift in how agents interact with the Model Context Protocol. The updates also mandated explicit AG-UI authorization-scope requirements, requiring developers to be more deliberate about what permissions agents grant to user-facing interfaces. Additionally, the releases clarified ownership rules for MCP-client lifecycles, addressing a pain point for teams managing multiple concurrent agent instances.
The Agent Framework is available across Python and .NET, with a Go implementation currently in public preview. This multi-language support positions the framework as a flexible option for enterprise teams working across heterogeneous tech stacks.
Developer Impact and Migration Path
Breaking changes often trigger migration work for production deployments, but the explicit authorization-scope requirements represent a security-focused design decision. Developers using earlier versions will need to audit their agent configurations and explicitly declare the scopes their agents require—a pattern aligned with OAuth 2.0 and other zero-trust security models.
The clarified MCP-client lifecycle ownership rules reduce a common source of bugs: memory leaks and resource exhaustion when agents spawn child clients without clear responsibility for cleanup. By codifying ownership semantics, Microsoft is lowering the operational burden on teams running agents in long-lived processes.
Position in the Broader Agent Ecosystem
Microsoft's Agent Framework sits within a broader ecosystem of agentic tools and frameworks, competing with and complementing offerings from Google, Anthropic, and open-source communities. The October releases demonstrate Microsoft's commitment to regular, versioned updates—a maturity signal for teams considering the framework for production workloads.
The Go public preview also suggests Microsoft is broadening language coverage, addressing teams that rely on Go for systems programming and cloud-native applications.
What's Next
Developers adopting these releases should plan for testing in non-production environments first, given the breaking changes. Teams should review their MCP integrations and authorization configurations before upgrading production agents.
