azure-resource-lookup

Azure Resource Graph uses KQL to query and list orphaned resources across multiple subscriptions via safe read-only operations. You can scope queries to specific subscriptions and identify unattached or misconfigured items for operational follow-up.

The best way to inventory Azure resources by type and location is querying Azure Resource Graph with KQL. You can group resources by type, display their location and resource group, and count instances using case-insensitive matching for audit scenarios.

Yes, you can validate tag coverage for Azure resources using KQL within Azure Resource Graph. The query identifies resources with missing tags across scoped subscriptions and resource groups, supporting audit and compliance checks.

Yes, Azure Resource Graph supports cross-subscription resource discovery. You can scope queries to multiple subscriptions to list resources, count by type, and find specific resource types using safe read-only operations and case-insensitive type matching.

To list Azure resources within a specific resource group, scope your KQL query in Azure Resource Graph to that specific resource group. This filters results to show targeted resources, their types, locations, and provisioning states for troubleshooting.

Limitations of Azure Resource Graph for resource audits include subscription scoping limits and a strict requirement for safe read-only operations. Query results depend on case-insensitive type matching and may not capture real-time provisioning state changes.