Merge pull request #254261 from richagaur/richagaur/serverless-doc-updates

updated limits and added DR guidance

Author: prmerger-automator[bot]

articles/cosmos-db/concepts-limits.md

@@ -88,8 +88,7 @@ Depending on the current RU/s provisioned and resource settings, each resource c
 | --- | --- |
 | Maximum RU/s per container | 20,000* |
 | Maximum storage across all items per (logical) partition | 20 GB |
-| Maximum storage per container (API for NoSQL, MongoDB, Table, and Gremlin)| 1 TB  |
-| Maximum storage per container (API for Cassandra)| 1 TB  |
+| Maximum storage per container | 1 TB  |
 
 *Maximum RU/sec availability is dependent on data stored in the container. See, [Serverless Performance](serverless-performance.md)
 
@@ -152,11 +151,9 @@ Here's a list of limits per account.
 
 | Resource | Limit |
 | --- | --- |
-| Maximum number of databases and containers per account  | 100¹ |
+| Maximum number of databases and containers per account  | 500 |
 | Maximum number of regions | 1 (Any Azure region) |
 
-¹ You can increase any of these per-account limits by creating an [Azure Support request](create-support-request-quota-increase.md).
-
 ## Per-container limits
 
 Depending on which API you use, an Azure Cosmos DB container can represent either a collection, a table, or graph. Containers support configurations for [unique key constraints](unique-keys.md), [stored procedures, triggers, and UDFs](stored-procedures-triggers-udfs.md), and [indexing policy](how-to-manage-indexing-policy.md). The following table lists the limits specific to configurations within a container.

articles/cosmos-db/serverless.md

@@ -64,6 +64,11 @@ You can monitor consumption by viewing a chart in your Azure Cosmos DB account i
 
 You can use the same [chart in Azure Monitor](monitor-request-unit-usage.md). When you use Azure Monitor, you can set up [alerts](../azure-monitor/alerts/alerts-metric-overview.md) so that you're notified when your RU consumption passes a threshold that you set.
 
+## High availability
+
+Azure Cosmos DB serverless extends high availability support with availability zones in [designated regions](../../articles/reliability/availability-zones-service-support.md#azure-regions-with-availability-zone-support). The associated Service Level Agreements (SLAs) are aligned with the [Single-region writes with availability zone](../../articles/cosmos-db/high-availability.md#slas) configuration, ensuring reliability for your deployments.
+
+
 ## Next steps
 
 To get started with using the serverless pricing option in Azure Cosmos DB, review the following articles: