What the announcement establishes
The title tells us the feature belongs to Azure SRE Agent and is in public preview. Azure Updates defines "In preview" as available to all Azure customers for non-production use and testing. That is a general site definition, not a statement about this feature. Treat it as a test-bed capability, not something to wire into your on-call process.
The entry does not say:
- which A2A protocol version or transport it uses
- whether SRE Agent acts as an A2A client, a server, or both
- how authentication works
- which regions are covered
- how it is priced
- what its known limitations are
Any claim about those would be a guess.
Why A2A matters for an operations agent
Microsoft's Agent Framework guidance describes A2A as an open protocol for agents to discover one another, exchange messages and coordinate tasks over HTTP. It is meant to work across service, team and organizational boundaries, in any language or framework. That is protocol background, not a description of how SRE Agent implements it.
Azure SRE Agent is Microsoft's AI service for operations teams. It investigates incidents, queries Azure Monitor and Application Insights, and can take remediation actions when it is configured to. Microsoft's overview lists five extension points for it: skills, custom agents, Python tools, MCP servers and agent hooks. The overview describes MCP as a way to connect external data sources and platforms, including partner observability tools such as Datadog and Splunk.
A2A would sit alongside MCP, not replace it. In general terms, MCP gives an agent tools and data, while A2A lets an agent talk to another agent. Microsoft hasn't said whether the SRE Agent preview connects the two or how administrators would choose between them.
Practical cautions before you test
Microsoft's general A2A guidance lists operational costs of calling remote agents:
- network latency
- failure handling
- timeouts
- retries
- versioning
- discovery through known endpoints or a registry
The guidance also says the remote agent keeps its own conversation state. Whether SRE Agent's preview behaves this way isn't confirmed.
Microsoft's documentation for Foundry's A2A tool also carries a warning that is worth keeping in mind. It says to treat provider-supplied agent descriptions as untrusted input. It also says to enforce permissions and approvals independently of model-generated decisions. SRE Agent can act on Azure resources, so the same caution applies to any A2A peer you connect it to. That is our inference. Microsoft hasn't said it applies to this preview.
SRE Agent already has governance controls. Per Microsoft's overview, every proposed tool call passes through governance controls before it runs. Its Reader mode gives read-only access, which Microsoft's FAQ suggests for trying the agent without affecting production. That is a sensible starting point for any preview test.
Don't mix this up with Foundry's A2A features
Microsoft has several separate A2A features. Foundry has an A2A tool for calling remote agents. At Build 2026 it also added incoming A2A in public preview, which exposes a Foundry agent as an A2A endpoint. Azure API Management has had A2A API support in preview since November 2025. Foundry's documentation lists A2A v1.0 as generally available and v0.3 as preview. Those version details belong to Foundry, not SRE Agent, so don't assume they carry over.
What to do now
- Check the SRE Agent documentation and the portal for the new A2A settings before planning anything.
- Confirm your region. Microsoft's FAQ lists Sweden Central, East US 2 and Australia East as current SRE Agent regions, and that list may not match the preview's availability.
- Ask what identity and authorization model applies, and what data leaves your environment.
- Test only in a non-production subscription, ideally in Reader mode.
Once Microsoft publishes feature-specific documentation, the open questions above will be answerable. Until then, the supported fact is that A2A support in Azure SRE Agent has entered public preview.
References
- (In preview) Public Preview: Agent-to-Agent (A2A) protocol support in Azure SRE Agent Azure Updates · 2026-11-17T20:00:32Z
- Preview: Govern, Secure, and Observe A2A APIs with Azure API Management techcommunity.microsoft.com
- Host agents with A2A | Microsoft Learn learn.microsoft.com