GOOGLE I/O 2026 — LIVE UPDATE
Google A2A Protocol Just Hit 150 Enterprises in Production
Microsoft. AWS. Salesforce. SAP. ServiceNow. All running A2A this week. If your enterprise architecture hasn’t accounted for agent-to-agent communication, this is the update you need to read.
Summary
Google’s A2A protocol — the open standard for AI agents communicating across platforms — just got its biggest upgrade at I/O 2026. 150+ enterprises are in production. ADK 1.0 is stable. This guide explains the architecture, compares A2A vs MCP, and gives your team 3 concrete steps to take this week.
⚡ TL;DR — What Changed This Week
- A2A v1.2: gRPC support, signed Agent Cards, latency broadcasting
- ADK 1.0 GA: Python, Go, Java, TypeScript — stable, ship now
- 150+ orgs in production: Microsoft, AWS, Salesforce, SAP, ServiceNow all live
- Linux Foundation governance: Open industry standard, not a Google project
- Your move: Audit A2A readiness → add Agent Cards → pick build path
What Is the Google A2A Protocol?
The Agent2Agent (A2A) protocol is an open communication standard that allows AI agents built by different vendors, on different frameworks, to discover each other, delegate tasks, and return results — without any custom integration code between them.
If MCP is the USB-C port that connects an AI agent to its tools and data sources, then A2A is the internet routing layer that lets entire networks of agents cooperate across company and platform boundaries.
Google announced A2A in April 2025 with 50 technology partners. By Google I/O 2026, that number had grown to 150+ organisations in active production — including Microsoft, AWS, Atlassian, Cohere, Intuit, LangChain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, UKG, and Workday.
The protocol is now governed by the Linux Foundation’s Agentic AI Foundation (AAIF) — the same body that oversees MCP — which signals it has crossed from a Google project to an open industry standard.
At Ailoitte, we build AI agent systems for enterprises using exactly the kind of multi-agent architecture A2A is designed to enable. Here is what your team needs to understand right now.
What Changed at Google I/O 2026
The upgrade announced at Google I/O 2026 is significant for two reasons: it makes A2A stable enough to build production systems on, and it dramatically improves enterprise security.
| Feature | What It Means for Enterprise |
|---|---|
| gRPC support | Lower latency for high-frequency agent coordination — critical for real-time workflows |
| Signed Agent Cards | Cryptographic domain verification — agents can now trust who they are talking to |
| Extended Python SDK | Faster integration for LangChain, CrewAI, AutoGen, or custom Python agent stacks |
| Latency broadcasting | Agents advertise response speed — enables intelligent routing to the fastest available agent |
| ADK 1.0 GA | Google’s Agent Development Kit is now stable across Python, Go, Java, and TypeScript. Framework risk: gone. |
Before ADK 1.0, building on the A2A carried framework stability risk. That risk is gone. The ADK 1.0 stable release is the green light for enterprise engineering teams to move from evaluation to implementation.
How A2A Works: Architecture in Plain English
A2A operates on three components: Agent Cards, a client agent, and a remote agent.
Agent Cards are structured capability declarations — think of them as a business card for an AI agent that describes what it can do, what inputs it accepts, what outputs it returns, and how to reach it. At I/O 2026, Agent Cards gained cryptographic signatures for domain verification, closing a major enterprise security gap.
The client agent identifies a task it needs to delegate. It searches for an appropriate remote agent using Agent Card discovery, then sends the task using JSON-RPC 2.0 over HTTP or gRPC.
The remote agent receives the task, executes it, and returns artifacts — structured results — along with status updates. A2A supports both fast tasks (seconds) and long-running operations (hours or days, with human-in-the-loop steps).
Real-World A2A Example
A Salesforce CRM agent needs to verify a contract clause before closing a deal. It sends the contract via A2A to a specialised legal review agent on a law firm’s internal platform. The legal agent returns a structured verdict. The CRM agent updates the deal status — all without either system knowing the internal architecture of the other. This is the pattern Ailoitte uses in its AI CRM automation builds for Salesforce and HubSpot.
A2A vs MCP: The Clearest Comparison You Will Find
This is the question every enterprise architect is asking in 2026. Here is the direct answer:
| MCP (Model Context Protocol) | A2A (Agent2Agent Protocol) | |
|---|---|---|
| Purpose | Agent connects to tools and data | Agents delegate tasks to other agents |
| Direction | Vertical — agent gets context and capability | Horizontal — agents coordinate across orgs |
| Analogy | USB-C: standardises how one device plugs in | Internet routing: standardises how networks connect |
| Transport | JSON-RPC over HTTP/SSE | JSON-RPC over HTTP/SSE/gRPC |
| Governed by | Linux Foundation (AAIF) | Linux Foundation (AAIF) |
| Scale | 18,000+ community-indexed servers | 150+ orgs in production |
| Best for | Giving one agent access to tools, APIs, data | Multi-agent pipelines across vendors or teams |
The key point: MCP and A2A are not competitors. They are designed to work together. MCP handles how an individual agent gets equipped. A2A handles how fleets of equipped agents cooperate. Enterprise systems need both. If you are building enterprise AI solutions and you have only implemented MCP, you have the tools but not the network. A2A is the network.
Who Is Running A2A in Production Right Now
The 150+ production organisations are not startups. They are the enterprise software stack:
| Company | A2A Implementation | What It Enables |
|---|---|---|
| Microsoft | Azure AI Foundry + Copilot Studio | Enterprise agents coordinate across Microsoft 365 and Azure services |
| AWS | Bedrock AgentCore Runtime | Multi-agent orchestration across AWS services and external systems |
| Salesforce | Agentforce platform | CRM agents communicate with external specialist agents via A2A |
| SAP | Enterprise ERP modules | Workflow agents coordinate across finance, HR, and supply chain |
| ServiceNow | IT service management | IT agents delegate to specialist resolution agents via A2A |
This is not early-adopter territory. If your enterprise customers run Microsoft, AWS, or Salesforce infrastructure — and most do — they are already in an A2A-capable environment. The question is whether the agents you build for them can participate in that environment. At Ailoitte, every AI agent we build through our Velocity Pod model is designed to integrate with the platforms your enterprise already runs — not to add another silo.
3 Steps Enterprise App Teams Should Take This Week
Step 1: Audit Your Current Agent Architecture for A2A Readiness
Before building anything new, map what you have. For each AI agent or AI-powered service in your stack, answer three questions: (1) Does it expose a structured capability description? (2) Can it accept tasks from external systems without a custom integration? (3) Can it return structured results that another agent can parse without human interpretation?
If the answer to any of these is no, that agent is an island. As enterprise AI moves toward orchestration — not just automation — isolated agents will deliver diminishing returns. Ailoitte’s AI Strategy Workshop maps exactly this: your current AI footprint, which components are agent-ready, and where A2A integration creates the highest ROI.
Step 2: Implement Agent Cards on Your Existing AI Services
You do not need to rebuild your agents to make them A2A-compatible. An Agent Card is a JSON document that describes what your agent does, what inputs it accepts, authentication requirements, and endpoint details. For most existing services, this is a documentation exercise with a lightweight API wrapper — not a ground-up rewrite. Once Agent Cards are in place, your agent becomes discoverable and callable by any A2A-compatible system in the Microsoft/AWS/Salesforce/SAP stack.
Our Engine Room methodology includes agent interoperability as a baseline requirement. Agent Cards are part of our Agentic QA pipeline checks before any agent goes to production.
Step 3: Choose Your A2A Build Path
Path A — Build on Google ADK 1.0
Best for teams starting fresh. ADK 1.0 is stable across Python, Go, Java, and TypeScript. A2A support is native.
Timeline: 4–8 weeks to first production agent
Path B — Add A2A Adapter to Existing Stack
Best for existing LangChain, CrewAI, and AutoGen teams. Add A2A wrapper — no core logic changes needed.
Timeline: 2–5 days per agent for Agent Card + wrapper
Ailoitte builds on both paths through our AI agent development practice and Generative AI development capabilities across all major frameworks. Our AI Velocity Pods take an enterprise from A2A assessment to first production agent in under 6 weeks.
What This Means for Specific Industries
Healthcare: Healthcare software teams can connect clinical decision agents to administrative agents to billing agents across vendors — without centralising sensitive patient data. Each agent stays behind its own compliance boundary. A2A handles the task handoff.
FinTech: Financial software platforms can connect fraud detection agents, credit scoring agents, and customer service agents from different vendors into a single orchestrated flow. Real-time. Auditable.
Retail and eCommerce: Retail AI systems can connect inventory agents, pricing agents, and fulfilment agents across ERP, WMS, and CRM platforms — via A2A, without a custom integration layer for every pair.
Enterprise SaaS: If your product is a SaaS platform, implementing A2A today means your product becomes a node in the enterprise agent network. Your customers’ Copilot and Agentforce agents can call your product’s agents natively. This is a distribution channel that did not exist 12 months ago.
The Window Is Narrow
A2A hit 150 production organisations this week. Six months from now, it will hit 500. Enterprise RFPs in Q3 2026 will start including “A2A-compatible” as a requirement, the same way “cloud-native” and “API-first” became requirements a decade ago.
The teams that build A2A expertise now — in architecture, implementation, and production operations — will have a 12–18 month advantage over teams that wait for the market to demand it. Ailoitte’s AI Velocity Pods are built for exactly this moment: AI-native engineering teams that ship production-grade agentic systems on fixed-price, outcome-based engagements — not billable hours.
FAQs
What is the Google A2A protocol?
The Google Agent2Agent (A2A) protocol is an open standard that enables AI agents built by different vendors and on different frameworks to communicate, delegate tasks, and share results without custom integration code. It uses HTTP, gRPC, and JSON-RPC 2.0 for transport, and Agent Cards for capability discovery. A2A was launched by Google in April 2025 and is now governed by the Linux Foundation’s Agentic AI Foundation. As of May 2026, more than 150 organisations are running A2A in production including Microsoft, AWS, Salesforce, SAP, and ServiceNow.
How is A2A different from MCP?
MCP (Model Context Protocol) handles how an individual AI agent connects to tools, APIs, and data sources — it is vertical (agent-to-tool). A2A handles how multiple AI agents communicate with each other across platforms and organisational boundaries — it is horizontal (agent-to-agent). Both standards are governed by the Linux Foundation and are designed to work together. If you are building enterprise AI solutions, you need MCP to equip each agent and A2A to let your fleet of agents cooperate. Ailoitte implements both on all production agent builds.
Which companies support A2A in 2026?
As of Google I/O 2026, companies running A2A in production include Microsoft (Azure AI Foundry, Copilot Studio), AWS (Bedrock AgentCore Runtime), Salesforce (Agentforce), SAP, ServiceNow, Atlassian, Cohere, Intuit, LangChain, MongoDB, PayPal, UKG, and Workday — among 150+ total organisations. This broad enterprise adoption means if your customers run any major cloud or SaaS platform, they are already in an A2A-capable environment. Ailoitte’s Velocity Pods build A2A-native agents that integrate with all of these platforms.
Do I need to use Google Cloud to use A2A?
No. A2A is an open protocol governed by the Linux Foundation, not a Google-proprietary technology. It runs on HTTP and gRPC — standard transport layers. Microsoft and AWS have both implemented A2A support on their own platforms independently. You can implement A2A on any cloud or on-premise infrastructure. Ailoitte builds A2A-compatible agents across all major cloud environments — GCP, AWS, Azure, and private infrastructure.
How long does it take to make an existing app A2A-compatible?
For an existing AI service with a well-defined API, adding A2A compatibility — primarily creating an Agent Card and an A2A-compatible endpoint wrapper — typically takes 2–5 days of engineering effort. A full multi-agent system built A2A-native from the ground up typically takes 4–8 weeks depending on the number of agents and integration complexity. Ailoitte’s AI Velocity Pods are structured to deliver first-production A2A agents in under 6 weeks, on fixed-price engagements. Start with an AI Strategy Workshop to assess your current agent architecture readiness.
What is Google ADK 1.0?
Google ADK (Agent Development Kit) is the official framework for building A2A-compatible agents. ADK 1.0 was announced at Google I/O 2026 as the first stable, production-ready release, available in Python, Go, Java, and TypeScript. It provides native A2A protocol support, built-in Agent Card generation, task routing, and long-running task management. Before ADK 1.0, building on A2A carried framework instability risk. That risk is now gone — ADK 1.0 is the green light for enterprise teams to move from evaluation to implementation. Ailoitte builds on ADK 1.0 for new A2A-native agent projects.
Is A2A secure enough for enterprise use?
Yes. A2A v1.2 (released at Google I/O 2026) introduced signed Agent Cards with cryptographic domain verification, closing the main enterprise security gap from earlier versions. A2A also supports OAuth 2.0 and enterprise authentication schemes at parity with OpenAPI standards. SAP and ServiceNow — both running sensitive enterprise workloads — are in production on A2A today. For regulated industries, Ailoitte implements additional security layers including HIPAA-compliant agent architectures for healthcare and SOC 2 compliant builds for financial services. Contact Ailoitte to discuss your specific compliance requirements.
Discover how Ailoitte AI keeps you ahead of risk
Sunil Kumar
Sunil Kumar is CEO of Ailoitte, an AI-native engineering company building intelligent applications for startups and enterprises. He created the AI Velocity Pods model, delivering production-ready AI products 5× faster than traditional teams. Sunil writes about agentic AI, GenAI strategy, and outcome-based engineering. Connect on
LinkedIn
Stephan is the sports journalist for the Maple Grove Report.
