index.md

title	summary	reviewed	component	related	redirects
Azure Table Persistence	Using Azure Tables as persistence	2024-02-01	ASP	persistence/upgrades/asp-saga-deduplication persistence/upgrades/asp-saga-pruning samples/azure/azure-table	nservicebus/using-azure-storage-persistence-in-nservicebus nservicebus/azure/azure-storage-persistence nservicebus/azure-storage-persistence persistence/azure-table

Certain features of NServiceBus require persistence to permanently store data. Among them are subscription storage, sagas, and outbox. Various storage options are available including Azure Table and Azure Cosmos DB Table API.

Azure Table Persistence stores NServiceBus data in Azure Table storage or Azure Cosmos DB using the Table API.

Persistence at a glance

For a description of each feature, see the persistence at a glance legend.

Feature
Supported storage types	Sagas, Outbox, Subscriptions
Transactions	Using TransactionalBatch, with caveats
Concurrency control	Optimistic concurrency
Scripted deployment	Not supported
Installers	Supported. Subscription, the default table or saga tables derived by convention when no default table is set are created at runtime, when enabled.

Enable Azure Table Persistence

partial: config

partial: ratelimiting

partial: transaction

Saga concurrency

partial: saga-concurrency

Supported saga properties' types

partial: saga-property-types

Saga Correlation property restrictions

Saga correlation property values are subject to the underlying Azure Storage table PartitionKey and RowKey restrictions:

• Up to 1KB in size
• Cannot contain invalid characters