SRE Agent support multiple subscriptions

Azure SRE Agent isn’t limited to just one subscription. If you connect environments using Azure Lighthouse and set up the right permissions, a single agent can work across multiple subscriptions even across different tenants.

There’s also no strict cap on how many subscriptions or resource groups an agent can manage. In practice, the limits come down to how you’ve configured permissions and Azure’s general service boundaries.

From a cost perspective, things are fairly predictable. Each agent has a small, fixed “always-on” cost, and then you only pay extra when it’s actively doing work like investigating issues or applying fixes.

One of the biggest advantages is automation. Repetitive tasks, such as resizing virtual machines, can be handled through reusable scripts and runbooks. This not only saves time but also helps keep costs down by reducing how often the agent needs to step in.

The agent can also manage multiple tasks at the same time. Azure takes care of how those tasks run in parallel, so you don’t need to worry about tuning or managing concurrency yourself.

That said, it’s usually better not to make one agent responsible for everything. You’ll get better performance, security, and cost control by assigning agents to specific workloads or environments instead of using a single, all-purpose setup.

You can check the below links for more information

Cross-tenant management experiences - Azure Lighthouse | Microsoft Learn

Overview of Azure SRE Agent | Microsoft Learn

Pricing and billing for Azure SRE Agent | Microsoft Learn

Create and Use an agent in Azure SRE Agent | Microsoft Learn