In a press release dated 9 April 2026, marking the project's first anniversary, the Linux Foundation reported that the Agent2Agent (A2A) protocol now has more than 150 supporting organizations, up from more than 50 a year earlier, and had reached version 1.0.
What 1.0 adds, per the release
- Enterprise multi-tenancy.
- Signed Agent Cards, for cryptographic verification of an agent's identity.
- Modernized security flows, with a migration path for early adopters.
- Five production-ready SDKs: Python, JavaScript, Java, Go and .NET.
Where it fits
The release describes A2A as complementary to MCP: MCP connects an agent to tools and data, while A2A lets agents from different vendors talk to each other. It reports integration in Microsoft Azure AI Foundry and Copilot Studio, and support via Amazon Bedrock AgentCore Runtime.
What to do
- If you plan a multi-vendor agent estate, design against open protocols rather than a single vendor's connectors.
- Pay attention to agent identity: signed identities are what make audit possible.
A press release from the standards body describes adoption in its own favourable terms. Verify the vendors' support in their own documentation.