In the Cosmos DB docs, I see that allocating a Fixed (10GB) Collection means that there will only ever be a single partition allocated to hold documents within the Collectio
When we create partitioned collection we are dealing with "logical partitions" not physical ones, the physical partitions is managed by the Cosmos service.
For "Should I partition my collection?" question, in this blog, you can find:
@Rob : When you create a "fixed" 10 GB partition, there is only one physical partition allocated, whether you provide a partition key or not. Note that providing a partition key in this case is optional.
If you have provided a partition key while creating this "fixed" collection, there is a migration path for this collection to a partitioned collection and you would not have to change your application code.
If you don't provide the partition key, we don't support migration of this collection to a partitioned collection and hence you will be stuck with 10GB and you would have to manually migrate your data using our data Migration Tool to a new partitioned collection, if you ever cross the 10GB limit. Also, this would require you to change your application code(to pass in the partition key in various APIs) once you start targeting a partitioned collection.
In summary, you are well off providing a partition key while creating this "fixed" collection, even though all partition key values will be mapped to the single partition.
Hope that answers you query. Let me know if you have any more comments.