Query Azure Resources Across All Subscriptions with Azure Resource Graph

The Problem: You need to find specific resources across multiple Azure subscriptions, but clicking through the portal one subscription at a time is painfully slow.

The Nugget: Azure Resource Graph lets you query all your Azure resources across every subscription in seconds—using a simple query language similar to KQL.

How to Access:

• Open Azure Portal

• Search for “Resource Graph Explorer”

• Start querying

Example Query – Find All VMs Not Running:

kusto

resources | where type == “microsoft.compute/virtualmachines” | extend vmState = tostring(properties.extended.instanceView.powerState.code) | where vmState != “PowerState/running” | project name, resourceGroup, subscriptionId, vmState

Why This Matters:

• Searches across ALL subscriptions instantly

• No need for multiple Azure CLI loops

• Results exportable to CSV

• Can be saved as shared queries for your team

Bonus: Pin your most-used queries to an Azure Dashboard for one-click access to cross-subscription insights.

Pro Tip: Use summarize count() by type to get a quick inventory of all resource types in your environment.

Admin context

For Microsoft admins, the practical point in Query Azure Resources Across Subscriptions w/ Azure is to treat the change as something that should be validated before it becomes tenant-wide behavior. Check the affected users, devices, assignments and support process so the Nugget turns into a controlled operational improvement instead of another undocumented setting.

Operational follow-up

As an additional operational note, Query Azure Resources Across All Subscriptions with Azure Resource Graph should be reviewed together with your existing Microsoft 365 change process. Even small platform changes can affect helpdesk instructions, user communication, device targeting, reporting expectations and the way administrators explain the result to stakeholders.

Runbook notes for Query Azure Resources Across All Subscriptions with Azure Resource Graph

Query Azure Resources Across All Subscriptions with Azure Resource Graph deserves a little more operational context because the decision usually affects cross-subscription visibility. The related items are Azure Resource Graph, KQL, subscriptions, resource inventory, governance reports. Treat this Nugget as a starting point for a concrete tenant decision: who is in scope, which Microsoft portal or policy is touched, and what visible result should confirm that the configuration worked.

When validating Query Azure Resources Across All Subscriptions with Azure Resource Graph, keep the test narrow enough to understand the result. Select one representative user, device, workload or subscription, capture the current state, then apply the change and compare the outcome. This avoids guessing later when support sees a different enrollment state, access result, model response, update status or admin center signal.

The most useful documentation for Query Azure Resources Across All Subscriptions with Azure Resource Graph is practical rather than theoretical. Record the assignment logic, the owner, the expected monitoring view and the exception path. If the change affects users, include the wording support teams should use when they explain the behavior. If it affects devices or services, include the exact place where administrators can verify health.

For search consistency, keep the phrase Query Azure Resources Across All Subscriptions with Azure Resource Graph connected to the body text, the internal links and the category context. That helps readers understand why this Microsoft admin topic belongs with the surrounding Intune, Entra, Azure, Copilot, Security or automation Nuggets, and it gives AI search systems clearer signals about the real subject of the page.

Revisit Query Azure Resources Across All Subscriptions with Azure Resource Graph after the next rollout wave or Microsoft service update. Cloud behavior, licensing boundaries and portal labels can move quickly, so a short review prevents stale instructions. Confirm that the original assumption is still true, remove obsolete exceptions, and update the runbook if the operating model changed.

A clean handover for Query Azure Resources Across All Subscriptions with Azure Resource Graph should also include a fallback. Write down how the team pauses the change, narrows the scope, or returns to the previous configuration if the result creates noise. This makes the Nugget safer to use in production because the implementation path includes both the happy path and the recovery path.