I used to create a Cosmos database with shared throughput that has more than 30 containers. It looks like Microsoft added a limitation in February of this year so that the maximum number of containers in a shared database is 25. My account was given an exception to the rule so I can continue to create more than 25 containers, but I need to migrate my application & data to another Azure account. Thus, I can no longer do what I did before.
This frustrates me because the lowest throughput on an individual container in a non-shared database seems to be 400. Now, I have to pay for 400 * {# of containers} throughput instead of 100 * {# of containers}. All that buzz about paying for what you use in a cloud environment seems like a joke now.
I need to know if there is a way to create a container with 100 min throughput?
It is no longer possible to share your database throughput across more than 25 containers. This is the corresponding announcement.
This will allow for better throughput sharing across collections.
To get back to 100 RUs per container, you should just create an additional database with its own shared troughput. I would not recomment to max out each database with 25 containers each just to save costs. It would probably give you a bit more flexibility to only put 10 to 15 containers in one database.
Keep in mind that you will not be able to simply change a collection from shared throughput to dedicated throughput. This is a destructive operation and requires a data migration, e.g. via the import tool.