PluginBench
Skill
Official
Pass
Audit score 90

azure-resource-lookup

microsoft/azure-skills

List, find, and discover Azure resources across subscriptions and resource groups using Azure Resource Graph.

SourceView on skills.sh

What is azure-resource-lookup?

This skill queries Azure resources of any type—VMs, web apps, storage accounts, container apps, and more—across subscriptions and resource groups. Use it when you need to inventory resources, find orphaned items, audit tags, or answer "what resources do I have?"

  • List resources of any type across subscriptions or resource groups
  • Query resources by state, tags, or configuration using Azure Resource Graph (ARG)
  • Discover orphaned resources like unattached disks and unused network interfaces
  • Find resources missing required tags or in unhealthy states
  • Count and inventory resources by type across multiple subscriptions
  • Route to dedicated MCP tools when available for single-resource-type queries

How to install azure-resource-lookup

npx skills add https://github.com/microsoft/azure-skills --skill azure-resource-lookup
Prerequisites
  • Azure CLI installed and authenticated
  • Resource Graph extension: `az extension add --name resource-graph`
  • Reader role or equivalent RBAC permissions on target subscriptions
Claude Code
Cursor
Windsurf
Cline

How to use azure-resource-lookup

  1. 1.Check if a dedicated MCP tool exists for your resource type (VMs, storage, Cosmos DB, etc.)
  2. 2.If no dedicated tool covers your need, use `extension_cli_generate` to build an Azure Resource Graph query
  3. 3.Specify your intent (e.g., "list web apps in my subscription" or "find unattached disks")
  4. 4.Execute the generated `az graph query` command with optional `--subscriptions` or `--first` flags to scope results
  5. 5.Use `--query` with JMESPath to shape the output table or JSON

Use cases

Good for
  • List all web apps or App Services in a subscription (no dedicated MCP list command)
  • Find unattached disks and orphaned network resources
  • Audit resources missing required tags across resource groups
  • Discover container apps or other resource types without dedicated tools
  • Get a complete resource inventory spanning multiple types and subscriptions
Who it's for
  • Azure administrators managing multi-subscription environments
  • DevOps engineers auditing resource inventory and compliance
  • Cloud architects discovering orphaned or unused resources
  • Teams performing tag-based governance and cost allocation analysis

azure-resource-lookup FAQ

When should I use this skill instead of a dedicated MCP tool?

Use this skill when querying App Services/web apps (no dedicated list command), container apps, or when you need cross-subscription queries. For single-resource-type queries like VMs or storage accounts, prefer dedicated MCP tools if available.

What query language does Azure Resource Graph use?

Azure Resource Graph uses KQL (Kusto Query Language), a subset of the full language. The skill generates KQL queries via `extension_cli_generate` based on your intent.

Can I use this skill to modify or deploy resources?

No. Azure Resource Graph is read-only. Use the `azure-deploy` skill for deployments and resource changes.

How do I scope queries to avoid timeouts on large tenants?

Use the `--subscriptions` flag to target specific subscriptions, or use `--first N` to limit result count. Always use `=~` for case-insensitive resource type matching.

What if I get an AuthorizationFailed error?

You lack read access to the target subscription. Ensure your Azure account has at least Reader role on the subscriptions you're querying.

Full instructions (SKILL.md)

Source of truth, from microsoft/azure-skills.


name: azure-resource-lookup description: "List, find, and show Azure resources across subscriptions or resource groups. Handles prompts like "list the websites in my subscription", "list my web apps", "show my app services", "list virtual machines", "list my VMs", "show storage accounts", "find container apps", and "what resources do I have". USE FOR: list websites, list web apps, list app services, show websites in subscription, resource inventory, find resources by tag, tag analysis, orphaned resource discovery (not for cost analysis), unattached disks, count resources by type, cross-subscription lookup, and Azure Resource Graph queries. DO NOT USE FOR: deploying/changing resources (use azure-deploy), cost optimization (use cost-optimization from the optional azure-cost plugin), or non-Azure clouds." license: MIT metadata: author: Microsoft version: "1.2.2"

