Edit

Authorize access to blob access points

Blob access points use two kinds of authorization:

  • Management operations on blob access point configurations use Azure role-based access control (Azure RBAC) on the storage account.
  • Data operations on a blob access point use the same authorization methods as any other container.

Separately, Azure Storage uses the data source credentials that you store in the configuration to read from your data source.

Permission to allow blob access point creation

To allow or block blob access point creation on a storage account, you need permission to update the storage account (Microsoft.Storage/storageAccounts/write). The Storage Account Contributor, Contributor, and Owner roles include this permission.

Permissions to manage configurations

The following actions control blob access point configurations.

Action Lets you
Microsoft.Storage/storageAccounts/blobAccessPointConfigurations/read Get and list configurations
Microsoft.Storage/storageAccounts/blobAccessPointConfigurations/write Create and update configurations
Microsoft.Storage/storageAccounts/blobAccessPointConfigurations/delete Delete configurations
Microsoft.Storage/storageAccounts/blobAccessPointConfigurations/testExistingConnection/action Test the connection to the data source
Microsoft.Storage/storageAccounts/testBlobAccessPointConfigurationProposedConnection/action Test new connection settings before you apply them

The following built-in roles include these actions:

  • Storage Account Contributor. This role is enough to allow blob access point creation and to create and manage configurations, in the Azure portal or with the REST API.
  • Contributor and Owner. These roles also include the actions, but they grant broader access than you need.
  • Storage Blob Access Point Contributor (preview). This role lets you manage configurations, test connections, create blob access points, and read data. It doesn't include permission to update the storage account, so it can't allow or block blob access point creation.

To create a custom role, include Microsoft.Storage/storageAccounts/read and the blobAccessPointConfigurations and testBlobAccessPointConfigurationProposedConnection actions that you need. For more information, see Azure custom roles.

Permissions to create a blob access point

A blob access point is a container. To create it, you need permission to create a container in the storage account (Microsoft.Storage/storageAccounts/blobServices/containers/write):

Permissions to read data

Every authorization method that works for a container also works for a blob access point:

For the best security, use Microsoft Entra ID instead of Shared Key. For more information, see Authorize access to data in Azure Storage.

How Azure Storage uses data source credentials

When you create a configuration, you provide an access key ID and a secret access key for your data source. Azure Storage uses these credentials to read from the data source on behalf of every caller that you authorize on the blob access point.

  • The credentials are separate from your Azure identity. Azure RBAC controls who can read through the blob access point, and the credentials control what Azure Storage can read from the data source.
  • After you save the secret access key, you can't retrieve it from Azure. To change any credential setting, enter the secret access key again.
  • Use credentials that have read-only permissions on the bucket. Blob access points only read data, so they don't need write permissions.
  • Rotate the credentials regularly. For steps, see Update credentials.

Govern blob access points with Azure Policy

No built-in Azure Policy definition exists for blob access points. To audit or block blob access point creation across your organization, create a custom policy definition that checks the allowBlobAccessPoints property of storage accounts. For more information, see What is Azure Policy?