List Resources
azure_compute.list_resources
ActionMicrosoft Azureconnection required
Calls Azure Resource Manager GET /subscriptions/{id}/resources with a resourceType filter, which answers for every tracked type.
List Microsoft.Compute resources — availabilitySets, capacityReservationGroups, cloudServices, diskAccesses, diskEncryptionSets, disks….
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Azure Compute
- Secret shape
- {"tenant_id", "client_id", "client_secret"}
- Config it needs
- subscription_id, resource_group
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
subscription_id Azure subscription id (overrides the connection). | string | No | — | — | — |
resource_type Which Microsoft.Compute resource type to address. | string | No | virtualMachines | one of "availabilitySets", "capacityReservationGroups", "cloudServices", "diskAccesses", "diskEncryptionSets", "disks", "galleries", "hostGroups", "images", "interconnectBlocks", "proximityPlacementGroups", "restorePointCollections", "snapshots", "sshPublicKeys", "virtualMachineScaleSets", "virtualMachines" | — |
resource_group Limit to one resource group (blank = whole subscription). | string | No | — | — | — |
top Maximum resources to return. | number | No | — | ≥ 1 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"resource_type": "virtualMachines"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
value | array | — |
count | number | — |
{
"count": 0,
"value": []
}Related Azure Compute nodes
See List Resources run in a workflow.
In a technical demo we add the Azure Compute connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.