I am trying to insert multiple rows into the Azure table service. As far as this article goes, I have understood the partition key to be able to store duplicates. However, w
The Partition Key + the Row Key together act as a primary key for that entry into the table, this combination must be unique. You can have a virtually unlimited number of rowkeys within a single partition, as long as you don't violate the PK+RK=unique constraint.
Keep in mind however, that throughput scale targets for Azure table storage center around the partition. So the strategy you leverage to identify your partition key should be something that meets your needs for both scale and accessibility.