MCP Is Stable in Agent Framework 1.0. A2A Isn't.
Microsoft lists MCP as stabilized and backward-compatible in Agent Framework 1.0, released April 3, 2026, while full A2A 1.0 support is still coming soon with no committed date. For an IT services firm running agents across several clients, that gap matters before committing an integration to either protocol.
What Microsoft Agent Framework 1.0 Actually Changed
Microsoft published Agent Framework 1.0 on April 3, 2026, as a NuGet package named Microsoft.Agents.AI for .NET and a PyPI package named agent-framework for Python. The release follows a Release Candidate from February 2026 and the framework's original launch in October 2025. Microsoft describes 1.0 as a package version bump from the Release Candidate, not a rewrite. By November 6, 2026, the NuGet package had reached version 1.28.0.
MCP Is Part of the Stabilized Core
Microsoft lists MCP (Model Context Protocol) under "What's in version 1.0," stating that MCP lets agents dynamically discover and invoke external tools. 1.0 covers features Microsoft calls "battle-tested, stabilized, and committed to supporting with full backward compatibility." MCP sits inside that commitment, alongside single agents, multi-agent orchestration, agent memory, and YAML workflows. MCP's documentation describes it as a standard way to connect agents to external tools and data, like "a USB-C port for AI applications."
A2A Support Is Not There Yet
The same section of the announcement lists A2A (Agent2Agent) alongside MCP, but with a different status: "A2A 1.0 support coming soon." Microsoft does not give a date for that support. For a team planning cross-agent interoperability through A2A rather than MCP, the framework's 1.0 release does not yet carry the same backward-compatibility commitment.
Stable vs. Preview in Version 1.0
Microsoft splits 1.0 into two tiers. The stable tier includes MCP, single agents, multi-agent orchestration patterns, agent memory, and YAML-based workflows, all covered by the backward-compatibility commitment. The preview tier includes DevUI, Foundry Hosted Agent Integration, AG-UI and ChatKit integrations, Skills, the GitHub Copilot SDK and Claude Code SDK integrations, and the Agent Harness, which can still change before their own 1.0.
| Capability | Status in version 1.0 |
|---|---|
| MCP (Model Context Protocol) | Stable, backward-compatible |
| Single agents and connectors | Stable, backward-compatible |
| Multi-agent orchestration (sequential, concurrent, handoff, group chat, Magentic-One) | Stable, backward-compatible |
| Declarative YAML agents and workflows | Stable, backward-compatible |
| A2A (Agent2Agent) | 1.0 support coming soon |
| DevUI, Foundry Hosted Agent Integration, Skills, Agent Harness | Preview, can still change |
Why This Matters for ESNs Managing Multiple Clients
An IT services firm often runs agents on different frameworks for different clients, with little room to redo an integration after a major version change. Agent Framework 1.0 reduces that risk for the pieces it has stabilized, including MCP-based tool access. The same risk still applies to any integration built specifically on A2A, since Microsoft has not yet committed to its long-term compatibility.
Migrating from the Release Candidate, AutoGen, or Semantic Kernel
Teams already on the Release Candidate move to 1.0 with a package version bump, according to Microsoft. Teams coming from Semantic Kernel or AutoGen have dedicated migration guides from Microsoft, since both projects feed into Agent Framework. None of these paths require a different protocol choice: MCP tool integrations carry over, and projects relying on A2A keep that code in preview status.
What to Check Before Committing an Integration
Before building a client integration on Agent Framework 1.0, confirm which capability it depends on. MCP-based tool access, single and multi-agent orchestration, and YAML workflows sit inside Microsoft's backward-compatibility commitment. DevUI, the Agent Harness, SDK integrations, and full A2A support do not, and Microsoft gives no date for when they will.
Tracking Stability and Cost Across Clients with Atipol
For an ESN that already tracks budgets and tickets per client, Atipol's platform keeps that same separation for agent work: each collaborator runs an agent lead with their preferred tools, while leadership gets a shared view of cross-team tickets and per-project costs. See atipol.ai/use-cases/multi-team-management for how multi-team orchestration works in practice. For audit needs tied to MCP-connected tools, atipol.ai/agentic-ai-blog/ai-agent-audit-log covers what to log and for how long.
Frequently asked questions
Is MCP support in Microsoft Agent Framework 1.0 stable for production use?
Yes. Microsoft lists MCP among the features in version 1.0 that are battle-tested, stabilized, and covered by its backward-compatibility commitment, as stated in the April 3, 2026 announcement.
Is A2A (Agent2Agent) support also stable in version 1.0?
No. Microsoft's own announcement states that full A2A 1.0 support is coming soon, without a committed date, so it does not yet carry the same backward-compatibility guarantee as MCP.
Do teams need to rewrite their integrations to move to Agent Framework 1.0?
Microsoft describes the move from its Release Candidate to 1.0 as a package version bump, and provides migration guides for teams coming from Semantic Kernel or AutoGen, rather than a rewrite.
Sources
- Microsoft Agent Framework, Version 1.0 announcement, 03/04/2026
- Model Context Protocol, official documentation, docs version 28/07/2026
- NuGet, Microsoft.Agents.AI package page, last updated 06/11/2026
The public demo shows a fictional organization at work, no account needed. The free plan includes a project, three agents and an agent lead.
