How to Find Azure Resources Across Subscriptions with Resource Graph Explorer

Azure Resource Graph Explorer helps you query Azure Resource Manager resource information at scale. It is useful when the portal’s resource lists are too narrow or when you need to find resources across subscriptions and compare properties such as type, location, tags, or names.

What Resource Graph Explorer is for

Resource Graph uses a Kusto Query Language (KQL) style query experience to return resource and property data. The default Resources table contains most Resource Manager resource types and properties. Microsoft recommends using the table name explicitly when queries use joins or unions. [1]

1. Open Resource Graph Explorer

1. Sign in to the Azure portal.
2. Search for Resource Graph.
3. Select Resource Graph Explorer.
4. If needed, select Directory to change the directory, management group, or subscription scope.

The query scope controls which resources can appear. If you do not define a subscription or management-group scope, the available scope follows the context and permissions of the signed-in user. [2]

2. Run a first query

Paste this query into the editor and select Run query:

resources
| project name, type
| limit 20

The project operator limits the returned columns. The limit operator limits the number of rows. Starting with a small result set makes it easier to understand the data before adding more conditions.

3. Filter by resource type or location

Use where to narrow the result set. For example, to list virtual machines in a region:

Resources
| where type =~ 'microsoft.compute/virtualmachines'
| where location =~ 'canadacentral'
| project name, resourceGroup, subscriptionId, location
| order by name asc

Resource Graph supports operators such as where, project, sort, summarize, count, join, and union, subject to Resource Graph limits. [1]

4. Find resources by tag

Tags are stored in the resource properties, so you can query them directly. This example finds resources with an environment tag:

Resources
| where tostring(tags['Environment']) =~ 'Production'
| project name, type, resourceGroup, subscriptionId, location, tags

Use consistent tag names and values across subscriptions. Inconsistent capitalization or labels will produce incomplete results even when the resources are otherwise similar.

5. Review the schema browser

Use the schema browser in the left pane to inspect available tables, resource types, and properties. Selecting a resource type adds a starter filter to the query. Replace placeholder values and adjust the query with the conditions you actually need. [2]

6. Save, export, or chart the results

• Use Download as CSV to export query results. Microsoft documents a 55,000-record limit for this portal export.
• Use Save to store a useful private query for later use.
• Use the Charts tab for count-based query results.
• Use Pin to dashboard to keep a query or visualization visible in an Azure dashboard.

Charts work best for queries that return counts or other compatible aggregations. Lists can still be pinned, but they may not be compatible with donut or bar chart visualizations. [2]

Common mistakes

• Running the query against only one subscription when the inventory needs a management-group scope.
• Returning every property instead of projecting a small, useful set of columns.
• Filtering on a tag value that is not standardized across resources.
• Assuming all KQL operators and functions work exactly as they do in Log Analytics.

Sources

1. Microsoft Learn: Understand the Azure Resource Graph query language
2. Microsoft Learn: Quickstart — Run Resource Graph query using Azure portal
3. Microsoft Learn: Overview of Azure Resource Graph