When executing a batch, if one of the operation of TableBatchOperation fails:
- Every operations in the batch are canceled
- Every other operations that are valid are processed
- The first valid operations in the queue are processed until one operation fails, and following ones are not processed
Answer is 1 – Even if one operation fails in the batch, the entire operation fails (or in other words rolls back). This is similar to performing transactions in a relational database. What’s interesting is that you get an index of the failed entity in the response when this happens. Check this thread for more details: Azure CloudTable.ExecuteBatch(TableBatchOperation) throws a storageexception. How can I find which operation(s) caused the exception?