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"
💡 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
| Property |
Value |
| Query Language |
KQL (Kusto Query Language subset) |
| CLI Command |
az graph query -q "<KQL>" -o table |
| Extension |
az extension add --name resource-graph |
| MCP Tool |
extension_cli_generate with intent for az graph query |
| Best For |
Cross-subscription queries, orphaned resources, tag audits |
MCP Tools
| Tool |
Purpose |
When to Use |
extension_cli_generate |
Generate az graph query commands |
Primary tool — generate ARG queries from user intent |
mcp_azure_mcp_subscription_list |
List available subscriptions |
Discover subscription scope before querying |
mcp_azure_mcp_group_list |
List resource groups |
Narrow 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 Type |
MCP Tool |
Coverage |
| Virtual Machines |
compute |
✅ Full — list, details, sizes |
| Storage Accounts |
storage |
✅ Full — accounts, blobs, tables |
| Cosmos DB |
cosmos |
✅ Full — accounts, databases, queries |
| Key Vault |
keyvault |
⚠️ Partial — secrets/keys only, no vault listing |
| SQL Databases |
sql |
⚠️ Partial — requires resource group name |
| Container Registries |
acr |
✅ Full — list registries |
| Kubernetes (AKS) |
aks |
✅ Full — clusters, node pools |
| App Service / Web Apps |
appservice |
❌ No list command — use ARG |
| Container Apps |
— |
❌ No MCP tool — use ARG |
| Event Hubs |
eventhubs |
✅ Full — namespaces, hubs |
| Service Bus |
servicebus |
✅ 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
| Error |
Cause |
Fix |
resource-graph extension not found |
Extension not installed |
az extension add --name resource-graph |
AuthorizationFailed |
No read access to subscription |
Check RBAC — need Reader role |
BadRequest on query |
Invalid KQL syntax |
Verify table/column names; use =~ for case-insensitive type matching |
| Empty results |
No matching resources or wrong scope |
Check --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)
1---2name: azure-resource-lookup3description: List, find, and show Azure resources. Answers "list my VMs", "show my storage accounts", "list websites", "find container apps", "what resources do I have", and similar queries for any Azure resource type. USE FOR: list resources, list virtual machines, list VMs, list storage accounts, list websi...4license: MIT5---6# Azure Resource Lookup
7
8List, 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.
9
10## When to Use This Skill
11
12Use this skill when the user wants to:
13- **List resources** of any type (VMs, web apps, storage accounts, container apps, databases, etc.)
14- **Show resources** in a specific subscription or resource group
15- Query resources **across multiple subscriptions** or resource types
16- Find **orphaned resources** (unattached disks, unused NICs, idle IPs)
17- Discover resources **missing required tags** or configurations
18- Get a **resource inventory** spanning multiple types
19- Find resources in a **specific state** (unhealthy, failed provisioning, stopped)
20- Answer "**what resources do I have?**" or "**show me my Azure resources**"
21
22> 💡 **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.
23
24## Quick Reference
25
26| Property | Value |
27|----------|-------|
28| **Query Language** | KQL (Kusto Query Language subset) |
29| **CLI Command** | `az graph query -q "<KQL>" -o table` |
30| **Extension** | `az extension add --name resource-graph` |
31| **MCP Tool** | `extension_cli_generate` with intent for `az graph query` |
32| **Best For** | Cross-subscription queries, orphaned resources, tag audits |
33
34## MCP Tools
35
36| Tool | Purpose | When to Use |
37|------|---------|-------------|
38| `extension_cli_generate` | Generate `az graph query` commands | Primary tool — generate ARG queries from user intent |
39| `mcp_azure_mcp_subscription_list` | List available subscriptions | Discover subscription scope before querying |
40| `mcp_azure_mcp_group_list` | List resource groups | Narrow query scope |
41
42## Workflow
43
44### Step 1: Check for a Dedicated MCP Tool
45
46For single-resource-type queries, check if a dedicated MCP tool can handle it:
47
48| Resource Type | MCP Tool | Coverage |
49|---|---|---|
50| Virtual Machines | `compute` | ✅ Full — list, details, sizes |
51| Storage Accounts | `storage` | ✅ Full — accounts, blobs, tables |
52| Cosmos DB | `cosmos` | ✅ Full — accounts, databases, queries |
53| Key Vault | `keyvault` | ⚠️ Partial — secrets/keys only, no vault listing |
54| SQL Databases | `sql` | ⚠️ Partial — requires resource group name |
55| Container Registries | `acr` | ✅ Full — list registries |
56| Kubernetes (AKS) | `aks` | ✅ Full — clusters, node pools |
57| App Service / Web Apps | `appservice` | ❌ No list command — use ARG |
58| Container Apps | — | ❌ No MCP tool — use ARG |
59| Event Hubs | `eventhubs` | ✅ Full — namespaces, hubs |
60| Service Bus | `servicebus` | ✅ Full — queues, topics |
61
62If a dedicated tool is available with full coverage, use it. Otherwise proceed to Step 2.
63
64### Step 2: Generate the ARG Query
65
66Use `extension_cli_generate` to build the `az graph query` command:
67
68```yaml
69mcp_azure_mcp_extension_cli_generate
70 intent: "query Azure Resource Graph to <user's request>"
71 cli-type: "az"
72```
73
74See [Azure Resource Graph Query Patterns](references/azure-resource-graph.md) for common KQL patterns.
75
76### Step 3: Execute and Format Results
77
78Run the generated command. Use `--query` (JMESPath) to shape output:
79
80```bash
81az graph query -q "<KQL>" --query "data[].{name:name, type:type, rg:resourceGroup}" -o table
82```
83
84Use `--first N` to limit results. Use `--subscriptions` to scope.
85
86## Error Handling
87
88| Error | Cause | Fix |
89|-------|-------|-----|
90| `resource-graph extension not found` | Extension not installed | `az extension add --name resource-graph` |
91| `AuthorizationFailed` | No read access to subscription | Check RBAC — need Reader role |
92| `BadRequest` on query | Invalid KQL syntax | Verify table/column names; use `=~` for case-insensitive type matching |
93| Empty results | No matching resources or wrong scope | Check `--subscriptions` flag; verify resource type spelling |
94
95## Constraints
96
97- ✅ **Always** use `=~` for case-insensitive type matching (types are lowercase)
98- ✅ **Always** scope queries with `--subscriptions` or `--first` for large tenants
99- ✅ **Prefer** dedicated MCP tools for single-resource-type queries
100- ❌ **Never** use ARG for real-time monitoring (data has slight delay)
101- ❌ **Never** attempt mutations through ARG (read-only)
JantonioFC