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:
- Single-partition collections: have lower price options and the
ability to execute queries and perform transactions across all
collection data. They have the scalability and storage limits of a
single partition (10GB and 10,000 RU/s). You do not have to specify a
partition key for these collections. For scenarios that do not need
large volumes of storage or throughput, single partition collections
are a good fit.
- Partitioned collections: can span multiple partitions and support
very large amounts of storage and throughput. You must specify a
partition key for these collection.