When you list the containers in an Azure Storage account from your code, you can specify a number of options to manage how results are returned from Azure Storage. This article shows how to list containers using theAzure Storage client library for .NET.

Prerequisites

• Azure subscription -create one for free
• Azure storage account -create a storage account
• Latest.NET SDK for your operating system. Be sure to get the SDK and not the runtime.

Set up your environment

If you don't have an existing project, this section shows you how to set up a project to work with the Azure Blob Storage client library for .NET. The steps include package installation, addingusing directives, and creating an authorized client object. For details, seeGet started with Azure Blob Storage and .NET.

Install packages

From your project directory, install packages for the Azure Blob Storage and Azure Identity client libraries using thedotnet add package command. The Azure.Identity package is needed for passwordless connections to Azure services.

dotnet add package Azure.Storage.Blobsdotnet add package Azure.Identity

Addusing directives

Add theseusing directives to the top of your code file:

using Azure.Identity;using Azure.Storage.Blobs;using Azure.Storage.Blobs.Models;using Azure.Storage.Blobs.Specialized;

Some code examples in this article might require additionalusing directives.

Create a client object

To connect an app to Blob Storage, create an instance ofBlobServiceClient. The following example shows how to create a client object usingDefaultAzureCredential for authorization:

public BlobServiceClient GetBlobServiceClient(string accountName){    BlobServiceClient client = new(        new Uri($"https://{accountName}.blob.core.windows.net"),        new DefaultAzureCredential());    return client;}

You can register a service client fordependency injection in a .NET app.

You can also create client objects for specificcontainers orblobs. To learn more about creating and managing client objects, seeCreate and manage client objects that interact with data resources.

Authorization

The authorization mechanism must have the necessary permissions to list blob containers. For authorization with Microsoft Entra ID (recommended), you need Azure RBAC built-in roleStorage Blob Data Contributor or higher. To learn more, see the authorization guidance forList Containers (REST API).

About container listing options

When listing containers from your code, you can specify options to manage how results are returned from Azure Storage. You can specify the number of results to return in each set of results, and then retrieve the subsequent sets. You can also filter the results by a prefix, and return container metadata with the results. These options are described in the following sections.

To list containers in your storage account, call one of the following methods:

• GetBlobContainers
• GetBlobContainersAsync

These methods return a list ofBlobContainerItem objects. Containers are ordered lexicographically by name.

Manage how many results are returned

By default, a listing operation returns up to 5000 results at a time, but you can specify the number of results that you want each listing operation to return. The examples presented in this article show you how to return results in pages. To learn more about pagination concepts, seePagination with the Azure SDK for .NET.

Filter results with a prefix

To filter the list of containers, specify a string for theprefix parameter. The prefix string can include one or more characters. Azure Storage then returns only the containers whose names start with that prefix.

Include container metadata

To include container metadata with the results, specify theMetadata value for theBlobContainerTraits enum. Azure Storage includes metadata with each container returned, so you don't need to fetch the container metadata separately.

Include deleted containers

To include soft-deleted containers with the results, specify theDeleted value for theBlobContainerStates enum.

Code example: List containers

The following example asynchronously lists the containers in a storage account that begin with a specified prefix. The example lists containers that begin with the specified prefix and returns the specified number of results per call to the listing operation. It then uses the continuation token to get the next segment of results. The example also returns container metadata with the results.

async static Task ListContainers(BlobServiceClient blobServiceClient,                                 string prefix,                                 int? segmentSize){    try    {        // Call the listing operation and enumerate the result segment.        var resultSegment =             blobServiceClient.GetBlobContainersAsync(BlobContainerTraits.Metadata, prefix, default)            .AsPages(default, segmentSize);        await foreach (Azure.Page<BlobContainerItem> containerPage in resultSegment)        {            foreach (BlobContainerItem containerItem in containerPage.Values)            {                Console.WriteLine("Container name: {0}", containerItem.Name);            }            Console.WriteLine();        }    }    catch (RequestFailedException e)    {        Console.WriteLine(e.Message);        Console.ReadLine();        throw;    }}

Resources

To learn more about listing containers using the Azure Blob Storage client library for .NET, see the following resources.

REST API operations

The Azure SDK for .NET contains libraries that build on top of the Azure REST API, allowing you to interact with REST API operations through familiar .NET paradigms. The client library methods for listing containers use the following REST API operation:

• List Containers (REST API)

Client library resources

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

See also

• Enumerating Blob Resources

Related content

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