Azure Table transactions review

Author: mauroservienti

persistence/azure-table/transactions.md

@@ -4,14 +4,14 @@ component: ASP
 versions: 'ASTP:[3,]'
 related:
 - nservicebus/outbox
-reviewed: 2024-02-09
+reviewed: 2025-11-24
 ---
 
 partial: intro
 
 A custom [behavior](/nservicebus/pipeline/manipulate-with-behaviors.md) must be introduced to identify and insert the `TableEntityPartitionKey` value into the pipeline context for use by storage operations that occur during the processing of a given message.
 
-> [!NOTE]
+> [!IMPORTANT]
 > Do not use a [message mutator](/nservicebus/pipeline/message-mutators.md) to identify the partition key. Message mutators do not offer the necessary control or timing to reliably interact with this persistence.
 
 The custom behavior can be introduced in one of the two stages:

persistence/azure-table/transactions_sharing_astp_[3,5).partial.md

@@ -1,6 +1,6 @@
 ## Sharing the transaction
 
-Once a behavior is introduced to identify the partition key for a given message, it is possible to share a Azure Table [TableBatchOperation](https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.cosmos.table.tablebatchoperation?view=azure-dotnet) between both the Saga persistence and business data. The shared `TableBatchOperation` can then be used to persist document updates for both concerns atomically.
+Once a behavior is introduced to identify the partition key for a given message, it is possible to share an Azure Table [TableBatchOperation](https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.cosmos.table.tablebatchoperation?view=azure-dotnet) between both the Saga persistence and business data. The shared `TableBatchOperation` can then be used to persist document updates for both concerns atomically.
 
 ### Within a handler method using `IMessageHandlerContext`
 
@@ -18,6 +18,6 @@ For custom types that require access to the shared `TableBatchOperation`:
 
 snippet: TransactionalBatchRegisteredWithDependencyInjectionResolvedInCustomType
 
-And alternatively to using the the extension method `IMessageHandlerContext.SynchronizedStorageSession.AzureTablePersistenceSession()`:
+And alternatively to using the extension method `IMessageHandlerContext.SynchronizedStorageSession.AzureTablePersistenceSession()`:
 
 snippet: TransactionalBatchRegisteredWithDependencyInjectionResolvedInHandler

persistence/azure-table/transactions_sharing_astp_[5,).partial.md

@@ -1,10 +1,10 @@
 ## Sharing the transaction
 
-Once a behavior is introduced to identify the partition key for a given message, it is possible to share a batch, represented in Azure Table by `List<TableTransactionAction>` between both the Saga persistence and business data. This list can then be used to persist document updates for both concerns atomically.
+Once a behavior is introduced to identify the partition key for a given message, it is possible to share a batch, represented in Azure Table by `List<TableTransactionAction>` between both the Saga persistence and business data. This batch can then be used to persist document updates for both concerns atomically.
 
 ### Within a handler method using `IMessageHandlerContext`
 
-To use the shared `List<TableTransactionAction>` in a message handler:
+To use the shared `List<TableTransactionAction>` batch in a message handler:
 
 snippet: HandlerSharedTransaction
 
@@ -14,10 +14,10 @@ The `TestableAzureTableStorageSession` class in the `NServiceBus.Testing` namesp
 
 ### With dependency injection
 
-For custom types that require access to the shared `List<TableTransactionAction>`:
+For custom types that require access to the shared `List<TableTransactionAction>` batch:
 
 snippet: TransactionalBatchRegisteredWithDependencyInjectionResolvedInCustomType
 
-And alternatively to using the the extension method `IMessageHandlerContext.SynchronizedStorageSession.AzureTablePersistenceSession()`:
+And alternatively to using the extension method `IMessageHandlerContext.SynchronizedStorageSession.AzureTablePersistenceSession()`:
 
 snippet: TransactionalBatchRegisteredWithDependencyInjectionResolvedInHandler