Need help with Partner questions/issues

[MiguelRBarbosa]

Issue Description:

We are working with a Partner testing the Azure SRE Agent.
They have two situations and questions we need help with, pls:

1- When adding resource groups to the managed resource group in the SRE agent, not all resources are visible in the resource mapping, with some entire resource groups and specific resource types missing from the view. Is there a particular way to configure this? since this issue is not only in one tenant, it seems like a product issue. Could you please confirm? is only compute resources visible under viewer?

2- Inconsistent behavior of incident triggers and sub agent workflows in the SRE agent, where incidents are sometimes not fired or sub agents are not triggered as expected, despite correct alert configurations. Are there any known limitations or issues?

TPD DfM Case:
2601300010002188

[surivineela]

Hi @MiguelRBarbosa, please find the responses below:

1. The resource mapping view is working as designed — it uses an application-centric grouping model rather than a flat resource list. Only four resource types appear as top-level "Application Groups": App Services (web apps and function apps), AKS Clusters, Container App Environments, and API Management instances. All other resources in your managed resource groups — such as databases, storage accounts, Key Vaults, and networking components — are discovered by the agent's graph and displayed as dependency nodes connected to these primary application groups. If a resource group contains none of these four types, it won't show top-level entries in the map — but those resources are still fully managed and accessible through the agent's conversations, incident investigations, and scheduled tasks. This is consistent across tenants as it reflects the product's architecture, not a configuration issue.
2. Would need more details on the agent details to understand what's happening here - such as agent name, subscription, subagent and incident trigger config details.