
Azure Resource Graph (ARG) fixes that with fast, read-only queries across everything you can access. This guide covers the service, Resource Graph Explorer, KQL query construction, enterprise use cases, comparisons with related services, and the limits to plan around.
One boundary up front: ARG answers inventory and configuration questions. It doesn't replace Azure Monitor telemetry, Cost Management, or identity services.
Key Takeaways
- ARG runs read-only KQL-based queries across every subscription you can access.
- Resource Graph Explorer is the fastest place to inspect schemas and test queries.
- Strong queries combine filtering, projection, aggregation, and a deliberate scope.
- Check permissions, freshness, pagination, and throttling against current Microsoft documentation.
What Is Azure Resource Graph and How Does It Work?
Azure Resource Graph (ARG) is an Azure service for exploring resource metadata and configuration across subscriptions, management groups, or your whole tenant. Microsoft's overview describes it as efficient, performant resource exploration with cross-subscription querying for governance.
Data model and tables
Typical fields include name, ID, type, location, subscription, resource group, tags, SKU, and provider-specific properties. Exact availability varies by resource type.
- Resources is the default table for most resource types.
- ResourceContainers holds management groups, subscriptions, and resource groups.
- Specialized tables such as PolicyResources, GuestConfigurationResources, RecoveryServicesResources, and HealthResources cover specific services.
Check Microsoft's supported tables and resource types reference before assuming a type is queryable.
Indexed queries versus provider calls
ARG queries an index, so you avoid calling each resource provider through Azure Resource Manager (ARM) one resource at a time. The tradeoff is consistency.
ARM change notifications update the index, and periodic full scans catch anything missed, so data is not strongly consistent. For authoritative state, such as before a destructive operation, call the provider API directly.
ARG is also read-only. It reveals conditions; you change them through ARM, Azure Policy, scripts, or automation.
KQL in ARG
ARG supports a subset of Kusto Query Language. Operators you'll use most:
where,project,extend,summarize,sort,limitjoin,union,distinct,parse,mv-expand- Scalar functions for strings, arrays, and dynamic properties
Scope, access, and what ARG isn't
Results depend on your selected scope and your RBAC permissions. You need at least read access to a resource to see it. If only some subscriptions are accessible, you may get partial results; if none are, you get an HTTP 403.
ARG holds no CPU, memory, disk I/O, or application logs. For time-series telemetry, use Azure Monitor and Log Analytics.
Azure Resource Graph Explorer and Querying with KQL
Accessing Resource Graph Explorer
- Search for "resource graph" in the Azure portal and open Resource Graph Explorer.
- Set the Directory and scope (subscription, management group, or tenant).
- Open the schema browser on the left to see supported types and properties present in your tenant.
- Enter a query and run it.
- Review the Results tab; the Messages tab shows record count, duration, and errors.
Count-style queries can be charted and pinned to dashboards, and pins keep their scope. You can also save private queries or share them as RBAC-protected resources. Portal layouts change over time, so verify labels and navigation against the live experience.
Querying ARG outside the portal
The same KQL runs through several clients:
- Azure CLI:
az graph query -q "<KQL>"(the extension installs on first use) - PowerShell:
Search-AzGraphfrom theAz.ResourceGraphmodule - REST: a POST to the
Microsoft.ResourceGraph/resourcesendpoint - SDKs: for example, the Python
azure.mgmt.resourcegraphlibrary
Authentication, scope handling, output format, and pagination differ by client. A basic starting query:
Resources
| where type =~ 'microsoft.storage/storageaccounts'
| project name, location, resourceGroup, subscriptionId, tags
Building more useful queries
Start with a filter, then trim columns with project, derive values with extend, and group with summarize. Use =~ for case-insensitive type matching. Tag-value equality with == is case-sensitive.
An aggregation for reporting:
Resources
| summarize count() by type, location
| order by type asc
Dynamic properties need conversion. This counts VMs by OS type:
Resources
| where type =~ 'microsoft.compute/virtualmachines'
| summarize count() by tostring(properties.storageProfile.osDisk.osType)
For arrays, such as virtual network subnets, expand them first:
Resources
| where type =~ 'microsoft.network/virtualnetworks'
| extend subnets = properties.subnets
| mv-expand subnets
Aggregates like these feed workbooks, dashboards, and recurring reports directly.

