Azure WebJobs Storage Blobs and Queues client library for .NET - version 5.3.0

This extension provides functionality for accessing Azure Storage Blobs and Queues in Azure Functions. This package is a metapackage created for backwards compatibity. Using Azure.WebJobs.Extensions.Storage.Blobs and Azure.WebJobs.Extensions.Storage.Queues directly is recommended.

Getting started

Install the package

Install the Storage Blobs and Queues extension with NuGet:

dotnet add package Microsoft.Azure.WebJobs.Extensions.Storage


You need an Azure subscription and a Storage Account to use this package.

To create a new Storage Account, you can use the Azure Portal, Azure PowerShell, or the Azure CLI. Here's an example using the Azure CLI:

az storage account create --name <your-resource-name> --resource-group <your-resource-group-name> --location westus --sku Standard_LRS

Authenticate the client

In order for the extension to access Blobs, you will need the connection string which can be found in the Azure Portal or by using the Azure CLI snippet below.

az storage account show-connection-string -g <your-resource-group-name> -n <your-resource-name>

The connection string can be supplied through AzureWebJobsStorage app setting.

Key concepts

Using Queues

Please refer to Azure WebJobs Storage Queues.

Using Blobs

Please refer to Azure WebJobs Storage Blobs.


Please refer to Azure WebJobs Storage Queues and Azure WebJobs Storage Blobs.


Please refer to Monitor Azure Functions for troubleshooting guidance.

Next steps

Read the introduction to Azure Function or creating an Azure Function guide.


See the Storage for details on building, testing, and contributing to this library.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.