Azure Tables: best practices for choosing partition/row keys

Question

What would be best practices for choosing partition/row keys for entities in Azure Tables? The common advice is to magically balance between partition size and the number of partitions. But no one seems to have a good definition of how it can be accomplished in 3 easy steps. Is there a general approach for choosing keys so that everything then just works?

Answer 1

This article covers your concern: https://docs.microsoft.com/en-us/azure/cosmos-db/table-storage-design-guide