Troubleshooting empty or odd results
- Confirm the selected scope.
- Verify you have read permission on the resources.
- Check type spelling and casing, and use
=~. - Inspect the schema for the real property path.
- Account for null or nested values.
- Confirm the resource type is supported.
- Remember recently created resources may not be indexed yet.
Making queries automation-ready
- Project stable, named columns and nothing extra.
- Record the scope each run used.
- Handle pagination: the page size is 1,000 records maximum, so use skip tokens for larger inventories.
- Sort by a unique key such as
idwhen paging. - Watch quota headers, and check current throttling guidance.
Queries have a 30-second timeout, and smaller scopes help.
Azure Resource Graph Use Cases for Enterprise Teams
Inventory and environment discovery
Build a cross-subscription inventory of VMs, storage accounts, managed disks, databases, networks, tags, regions, and SKUs without opening each resource. Tailor outputs by audience:
- ITOps: resource type, region, lifecycle and ownership tags
- DevOps: deployment context and resource group structure
- Security: exposed configuration settings
- FinOps: subscription, SKU, region, and owner dimensions
Governance, compliance, and configuration review
ARG surfaces missing tags, resources outside approved regions, unsupported SKUs, and configurations needing policy review. A missing-tag check:
Resources
| where isnull(tags['Environment']) or isnull(tags['CostCenter'])
| project name, type, resourceGroup, tags
Microsoft publishes sample queries for Azure Policy compliance states (PolicyResources) and guest configuration results. Change history supports drift detection and audits. It covers control-plane creates, updates, and deletes, and those records are retained for 14 days. Data-plane writes are excluded.

FinOps and storage visibility
ARG can find unattached managed disks, a common cost-review starting point:
Resources
| where type =~ 'microsoft.compute/disks'
| where isempty(managedBy)
| project name, resourceGroup, location, diskSizeGb=properties.diskSizeGB, sku=sku.name
Inventory alone doesn't prove low utilization or real savings. An unattached disk might be a deliberate standby, and an attached one can be mostly empty.
Complementary example: Teams that need continuous storage visibility beyond a point-in-time query can use Lucidity, a multi-cloud block storage management platform covering AWS, Azure, and Google Cloud. It monitors usage patterns and autonomously optimizes storage.
Lucidity states it can cut block storage costs by up to 70% without infrastructure changes. It is a separate product, not an ARG feature or integration.
Operations, monitoring, and alert context
Azure Monitor's arg() function lets you join ARG metadata with Log Analytics data, for example, filtering performance data to production-tagged resources. The integration is labeled preview, so verify syntax and permissions. Notable limits:
- Requires Log Analytics query-read permission plus ARG read access
- The ARG portion returns only the first 1,000 records
- Some functions, such as
arg_max()andpercentile(), are unsupported - Government clouds are unsupported
ARG-based log alerts also require a managed identity, with a maximum of 50 ARG log-search alert rules per identity.
Reporting, automation, and incident investigation
CLI, PowerShell, SDK, and REST workflows can export results into reports, dashboards, ticketing, or approved remediation pipelines. Azure Workbooks also has a native ARG query source.
During incidents, the change tables (resourcechanges, resourcecontainerchanges) help answer what changed and when. Records should appear in under five minutes, though details can arrive later. They don't replace activity logs, audit systems, or a full configuration management database.

How Azure Resource Graph Compares With Related Azure Services
Azure Resource Graph vs. Azure Resource Manager
ARG offers indexed, cross-scope reads for discovery and analysis. ARM creates, updates, deletes, and retrieves authoritative resource details. Use ARG to find candidates, then ARM to confirm and act.
Azure Resource Graph vs. Azure Monitor and Log Analytics
ARG describes what exists and how it's configured. Azure Monitor and Log Analytics hold metrics, logs, and events. Use one source when the question is purely inventory or purely performance, and arg() when you need both.
Azure Resource Graph vs. Azure AD Graph
These are unrelated. ARG queries Azure resource inventory. Azure AD Graph was an identity API that Microsoft is retiring in favor of Microsoft Graph. Microsoft's migration guide covers the path. Retirement dates differ across Microsoft pages, so confirm timing in current Entra documentation.
Best practices and limitations
- Grant least-privilege read access.
- Set explicit scopes, and don't assume tenant-wide coverage: tenant and management group scopes cover the first 10,000 accessible subscriptions.
- Treat partial results as a possibility.
- Test queries on small scopes first.
- Keep join and
mv-expandusage modest; SDK defaults allow three of each. - Document each query's owner, purpose, scope, expected output, refresh cadence, and downstream action.

Frequently Asked Questions
What is Azure Resource Graph?
An indexed, read-only service for querying Azure resource metadata and configuration across the scopes you can access. It doesn't hold Azure Monitor telemetry.
Is the Azure AD Graph deprecated?
Yes, but it's a different service from Azure Resource Graph. Follow Microsoft's Entra guidance to migrate to Microsoft Graph.
How do I open Azure Resource Graph Explorer?
Search "resource graph" in the Azure portal and open Resource Graph Explorer. Pick your scope, browse the schema, enter a query, and read the Results pane.
What query language does Azure Resource Graph use?
A subset of KQL. Start with where, project, extend, summarize, and sort.
What can Azure Resource Graph be used for?
Inventory, governance, compliance checks, configuration review, reporting, change investigation, and filtering Azure Monitor queries by resource properties.
How is Azure Resource Graph different from Azure Monitor?
Azure Resource Graph covers resource inventory and configuration. Azure Monitor covers metrics, logs, and events. In supported preview scenarios, you can query both together.