Supported resources and Actions for Chaos Studio Workspaces

This article lists the Azure resource types that Chaos Studio Workspaces can target. For each resource type, it shows the Actions you can run and the Scenario templates that use them. Use it to check which faults are available for your resources before you build a custom Scenario. For example, to test a Service Bus outage, find Microsoft.ServiceBus/namespaces, pick an Action, and copy its actionId.

Find Actions for a resource type

Find your resource type in the following table. The Scenario templates column lists the supported Scenario templates that use an Action on that resource type. You can use every Action in a custom Scenario.

Faults inside an Azure Kubernetes Service (AKS) cluster, such as pod delete and network latency, aren't in this catalog. They run through the Chaos Studio extension for AKS. To shut down AKS nodes, use the scale set Actions. For more information, see AKS resilience testing with Chaos Studio Workspaces.

Use an Action in a custom Scenario

1. Find the Action in the Action reference. Copy its actionId.
2. Add the Action to a Scenario in the Scenario designer, or in a Microsoft.Chaos/workspaces/scenarios resource. For the resource structure and a Bicep example, see Create a custom Scenario.
3. Set the parameters that the Action requires. Set a duration for Continuous and Cancelable Actions.
4. Give the Workspace identity the recommended role, or a custom role with the same permissions. For more information, see Permissions and identity in Chaos Studio Workspaces and Create least-privilege roles.

The Workspace runs each Action against the discovered resources of its target type in the Workspace scope. To limit the resources, use resource filters or resource exclusions.

Action types

Each Action has one of three types. The type controls how the Action uses duration and what happens when the Action ends.

Action reference

The tables in this section come from the Workspaces Action catalog. Each actionId has the form <action name>/<major>.<minor>. Parameters marked required must have a value. Other parameters are optional.

Application and integration

Caching

The Reboot Action works on clustered and non-clustered Azure Cache for Redis instances. For a non-clustered cache, such as a Basic or Standard cache, don't set ShardId.

Compute

CPU pressure and physical memory pressure are agent-based Actions. For the operating system and VM requirements, see Agent-based Scenario requirements.

Databases

Messaging

Change subscription state and Change topic state are Discrete. They don't restore the original state. To restore it, add a later Action that sets desiredState to Active.

Networking

Storage

List Actions with the REST API

The Action catalog is also available through Azure Resource Manager. Use it to get the full parameter schema and the exact permissions that each Action needs.

1. Run the following command. Replace <subscription-id> with your subscription ID. The example uses the West Central US region.

   az rest --method get \
     --url "https://management.azure.com/subscriptions/<subscription-id>/providers/Microsoft.Chaos/locations/westcentralus/actions?api-version=2026-08-01-preview" \
     --query "value[].{name:name, type:properties.actionType, targets:properties.supportedTargetTypes[].targetType}"
   

2. Check the result. Each entry shows the Action name, its type, and its target resource types:

   {
     "name": "microsoft-documentdb-offlineregion",
     "targets": [
       "Microsoft.DocumentDb/databaseAccounts"
     ],
     "type": "Cancelable"
   }
   

Each Action also returns parametersSchema, supportedTargetTypes[].requiredPermissions, and recommendedRoles. The recommendedRoles property holds built-in role definition IDs. To build a least-privilege role from requiredPermissions, see Create least-privilege roles.

Report issues and request features

Azure Chaos Studio is developed in the open. To report a bug, request a feature, or ask a question about Workspaces, Scenarios, or the Azure CLI extension, open an issue in the Chaos Studio repository on GitHub. By filing an issue, you can track its progress and see requests from other customers.

Next steps

• Scenarios and outage templates for Chaos Studio Workspaces
• Permissions and identity in Chaos Studio Workspaces
• Manage Workspaces and Scenarios with the Azure CLI