A shared access signature (SAS) enables you to grant limited access to containers and blobs in your storage account. When you create a SAS, you specify its constraints, including which Azure Storage resources a client is allowed to access, what permissions they have on those resources, and how long the SAS is valid.

Every SAS is signed with a key. You can sign a SAS in one of two ways:

• With a key created using Microsoft Entra credentials. A SAS that is signed with Microsoft Entra credentials is auser delegation SAS. A client that creates a user delegation SAS must be assigned an Azure RBAC role that includes theMicrosoft.Storage/storageAccounts/blobServices/generateUserDelegationKey action. To learn more, seeCreate a user delegation SAS.
• With the storage account key. Both aservice SAS and anaccount SAS are signed with the storage account key. The client that creates a service SAS must either have direct access to the account key or be assigned theMicrosoft.Storage/storageAccounts/listkeys/action permission. To learn more, seeCreate a service SAS orCreate an account SAS.

This article shows how to use Microsoft Entra credentials to create a user delegation SAS for a container or blob using theAzure Storage client library for Java.

About the user delegation SAS

A SAS token for access to a container or blob may be secured by using either Microsoft Entra credentials or an account key. A SAS secured with Microsoft Entra credentials is called a user delegation SAS, because the OAuth 2.0 token used to sign the SAS is requested on behalf of the user.

Microsoft recommends that you use Microsoft Entra credentials when possible as a security best practice, rather than using the account key, which can be more easily compromised. When your application design requires shared access signatures, use Microsoft Entra credentials to create a user delegation SAS for superior security. For more information about the user delegation SAS, seeCreate a user delegation SAS.

For more information about shared access signatures, seeGrant limited access to Azure Storage resources using shared access signatures (SAS).

Assign Azure roles for access to data

When a Microsoft Entra security principal attempts to access data, that security principal must have permissions to the resource. Whether the security principal is a managed identity in Azure or a Microsoft Entra user account running code in the development environment, the security principal must be assigned an Azure role that grants access to data. For information about assigning permissions via Azure RBAC, seeAssign an Azure role for access to blob data.

Set up your project

To work with the code examples in this article, add the following import directives:

import com.azure.storage.blob.*;import com.azure.storage.blob.models.*;import com.azure.storage.blob.sas.*;

Get an authenticated token credential

To get a token credential that your code can use to authorize requests to Blob Storage, create an instance of theDefaultAzureCredential class. For more information about using the DefaultAzureCredential class to authorize a managed identity to access Blob Storage, seeAzure Identity client library for Java.

The following code snippet shows how to get the authenticated token credential and use it to create a service client for Blob storage:

BlobServiceClient blobServiceClient = new BlobServiceClientBuilder()        .endpoint("https://<storage-account-name>.blob.core.windows.net/")        .credential(new DefaultAzureCredentialBuilder().build())        .buildClient();

To learn more about authorizing access to Blob Storage from your applications with the Java SDK, seeAzure authentication with Java and Azure Identity.

Get the user delegation key

Every SAS is signed with a key. To create a user delegation SAS, you must first request a user delegation key, which is then used to sign the SAS. The user delegation key is analogous to the account key used to sign a service SAS or an account SAS, except that it relies on your Microsoft Entra credentials. When a client requests a user delegation key using an OAuth 2.0 token, Blob Storage returns the user delegation key on behalf of the user.

Once you have the user delegation key, you can use that key to create any number of user delegation shared access signatures, over the lifetime of the key. The user delegation key is independent of the OAuth 2.0 token used to acquire it, so the token doesn't need to be renewed if the key is still valid. You can specify the length of time that the key remains valid, up to a maximum of seven days.

Use one of the following methods to request the user delegation key:

• getUserDelegationKey

The following code example shows how to request the user delegation key:

public UserDelegationKey requestUserDelegationKey(BlobServiceClient blobServiceClient) {    // Request a user delegation key that's valid for 1 day, as an example    UserDelegationKey userDelegationKey = blobServiceClient.getUserDelegationKey(        OffsetDateTime.now().minusMinutes(5),        OffsetDateTime.now().plusDays(1));    return userDelegationKey;}

Create a user delegation SAS

You can create a user delegation SAS for a container or blob, based on the needs of your app.

public String createUserDelegationSASContainer(BlobContainerClient containerClient, UserDelegationKey userDelegationKey) {    // Create a SAS token that's valid for 1 day, as an example    OffsetDateTime expiryTime = OffsetDateTime.now().plusDays(1);    // Assign read permissions to the SAS token    BlobContainerSasPermission sasPermission = new BlobContainerSasPermission()            .setReadPermission(true);    BlobServiceSasSignatureValues sasSignatureValues = new BlobServiceSasSignatureValues(expiryTime, sasPermission)            .setStartTime(OffsetDateTime.now().minusMinutes(5));    String sasToken = containerClient.generateUserDelegationSas(sasSignatureValues, userDelegationKey);    return sasToken;}

public String createUserDelegationSASBlob(BlobClient blobClient, UserDelegationKey userDelegationKey) {    // Create a SAS token that's valid for 1 day, as an example    OffsetDateTime expiryTime = OffsetDateTime.now().plusDays(1);    // Assign read permissions to the SAS token    BlobSasPermission sasPermission = new BlobSasPermission()            .setReadPermission(true);    BlobServiceSasSignatureValues sasSignatureValues = new BlobServiceSasSignatureValues(expiryTime, sasPermission)            .setStartTime(OffsetDateTime.now().minusMinutes(5));    String sasToken = blobClient.generateUserDelegationSas(sasSignatureValues, userDelegationKey);    return sasToken;}

Use a user delegation SAS to authorize a client object

You can use a user delegation SAS to authorize a client object to perform operations on a container or blob based on the permissions granted by the SAS.

// Create a SAS token for a containerBlobContainerClient containerClient = blobServiceClient.getBlobContainerClient("sample-container");String sasToken = createUserDelegationSASContainer(containerClient, userDelegationKey);// Create a new BlobContainerClient using the SAS tokenBlobContainerClient sasContainerClient = new BlobContainerClientBuilder()        .endpoint(containerClient.getBlobContainerUrl())        .sasToken(sasToken)        .buildClient();

// Create a SAS token for a blobBlobClient blobClient = blobServiceClient        .getBlobContainerClient("sample-container")        .getBlobClient("sample-blob.txt");String sasToken = createUserDelegationSASBlob(blobClient, userDelegationKey);// Create a new BlobClient using the SAS tokenBlobClient sasBlobClient = new BlobClientBuilder()        .endpoint(blobClient.getBlobUrl())        .sasToken(sasToken)        .buildClient();

Resources

To learn more about creating a user delegation SAS using the Azure Blob Storage client library for Java, see the following resources.

Code samples

• View code samples from this article (GitHub)

REST API operations

The Azure SDK for Java contains libraries that build on top of the Azure REST API, allowing you to interact with REST API operations through familiar Java paradigms. The client library method for getting a user delegation key uses the following REST API operation:

• Get User Delegation Key (REST API)

Client library resources

• Client library reference documentation
• Client library source code
• Package (Maven)

See also

• Grant limited access to Azure Storage resources using shared access signatures (SAS)
• Create a user delegation SAS

Related content

• This article is part of the Blob Storage developer guide for Java. To learn more, see the full list of developer guide articles atBuild your Java app.