Choose how to authorize access to queue data in the Azure portal
When you access queue data using the Azure portal, the portal makes requests to Azure Storage under the covers. A request to Azure Storage can be authorized using either your Azure AD account or the storage account access key. The portal indicates which method you are using, and enables you to switch between the two if you have the appropriate permissions.
Permissions needed to access queue data
Depending on how you want to authorize access to queue data in the Azure portal, you'll need specific permissions. In most cases, these permissions are provided via Azure role-based access control (Azure RBAC). For more information about Azure RBAC, see What is Azure role-based access control (Azure RBAC)?.
Use the account access key
To access queue data with the account access key, you must have an Azure role assigned to you that includes the Azure RBAC action Microsoft.Storage/storageAccounts/listkeys/action. This Azure role may be a built-in or a custom role. Built-in roles that support Microsoft.Storage/storageAccounts/listkeys/action include the following, in order from least to greatest permissions:
- The Reader and Data Access role
- The Storage Account Contributor role
- The Azure Resource Manager Contributor role
- The Azure Resource Manager Owner role
When you attempt to access queue data in the Azure portal, the portal first checks whether you have been assigned a role with Microsoft.Storage/storageAccounts/listkeys/action. If you have been assigned a role with this action, then the portal uses the account key for accessing queue data. If you have not been assigned a role with this action, then the portal attempts to access data using your Azure AD account.
When a storage account is locked with an Azure Resource Manager ReadOnly lock, the List Keys operation is not permitted for that storage account. List Keys is a POST operation, and all POST operations are prevented when a ReadOnly lock is configured for the account. For this reason, when the account is locked with a ReadOnly lock, users must use Azure AD credentials to access queue data in the portal. For information about accessing queue data in the portal with Azure AD, see Use your Azure AD account.
The classic subscription administrator roles Service Administrator and Co-Administrator include the equivalent of the Azure Resource Manager
Owner role. The Owner role includes all actions, including the Microsoft.Storage/storageAccounts/listkeys/action, so a user with one of these administrative roles can also access queue data with the account key. For more information, see Classic subscription administrator roles, Azure roles, and Azure AD administrator roles.
Use your Azure AD account
To access queue data from the Azure portal using your Azure AD account, both of the following statements must be true for you:
- You have been assigned either a built-in or custom role that provides access to queue data.
- You have been assigned the Azure Resource Manager Reader role, at a minimum, scoped to the level of the storage account or higher. The Reader role grants the most restricted permissions, but another Azure Resource Manager role that grants access to storage account management resources is also acceptable.
The Azure Resource Manager Reader role permits users to view storage account resources, but not modify them. It does not provide read permissions to data in Azure Storage, but only to account management resources. The Reader role is necessary so that users can navigate to queues in the Azure portal.
For information about the built-in roles that support access to queue data, see Authorize access to queues using Azure Active Directory.
Custom roles can support different combinations of the same permissions provided by the built-in roles. For more information about creating Azure custom roles, see Azure custom roles and Understand role definitions for Azure resources.
The preview version of Storage Explorer in the Azure portal does not support using Azure AD credentials to view and modify queue data. Storage Explorer in the Azure portal always uses the account keys to access data. To use Storage Explorer in the Azure portal, you must be assigned a role that includes Microsoft.Storage/storageAccounts/listkeys/action.
Navigate to queues in the Azure portal
To view queue data in the portal, navigate to the Overview for your storage account, and click on the links for Queues. Alternatively you can navigate to the Queue service section in the menu.
Determine the current authentication method
When you navigate to a queue, the Azure portal indicates whether you are currently using the account access key or your Azure AD account to authenticate.
Authenticate with the account access key
If you are authenticating using the account access key, you'll see Access Key specified as the authentication method in the portal:
To switch to using Azure AD account, click the link highlighted in the image. If you have the appropriate permissions via the Azure roles that are assigned to you, you'll be able to proceed. However, if you lack the right permissions, you'll see an error message like the following one:
Notice that no queues appear in the list if your Azure AD account lacks permissions to view them. Click on the Switch to access key link to use the access key for authentication again.
Authenticate with your Azure AD account
If you are authenticating using your Azure AD account, you'll see Azure AD User Account specified as the authentication method in the portal:
To switch to using the account access key, click the link highlighted in the image. If you have access to the account key, then you'll be able to proceed. However, if you lack access to the account key, the Azure portal displays an error message.
Queues are not listed in the portal if you do not have access to the account keys. Click on the Switch to Azure AD User Account link to use your Azure AD account for authentication again.