Docs / Development / Azure Blob Storage blob provider

Azure Blob Storage blob provider

By default sensenet stores binaries (files) in its main database. If you want to store binaries in an external Blob provider instead of the main Content Repository database, we let you store binaries in Azure Blob Storage so that operators have more flexibility when installing and maintaining sensenet.

Azure Blob Storage is a great choice for Enterprise solutions as a binary storage. It is reliable and easy to adapt to.

Installation and maintenance

We tested this component with the Microsoft.Azure.Storage.Blob v9.4.2 client library. You can learn more of Azure Blob Storage at the Azure Blob Storage home page. You should follow the instructions below to install and maintain this enterprise feature.

Multiple blob providers: you cannot write to multiple blob providers at the same time, but you can change to another blob provider at any time: as long as all the necessary blob provider libraries are present in the application folder, old binaries written into a previous blob provider will still be accessible. This makes it possible to migrate to a new blob provider gradually, without a long app downtime.

Azure Blob Storage provider installation

To get started install the following NuGet package:



In order to use Azure for blob storage you have to configure the new Azure blob provider.

Connection string

Azure blob provider needs a connection string that points to the appropriate Azure storage. The place of this connection string is up to you, the following is only a best practice:

   <add name="SenseNet.AzureBlobStorage" connectionString="DefaultEndpointsProtocol=https;AccountName=[azure account name];AccountKey=[azure account key];" />

Configure the provider

We have to tell the system to use the Azure blob provider as the appointed external blob storage. To do that add the following code to your application global class:

protected override void BuildRepository(IRepositoryBuilder repositoryBuilder)


Please note that the chunk size for this provider has to be the same value as the system-wide binary chunk size, otherwise writing operations will fail.


If you intend to implement a backup policy, take a look at the following article to see the different options for that.


Currently there is no migration tool that moves existing binaries from the main Content Repository database (or from another blob provider) to Azure Blob Storage. However after you install this provider, the system will save new files to it and old files will also be moved as you save them.

Is something missing? See something that needs fixing? Propose a change here.