Azure Resource Lookup

List, find, and discover Azure resources of any type across subscriptions and resource groups. Use Azure Resource Graph (ARG) for fast, cross-cutting queries when dedicated MCP tools don't cover the resource type.

When to Use This Skill

Use this skill when the user wants to:

  • List resources of any type (VMs, web apps, storage accounts, container apps, databases, etc.)
  • Show resources in a specific subscription or resource group
  • Query resources across multiple subscriptions or resource types
  • Find orphaned resources (unattached disks, unused NICs, idle IPs)
  • Discover resources missing required tags or configurations
  • Get a resource inventory spanning multiple types
  • Find resources in a specific state (unhealthy, failed provisioning, stopped)
  • Answer "what resources do I have?" or "show me my Azure resources"
  • List web apps, websites, or App Services

⚠️ Warning: App Service / Web Apps have no dedicated MCP list command. Prompts like "list websites", "list web apps", or "list app services" must route through this skill to use Azure Resource Graph.

💡 Tip: For single-resource-type queries, first check if a dedicated MCP tool can handle it (see routing table below). If none exists, use Azure Resource Graph.

Quick Reference

PropertyValue
Query LanguageKQL (Kusto Query Language subset)
CLI Commandaz graph query -q "<KQL>" -o table
Extensionaz extension add --name resource-graph
MCP Toolextension_cli_generate with intent for az graph query
Best ForCross-subscription queries, orphaned resources, tag audits

MCP Tools

ToolPurposeWhen to Use
extension_cli_generateGenerate az graph query commandsPrimary tool — generate ARG queries from user intent
mcp_azure_mcp_subscription_listList available subscriptionsDiscover subscription scope before querying
mcp_azure_mcp_group_listList resource groupsNarrow query scope

Workflow

Step 1: Check for a Dedicated MCP Tool

For single-resource-type queries, check if a dedicated MCP tool can handle it:

Resource TypeMCP ToolCoverage
Virtual Machinescompute✅ Full — list, details, sizes
Storage Accountsstorage✅ Full — accounts, blobs, tables
Cosmos DBcosmos✅ Full — accounts, databases, queries
Key Vaultkeyvault⚠️ Partial — secrets/keys only, no vault listing
SQL Databasessql⚠️ Partial — requires resource group name
Container Registriesacr✅ Full — list registries
Kubernetes (AKS)aks✅ Full — clusters, node pools
App Service / Web Appsappservice❌ No list command — use ARG
Container Apps—❌ No MCP tool — use ARG
Event Hubseventhubs✅ Full — namespaces, hubs
Service Busservicebus✅ Full — queues, topics

If a dedicated tool is available with full coverage, use it. Otherwise proceed to Step 2.

Step 2: Generate the ARG Query

Use extension_cli_generate to build the az graph query command:

mcp_azure_mcp_extension_cli_generate
  intent: "query Azure Resource Graph to <user's request>"
  cli-type: "az"

See Azure Resource Graph Query Patterns for common KQL patterns.

Step 3: Execute and Format Results

Run the generated command. Use --query (JMESPath) to shape output:

az graph query -q "<KQL>" --query "data[].{name:name, type:type, rg:resourceGroup}" -o table

Use --first N to limit results. Use --subscriptions to scope.

Error Handling

ErrorCauseFix
resource-graph extension not foundExtension not installedaz extension add --name resource-graph
AuthorizationFailedNo read access to subscriptionCheck RBAC — need Reader role
BadRequest on queryInvalid KQL syntaxVerify table/column names; use =~ for case-insensitive type matching
Empty resultsNo matching resources or wrong scopeCheck --subscriptions flag; verify resource type spelling

Constraints

  • ✅ Always use =~ for case-insensitive type matching (types are lowercase)
  • ✅ Always scope queries with --subscriptions or --first for large tenants
  • ✅ Prefer dedicated MCP tools for single-resource-type queries
  • ❌ Never use ARG for real-time monitoring (data has slight delay)
  • ❌ Never attempt mutations through ARG (read-only)