azureblog.co.uk
← cd ~/roles
// roles/azure · storage

Storage Queue Data Message ProcessorAzure built-in role

Allows for peek, receive, and delete access to Azure Storage queue messages

Role ID8a0f0c08-91a1-4084-bc3d-661d67233fed
CategoryStorage
Actions0
Data actions2

Before you assign it

  • It reaches the data, not just the resource. It has 2 data actions, such as reading blobs, secrets or messages.

What it can do

No control-plane actions.

Data actions

PermissionWhat it allows
Microsoft.Storage/storageAccounts/queueServices/queues/messages/readReturns a message
Microsoft.Storage/storageAccounts/queueServices/queues/messages/process/actionReturns the result of processing a message

Assign it

Scope it as tightly as you can: a resource or resource group rather than the whole subscription.

azure cli
az role assignment create \
  --assignee "jane.doe@contoso.com" \
  --role "Storage Queue Data Message Processor" \
  --scope "/subscriptions/<subscription id>/resourceGroups/<resource group>"
powershell3 lines
New-AzRoleAssignment -SignInName "jane.doe@contoso.com" `
  -RoleDefinitionName "Storage Queue Data Message Processor" `
  -Scope "/subscriptions/<subscription id>/resourceGroups/<resource group>"
bicep7 lines
resource assignment 'Microsoft.Authorization/roleAssignments@2022-04-01' = {
  name: guid(resourceGroup().id, principalId, '8a0f0c08-91a1-4084-bc3d-661d67233fed')
  properties: {
    roleDefinitionId: subscriptionResourceId('Microsoft.Authorization/roleDefinitions', '8a0f0c08-91a1-4084-bc3d-661d67233fed')
    principalId: principalId
  }
}

Who already has it?

kql · azure resource graph
authorizationresources
| where type == "microsoft.authorization/roleassignments"
| where tostring(properties.roleDefinitionId) endswith "8a0f0c08-91a1-4084-bc3d-661d67233fed"
| project principalId = tostring(properties.principalId), principalType = tostring(properties.principalType), scope = tostring(properties.scope)

Other storage roles

Find the smallest role for a task →

Sources