Skip to content

Commit 426bf01

Browse files
authored
Merge pull request #132385 from aliuy/patch-1
Update account-overview.md
2 parents 7b28e63 + 99ca6e6 commit 426bf01

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cosmos-db/account-overview.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ To securely manage access to all the data within your Azure Cosmos account, you
2323

2424
Azure Cosmos container is the fundamental unit of scalability. You can virtually have an unlimited provisioned throughput (RU/s) and storage on a container. Azure Cosmos DB transparently partitions your container using the logical partition key that you specify in order to elastically scale your provisioned throughput and storage. For more information, see [working with Azure Cosmos containers and items](databases-containers-items.md).
2525

26-
Currently, you can create a maximum of 100 Azure Cosmos accounts under an Azure subscription. A single Azure Cosmos account can virtually manage unlimited amount of data and provisioned throughput. To manage your data and provisioned throughput, you can create one or more Azure Cosmos databases under your account and within that database, you can create one or more containers. The following image shows the hierarchy of elements in an Azure Cosmos account:
26+
Currently, you can create a maximum of 50 Azure Cosmos accounts under an Azure subscription (this is a soft limit that can be increased via support request). A single Azure Cosmos account can virtually manage unlimited amount of data and provisioned throughput. To manage your data and provisioned throughput, you can create one or more Azure Cosmos databases under your account and within that database, you can create one or more containers. The following image shows the hierarchy of elements in an Azure Cosmos account:
2727

2828
:::image type="content" source="./media/account-overview/hierarchy.png" alt-text="Hierarchy of an Azure Cosmos account" border="false":::
2929

0 commit comments

Comments
 (0)