Build 2026 Update
When we launched Azure SRE Agent, the promise was simple: reduce operational toil, improve up time, and evolve teams from manual incident response towards AI-powered operations. Since GA in March 2026, that promise has held up in production. Teams are using the agent to diagnose live issues, reason across telemetry and code, and automate response workflows - and the footprint has grown fast.
But there's a gap between an agent that works in a dev/test environment and one that works in your production environment. Real production environments sits behind a private network with strict egress rules for enterprise security. Their code lives in a GitHub Enterprise tenant that a consumer OAuth sign-in can't reach. Platform teams need to govern what the agent can learn and use, and connectors must scale across many tools and many teams.
At Microsoft Build 2026, we're announcing five releases that take a major step toward enterprise adoption at scale:
- VNet integration Preview - Run SRE Agent inside your private Azure workloads, with full support for enterprise network boundaries and private connectivity.
- Managed Connectors - A redesigned connector experience for governing, securing and scaling connections across observability, incident management, code, and collaboration tools plus an expanded SaaS connector catalog including Jira, GitLab, Slack, Power BI, and more.
- Granular permissions model - Set allow, ask, and deny rules on individual tools. Admins can set guardrails that apply everywhere; Agent users can approve tools for the rest of their conversation without waiting on policy changes.
- Native GitHub Enterprise support - Ground investigations in your enterprise repositories and workflows, so an incident can become an issue, an investigation, a pull request, and a repair plan — all under a governed service identity.
- Private Plugins Marketplace - Give platform teams a governed way to publish approved skills, MCP tools, and operational workflows to every SRE Agent in the tenant.
Together with our Infrastructure-as-Code templates, these releases make Azure SRE Agent easy to integrate into secure environments with locked-down networks, regulated teams and complex codebases.
Read the series
- VNet integration - https://aka.ms/sreagent/blog/VNET
- Managed Connectors - https://aka.ms/sreagent/blog/connectorsv2
- SRE Agent permissions model - https://aka.ms/sreagent/blog/HooksAndToolPermissions
- Native GitHub Enterprise support - https://aka.ms/sreagent/blog/githubenterprise
- Private Plugins Marketplace - https://aka.ms/sreagent/blog/privatepluginmarketplace
📺 Watch the on-demand session from #MSBuild 2026 - https://aka.ms/sreagent/build26
Get started
- Create an SRE Agent — https://aka.ms/sreagent
- Documentation — https://aka.ms/sreagent/newdocs
- Recipes — https://aka.ms/sreagent/recipes
What's next
We're exploring Microsoft Entra Agent ID for first-class agent identity and Microsoft Agent 365 integration for centralized agent governance. What enterprise controls would unlock adoption in your production environments? Tell us in the comments below
Microsoft