Thank you for posting your question on Microsoft Q&A forum.
Azure Table Storage supports optimistic concurrency and conditional inserts to handle multiple data input at the same time. But keep in mind the below when picking partition and row keys for data being added.
Entities per second (storage account)
The scalability limit for accessing tables is up to 20,000 entities (1 KB each) per second for an account. In general, each entity that is inserted, updated, deleted, or scanned counts toward this target. So a batch insert that contains 100 entities would count as 100 entities. A query that scans 1000 entities and returns 5 would count as 1000 entities.
Entities per second (partition)
Within a single partition, the scalability target for accessing tables is 2,000 entities (1 KB each) per second, using the same counting as described in the previous section.
Performance and scalability checklist for Table storage
Azure Tables output bindings for Azure Functions
Regards,
Oury