Choose how to authorize access to blob data in the Azure portal
When you access blob 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 Microsoft Entra 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.
You can also specify how to authorize an individual blob upload operation in the Azure portal. By default the portal uses whichever method you are already using to authorize a blob upload operation, but you have the option to change this setting when you upload a blob.
Permissions needed to access blob data
Depending on how you want to authorize access to blob 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 blob 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 blob 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 blob data. If you have not been assigned a role with this action, then the portal attempts to access data using your Microsoft Entra account.
Important
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 Microsoft Entra credentials to access blob data in the portal. For information about accessing blob data in the portal with Microsoft Entra ID, see Use your Microsoft Entra account.
Note
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 blob data with the account key. For more information, see Azure roles, Microsoft Entra roles, and classic subscription administrator roles.
Use your Microsoft Entra account
To access blob data from the Azure portal using your Microsoft Entra 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 blob 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 blob containers in the Azure portal.
For information about the built-in roles that support access to blob data, see Authorize access to blobs using Microsoft Entra ID.
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.
Navigate to blobs in the Azure portal
To view blob data in the portal, navigate to the Overview for your storage account, and click on the links for Blobs. Alternatively you can navigate to the Containers section in the menu.
Determine the current authentication method
When you navigate to a container, the Azure portal indicates whether you are currently using the account access key or your Microsoft Entra 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 Microsoft Entra 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 blobs appear in the list if your Microsoft Entra 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 Microsoft Entra account
If you are authenticating using your Microsoft Entra account, you'll see Microsoft Entra 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, you'll see an error message like the following one:
Notice that no blobs appear in the list if you do not have access to the account keys. Click on the Switch to Microsoft Entra user Account link to use your Microsoft Entra account for authentication again.
Specify how to authorize a blob upload operation
When you upload a blob from the Azure portal, you can specify whether to authenticate and authorize that operation with the account access key or with your Microsoft Entra credentials. By default, the portal uses the current authentication method, as shown in Determine the current authentication method.
To specify how to authorize a blob upload operation, follow these steps:
In the Azure portal, navigate to the container where you wish to upload a blob.
Select the Upload button.
Expand the Advanced section to display the advanced properties for the blob.
In the Authentication Type field, indicate whether you want to authorize the upload operation by using your Microsoft Entra account or with the account access key, as shown in the following image:
Default to Microsoft Entra authorization in the Azure portal
When you create a new storage account, you can specify that the Azure portal will default to authorization with Microsoft Entra ID when a user navigates to blob data. You can also configure this setting for an existing storage account. This setting specifies the default authorization method only, so keep in mind that a user can override this setting and choose to authorize data access with the account key.
To specify that the portal will use Microsoft Entra authorization by default for data access when you create a storage account, follow these steps:
Create a new storage account, following the instructions in Create a storage account.
On the Advanced tab, in the Security section, check the box next to Default to Microsoft Entra authorization in the Azure portal.
Select the Review + create button to run validation and create the account.
To update this setting for an existing storage account, follow these steps:
Navigate to the account overview in the Azure portal.
Under Settings, select Configuration.
Set Default to Microsoft Entra authorization in the Azure portal to Enabled.
The defaultToOAuthAuthentication property of a storage account is not set by default and does not return a value until you explicitly set it.
Next steps
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