Supported resource types and role assignments for Chaos Studio
The following table lists the supported resource types for faults, the target types, and suggested roles to use when you give an experiment permission to a resource of that type.
More information about role assignments can be found on the Azure built-in roles page.
Resource type | Target name/type | Suggested role assignment |
---|---|---|
Microsoft.Cache/Redis (service-direct) | Microsoft-AzureCacheForRedis | Redis Cache Contributor |
Microsoft.ClassicCompute/domainNames (service-direct) | Microsoft-DomainNames | Classic Virtual Machine Contributor |
Microsoft.Compute/virtualMachines (agent-based) | Microsoft-Agent | Reader |
Microsoft.Compute/virtualMachineScaleSets (agent-based) | Microsoft-Agent | Reader |
Microsoft.Compute/virtualMachines (service-direct) | Microsoft-VirtualMachine | Virtual Machine Contributor |
Microsoft.Compute/virtualMachineScaleSets (service-direct) | Microsoft-VirtualMachineScaleSet | Virtual Machine Contributor |
Microsoft.ContainerService/managedClusters (service-direct) | Microsoft-AzureKubernetesServiceChaosMesh | Azure Kubernetes Service Cluster Admin Role |
Microsoft.DocumentDb/databaseAccounts (Cosmos DB, service-direct) | Microsoft-Cosmos DB | Azure Cosmos DB Operator |
Microsoft.Insights/autoscalesettings (service-direct) | Microsoft-AutoScaleSettings | Web Plan Contributor |
Microsoft.KeyVault/vaults (service-direct) | Microsoft-KeyVault | Azure Key Vault Contributor |
Microsoft.Network/networkSecurityGroups (service-direct) | Microsoft-NetworkSecurityGroup | Network Contributor |
Microsoft.Web/sites (service-direct) | Microsoft-AppService | Website Contributor |
Microsoft.ServiceBus/namespaces (service-direct) | Microsoft-ServiceBus | Azure Service Bus Data Owner |
Microsoft.EventHub/namespaces (service-direct) | Microsoft-EventHub | Azure Event Hubs Data Owner |
Microsoft.LoadTestService/loadtests (service-direct) | Microsoft-AzureLoadTest | Load Test Contributor |
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for