← cd ~/roles
// roles/azure · containers
Connected Cluster Managed Identity CheckAccess ReaderAzure built-in role
Built-in role that allows a Connected Cluster managed identity to call the checkAccess API
| Role ID | 65a14201-8f6c-4c28-bec4-12619c5a9aaa |
|---|---|
| Category | Containers |
| Actions | 1 |
| Data actions | 0 |
What it can do
| Permission | What it allows |
|---|---|
Microsoft.Authorization/*/read | Any read operation on anything under Microsoft.Authorization |
Assign it
Scope it as tightly as you can: a resource or resource group rather than the whole subscription.
az role assignment create \
--assignee "jane.doe@contoso.com" \
--role "Connected Cluster Managed Identity CheckAccess Reader" \
--scope "/subscriptions/<subscription id>/resourceGroups/<resource group>"New-AzRoleAssignment -SignInName "jane.doe@contoso.com" `
-RoleDefinitionName "Connected Cluster Managed Identity CheckAccess Reader" `
-Scope "/subscriptions/<subscription id>/resourceGroups/<resource group>"resource assignment 'Microsoft.Authorization/roleAssignments@2022-04-01' = {
name: guid(resourceGroup().id, principalId, '65a14201-8f6c-4c28-bec4-12619c5a9aaa')
properties: {
roleDefinitionId: subscriptionResourceId('Microsoft.Authorization/roleDefinitions', '65a14201-8f6c-4c28-bec4-12619c5a9aaa')
principalId: principalId
}
}Who already has it?
authorizationresources
| where type == "microsoft.authorization/roleassignments"
| where tostring(properties.roleDefinitionId) endswith "65a14201-8f6c-4c28-bec4-12619c5a9aaa"
| project principalId = tostring(properties.principalId), principalType = tostring(properties.principalType), scope = tostring(properties.scope)Other containers roles
- AcrDelete · 1 permission
- AcrPull · 1 permission
- Container Registry Cache Rule Reader · 1 permission
- Container Registry Credential Set Reader · 1 permission
- Container Registry Repository Catalog Lister · 1 permission
- AcrImageSigner · 2 permissions
- AcrPush · 2 permissions
- AcrQuarantineReader · 2 permissions