Playing around with Azure Table Storage

I’ve been using Azure table storage lately at work and I thought that I’d share my experiences with you, both good and bad. What I like about it is its ease of use and set up, requiring you to do minimal work to get it up and working in your solution. It does its job and it does it well, although it loses some of its charm when it comes down to performance and its lack of basic database operations such as “like” or “contains”. If you want those operations, you’d need to implement them yourself using what’s available.

Setting up Azure table storage is quite straightforward. I highly recommend using Azure Key Vault to store secret keys needed to connect to and use the table storage. Keys such as storageAccountKey. Let’s assume that we have a TableStorageService class that connects to and uses table storage, make sure that you’ve installed WindowsAzure.Storage, then the set up would look like the following:

private const string tableName = "Customers";
private static CloudTable _cloudTable;
public TableStorageService(KeyVaultSecretProvider keyVaultSecretProvider, string storageAccountName, string storageAccountKeyName)
    var storageAccountKey = keyVaultSecretProvider.GetSecret(storageAccountKeyName);
    var connectionString = $"DefaultEndpointsProtocol=https;AccountName={storageAccountName};AccountKey={storageAccountKey};";
    var cloudStorageAccount = CloudStorageAccount.Parse(connectionString);
    var cloudTableClient = cloudStorageAccount.CreateCloudTableClient();
    _cloudTable = cloudTableClient.GetTableReference(tableName);

Here is how the IoC installer - using Castle Windsor - looks like, that wires up the dependencies for TableStorageService:

public class Installer : IWindsorInstaller
    public void Install(IWindsorContainer container, IConfigurationStore store)
        container.Install(new AzureClientInstaller(new AzureClientOptions { SpnIdentifier = "Api", UseCacheForSecrects = true, SpnCertificateLocation = StoreLocation.LocalMachine }));

            .DependsOn(Dependency.OnValue("storageAccountName", ConfigurationManager.AppSettings["Storage.AccountName"]))
            .DependsOn(Dependency.OnValue("storageAccountKeyName", ConfigurationManager.AppSettings["Storage.AccountKeyName"])));

In TableStorageService we’re defining a table called Customers. The next step is to create this table if it does not exist:


And that’s pretty much it. Now let’s look at some of the available database operations that we can do.

Insert, Get, Delete

In order to insert a row into our table, we’d need to insert a TableEntity object. Consider the following:

public class CustomerEntity : TableEntity
    public CustomerEntity() { }

    public CustomerEntity(string lastName, string firstName)
        PartitionKey = lastName;
        RowKey = firstName;

We can insert this object as such:

var insertOperation = TableOperation.Insert(new CustomerEntity("Snow", "Jon"));
await _cloudTable.ExecuteAsync(insertOperation);

We can also do a batch insert of entities, this is really efficient if you want to store 100 or more entities at a time. Here is a simple example storing 100 entities:

var tableBatchOperation = new TableBatchOperation();
for(var i = 0; i < 100; i++){
    tableBatchOperation.Insert(new CustomerEntity("Snow", $"Jon {i}"));
    if(i == 99) {
        await _cloudTable.ExecuteBatchAsync(tableBatchOperation);

To get rows from our table, we can filter using the ParitionKey or RowKey:

var query = new TableQuery<CustomerEntity>().Where(TableQuery.GenerateFilterCondition("RowKey", QueryComparisons.Equal, "Jon"));

As mentioned earlier, table storage does not have a “like” or “contains” operation. If you really need it, you could implement it yourself, but that’s really not recommended since anything custom made would very likely take its toll on performance.

Deleting an entity is straightforward; first retrieve the entity then delete it:

var retrieveOperation = TableOperation.Retrieve<CustomerEntity>("Snow", "Jon");
var retrievedResult = await _cloudTable.ExecuteAsync(retrieveOperation);
var deleteEntity = (CustomerEntity)retrievedResult.Result;
var deleteOperation = TableOperation.Delete(deleteEntity);
await _cloudTable.ExecuteAsync(deleteOperation);

Those are the basic operations which help you get up and running with Azure table storage.

Blob containers

In addition, with table storage you can create blob containers where you can store blobs with JSON and/or other file formats. This is very handy. Here is an example of a Job class showing how to create a blob container and connect to it (note that we showed how to build a connection string earlier in this article):

private const string CustomersContainerName = "customers";
private static CloudBlobContainer _cloudBlobContainer;
public Job(string connectionString)
    var cloudStorageAccount = CloudStorageAccount.Parse(connectionString);
    var cloudBlobClient = cloudStorageAccount.CreateCloudBlobClient();
    _cloudBlobContainer = cloudBlobClient.GetContainerReference(CustomersContainerName);
    if (!_cloudBlobContainer.Exists()) _cloudBlobContainer.Create();            

Here is how to upload a JSON blob to the blob container:

var cloudBlockBlob = _cloudBlobContainer.GetBlockBlobReference(blobName);
cloudBlockBlob.Properties.ContentType = "application/json";
using (var ms = new MemoryStream())
    var j = JsonConvert.SerializeObject(json);
    var writer = new StreamWriter(ms);
    ms.Position = 0;

Here is how to download a blob from the blob container (make sure that blobName includes the file format):

var cloudBlockBlob = _cloudBlobContainer.GetBlockBlobReference(blobName);
await cloudBlockBlob.DownloadToFileAsync("C:\Documents\customer.json", FileMode.Create);

And finally, here is how to delete a blob from the blob container; first retrieve the blob then delete it (again, make sure that blobName includes the file format):

var cloudBlockBlob = _cloudBlobContainer.GetBlockBlobReference(blobName);
await cloudBlockBlob.DeleteIfExistsAsync();


Queues are used for asynchronous messaging between application components in the cloud, a queue is a service for storing messages that can be accessed from anywhere. A single queue message is up to 64 KB in size and a queue can contain millions of messages. Here is another example of a Job class, this time showing how to create a queue and connect to it (again, note that we showed how to build a connection string earlier in this article):

private const string queueName = "queue";
private static CloudQueue _cloudQueue;
public Job(string connectionString)
    var cloudStorageAccount = CloudStorageAccount.Parse(connectionString);
    var cloudQueueClient = cloudStorageAccount.CreateCloudQueueClient();
    _cloudQueue = cloudQueueClient.GetQueueReference(queueName);

Here is how to insert a message into the queue:

var cloudQueueMessage = new CloudQueueMessage("Hello, Jon Snow!");
await _cloudQueue.AddMessageAsync(cloudQueueMessage);

Here is how to peek at the message in the front of the queue (without removing it):

var cloudQueueMessage = await _cloudQueue.PeekMessageAsync();

Here is how to update the content of a message in the front of the queue (then make it invisible for 60 seconds so that others can work with the original content during that time):

var cloudQueueMessage = await _cloudQueue.GetMessageAsync();
cloudQueueMessage.SetMessageContent("New content.");
_cloudQueue.UpdateMessage(cloudQueueMessage, TimeSpan.FromSeconds(60.0), MessageUpdateFields.Content | MessageUpdateFields.Visibility);

Here is how to delete a message from the front of the queue:

var cloudQueueMessage = await _cloudQueue.GetMessageAsync();
await _cloudQueue.DeleteMessageAsync(cloudQueueMessage);

And finally, here is how to get the total number of messages in the queue:

var messageCount = _cloudQueue.ApproximateMessageCount;

I recommend downloading Azure Storage Explorer which is a tool to help you manage your tables. For more information on table storage, you can always check out the official Microsoft documentation.

Hope you enjoyed this!