Azure SRE Agent topics

SRE Agent support multiple subscriptions

Pranab_Mandal — Wed, 25 Mar 2026 17:13:12 GMT

One of my Customer building 3 PoCs and they have few technical requirement that are unclear from the documents. It would be super helpful to get technical guidance and documentation supporting those requirements.

Does one agent can access resources across all subscriptions connected to a Lighthouse tenant. Their current infrastructure setup, where a single Lighthouse tenant is used to manage multiple underlying tenants and their subscriptions. In this scenario if an SRE agent in one subscription could access resources across all these subscriptions. Is there an upper limit?
Is there a upper limit for number of resource group an SRE agent can manage per subscription?
Are there cost optimization best practices for scenarios like pre-recorded scripts or agent-level improvements for repetitive tasks in their case VM resizing?
From billing standpoint does always-on agent connections incur charges even when no alerts are active?
When handling multiple remediation tasks or queries, does the agent execute them sequentially or in parallel? Additionally, is there any control or configuration available for managing concurrency?

What are the recommended guardrails for...

sultanofsuede — Thu, 26 Feb 2026 17:58:54 GMT

Preventing the agent from making changes to any Azure resource?

Companies who have heard stories about hallucinations, etc. believe that the agent is a threat their production systems potentially.

From what I can tell, the agent can be given a managed identity that has limited rights to Azure resources. Read/list, etc.

Without guardrails, adoption of this tech will be difficult in some environments.

"But the hallucinations..."

I'm not sure it's a great idea to let an agent make changes to a production system... or even suggest doing it "for" the benefit of the on-call. It's too easy to screw up.

What is the guidance here? Managed identity with RBAC?

Does Azure SRE Agent support working with Private AKS cluster ?

Sreekumar — Wed, 18 Feb 2026 07:51:30 GMT

While I have my AKS cluster in private and wanted to connect with SRE agent but I don't find a related information on the docs about it

Diagnosing Java performance issues in Kubernetes just got easier!

Mayunk_Jain — Wed, 21 Jan 2026 07:09:40 GMT

Manual troubleshooting is slow and painful—but what if you could automate it?

Introducing the Azure Performance Diagnostics Tool for Java, powered by Azure SRE Agent. It delivers automated insights into JVM health, thread dumps, and memory usage—so you can resolve issues in minutes, not hours.

✅ Kubernetes-native
✅ Deep JVM visibility
✅ Faster root cause analysis

👉 Learn more: https://aka.ms/sreagent/javaperf

#YearInReview insights from the last few months building Azure SRE Agent...

Mayunk_Jain — Mon, 29 Dec 2025 21:13:43 GMT

To kick things off, sanchitmehta and visagarwal just shared a great deep dive on context engineering for reliable AI agents, and it’s a must‑read if you’re building or operating agents in real systems.

The core idea: reliability doesn’t come from bigger models alone—it comes from how well you design, structure, and control context. The post breaks down practical lessons learned from building real agent flows, including how context boundaries, memory, and guardrails directly impact consistency, debugging, and trust.

If you’ve ever asked:

Why does my agent behave differently run to run?
How do I make agent decisions more predictable?
Where should logic live vs. prompts?

This write‑up tackles those questions with concrete examples, especially relevant for folks working with Azure SRE Agent or thinking about agent reliability in production systems.

Give it a read, drop your thoughts here, and share how you’re approaching context design in your own agents. Curious what’s worked—or not—for you 👇

Welcome to Azure SRE Agent community hub

Mayunk_Jain — Mon, 29 Dec 2025 21:05:14 GMT

If you’re building, running, or breaking things with Azure SRE Agent, this space is for you.

We’re excited to open the Azure SRE Agent Community Hub—a new discussion space where developers and reliability engineers can hang out, swap ideas, ask questions, and help each other level up. You can jump in here:
👉 https://aka.ms/sreagent/discussions

This isn’t meant to be a one-way announcement board or a place for polished presentations. It’s a living, breathing discussion space powered by the people using SRE Agent in the real world. Whether you’re just getting started or you’re already pushing limits, there’s value in sharing what you’re learning along the way.

Have a question that you couldn’t find answered in the docs? Ask it.
Discovered a neat trick or workaround? Post it.
Trying something new and want feedback? Start a thread.

The hub is only as good as the conversations that happen here—so don’t be shy. Post early, post often, and jump into discussions even if you’re not 100% sure you have the “perfect” answer. Chances are someone else is wondering the same thing, or can build on what you share.

We especially want this to be a home for community champions—people who enjoy helping others, learning out loud, and shaping where this technology goes next. And if you know someone else working with Azure SRE Agent, invite them in. More voices = better conversations.

To stay up to date on deeper stories, product updates, and real-world use cases, make sure to also follow the blogs:
👉 http://aka.ms/sreagent/blogs

See you in the discussions—and welcome to the community 🚀