To insert multiple entities into Azure Table Storage as a single atomic operation, you need to use a batch process.

1. TableBatchOperation (Boxes 1 & 2): This class is designed specifically to create a collection of individual operations (like inserts, updates, or deletes) that will be executed together. You first declare a variable of this type and then create a new instance of it. All entities within a single batch operation must share the same partition key.
2. ExecuteBatch (Box 3): After populating the TableBatchOperation object with the desired operations, you call the ExecuteBatch method of the CloudTable class. This submits the entire batch to the Table Storage service. This approach significantly improves performance by reducing the number of requests sent to the service and ensures that all operations in the batch succeed or fail as a single unit (atomicity).

Microsoft. (n.d.). TableBatchOperation Class. Microsoft Azure Cosmos DB Table API for .NET Documentation.

Reference Point: The official API documentation defines the class as "Represents a batch operation on a table."

Microsoft. (2023, April 19). Get started with Azure Table storage and the Azure Cosmos DB Table API using the .NET SDK. Microsoft Learn.

Reference Point: The section titled "Batch transactions" provides a complete code example explicitly showing the creation of a TableBatchOperation instance and its submission via the CloudTable.ExecuteBatchAsync method.

Abadi, D. J. (2012). Lecture 17: Azure. CS 436/536: Distributed Systems, Yale University.

Reference Point: In discussions of Windows Azure Table Storage, the lecture notes describe Entity Group Transactions, which allow for atomic batch updates on entities within the same partition, directly corresponding to the function of TableBatchOperation.

Calder, B., et al. (2011). Windows Azure Storage: A Highly Available Cloud Storage Service with Strong Consistency. Proceedings of the 23rd ACM Symposium on Operating Systems Principles (SOSP '11). Association for Computing Machinery, New York, NY, USA, 143–157.

Reference Point: Section 3.1, "Table Storage Model," discusses Entity Group Transactions, explaining that "updates to entities in the same partition can be batched together in an atomic transaction," which is the underlying mechanism implemented by the ExecuteBatch call. DOI: https://doi.org/10.1145/2043556.2043571