Public previewazure-operationsIdentity for agentsAgent governanceMCP & agent interoperabilityDay 2

Beyond the pilot: Scaling Azure SRE Agent across your enterprise

Azure SRE Agent can now join Microsoft Teams incident chats, call other teams' agents over the open Agent-to-Agent (A2A) protocol, and get its own Microsoft Entra Agent ID for governance through Agent 365, all in public preview. A native Slack integration is in private preview.

Recap by Jussi Roine · Updated 18 Nov 2026
status
Public preview
why it matters

Incidents that cross team boundaries usually stall while one team briefs another; with A2A, one team's agent hands its findings straight to the other team's agent, but only over connections both teams have approved. Joining a Teams chat grants an agent no new access: admins enable it chat by chat and decide which actions are allowed, need approval or are blocked, and its Azure permissions stay with its managed identity. An Entra Agent ID with an accountable sponsor puts SRE agents in the same registry and Defender and Purview monitoring as the rest of the tenant's agents, which security teams will want before agents work in production.

Identity for agentsAgent governanceMCP & agent interoperability

Official sources

Community deep dives

0 links · newest first
Written or recorded something about this?It goes to the moderators with this recap attached. No account needed, and you can get the credit.
Add a link to this recap