Merge pull request #231360 from gahl-levy/mongo-vcore-updates

Updates for the release

Author: v-regandowner

articles/cosmos-db/mongodb/vcore/high-availability.md

@@ -17,11 +17,11 @@ High availability (HA) avoids database downtime by maintaining standby replicas
 
 ## How it works
 
-When HA is enabled, all primary nodes in a cluster are provisioned in one availability zone for better latency between nodes. The HA replica nodes, which don't receive requests, are provisioned in a different zone, if the region supports multiple zones and has available capacity.
+When HA is enabled, Azure Cosmos DB for MongoDB vCore runs one replica node for each primary node in the cluster. The primary and its replica use synchronous replication. The service detects failures on primary nodes and fails over to the replica nodes with zero data loss. The MongoDB connection string remains the same.
 
-Even without HA enabled, each node has its own locally redundant storage (LRS) with three synchronous replicas maintained by Azure Storage service. If there's a single replica failure, the Azure Storage service detects the failure, and transparently re-creates the relevant data. For LRS storage durability, see metrics on [this page](../../../storage/common/storage-redundancy.md#summary-of-redundancy-options).
+When HA is enabled, HA replica nodes are provisioned in a different availability zone from their primary nodes, if the region supports multiple zones and has available capacity. HA replicas don't receive requests from clients unless their primary node fails.
 
-When HA is enabled, Azure Cosmos DB for MongoDB vCore runs one replica node for each primary node in the cluster. The primary and its replica use synchronous replication. The service detects failures on primary nodes and fails over to the replica nodes with zero data loss. The MongoDB connection string remains the same.
+Even without HA enabled, each node has its own locally redundant storage (LRS) with three synchronous replicas maintained by Azure Storage service. If there's a single replica failure, the Azure Storage service detects the failure, and transparently re-creates the relevant data. For LRS storage durability, see metrics on [this page](../../../storage/common/storage-redundancy.md#summary-of-redundancy-options).
 
 ## Configure high availability
 

articles/cosmos-db/mongodb/vcore/how-to-restore-cluster.md

@@ -31,7 +31,7 @@ Azure Cosmos DB for MongoDB vCore provides automatic backups that enable point-i
 
 ## Backups
 
-Backups are **performed automatically** in the background. Backups are also retained for 35 days. All backups are encrypted using AES 256-bit encryption.
+Backups are **performed automatically** in the background. Backups are retained for 35 days for active clusters and 7 days for deleted clusters. All backups are encrypted using AES 256-bit encryption.
 
 > [!NOTE]
 > Backup files can't be exported. They may only be used for restore operations in Azure Cosmos DB for MongoDB vCore.

articles/cosmos-db/mongodb/vcore/introduction.md

@@ -13,21 +13,27 @@ ms.date: 03/07/2023
 
 # What is Azure Cosmos DB for MongoDB vCore?
 
-Azure Cosmos DB for MongoDB vCore provides developers with a fully managed MongoDB-compatible database service for building modern applications with a familiar architecture. With Cosmos DB for MongoDB vCore, developers can enjoy the benefits of native Azure integrations and the vCore architecture, designed to offer seamless lift and shift and unbeatable performance.
+Azure Cosmos DB for MongoDB vCore provides developers with a fully managed MongoDB-compatible database service for building modern applications with a familiar architecture. With Cosmos DB for MongoDB vCore, developers can enjoy the benefits of native Azure integrations, low total cost of ownership (TCO), and the familiar vCore architecture when migrating existing applications or building new ones.
 
-## Effortless management with the Azure platform
+## Effortless integration with the Azure platform
 
 Azure Cosmos DB for MongoDB vCore provides a comprehensive and integrated solution for resource management, making it easy for developers to seamlessly manage their resources using familiar Azure tools. The service features deep integration into various Azure products, such as Azure Monitor and Azure CLI. This deep integration ensures that developers have everything they need to work efficiently and effectively.
 
-In addition, developers can rest easy knowing that they have access to one unified support team for all their services, eliminating the need to juggle multiple support teams for different services.
+Developers can rest easy knowing that they have access to one unified support team for all their services, eliminating the need to juggle multiple support teams for different services.
 
-## A solution that simply works
+## Low total cost of ownership (TCO)
 
-Azure Cosmos DB for MongoDB vCore is organized into easy to understand cluster tiers based on vCPU counts and RAM with attached storage, making it easy to lift and shift your existing workloads. With a simple lift and shift, users can effortlessly transition to the platform, and its architecture and features match expectations.
+Azure Cosmos DB for MongoDB's scalable architecture is designed to deliver the best performance and cost efficiency for your workloads. Visit the [pricing page](https://azure.microsoft.com/pricing/details/cosmos-db/) to learn more about pricing for each cluster tier or price out a cluster in the Azure portal. With optional high availability (HA), there's no need to pay for resources you don't need for workloads such as development and testing. With HA disabled, we pass the **50% savings** on to you. The image below is an example of the pricing for a cluster with HA enabled and disabled.
+
+:::image type="content" source="media/introduction/cluster-tiers.png" alt-text="Screenshot of several cluster tier options.":::
+
+*East US region
+
+Azure Cosmos DB for MongoDB vCore is organized into easy to understand cluster tiers based on vCPUs, RAM, and attached storage, making it easy to lift and shift your existing workloads or build new applications.
 
 ## Flexibility for developers
 
-Cosmos DB for MongoDB vCore is built with flexibility for developers at the center. The service offers no shard key required until the database surpasses TBs and supports automatically sharding existing databases with no downtime. Developers can also easily scale their clusters up or down, vertically and horizontally, to meet their needs.
+Cosmos DB for MongoDB vCore is built with flexibility for developers in mind. The service offers high capacity vertical and horizontal scaling with no shard key required until the database surpasses TBs. The service also supports automatically sharding existing databases with no downtime. Developers can easily scale their clusters up or down, vertically and horizontally, all with no downtime, to meet their needs.
 
 ## Next steps
 

articles/cosmos-db/mongodb/vcore/media/introduction/cluster-tiers.png

@@ -52,7 +52,7 @@ Create a MongoDB cluster by using Azure Cosmos DB for MongoDB vCore.
     | Setting | Value |
     | --- | --- |
     | **Node count** | Single node |
-    | **Cluster tier** | M40 Tier, 4 vCores, 16-GiB RAM |
+    | **Cluster tier** | M30 Tier, 2 vCores, 8-GiB RAM |
     | **Storage per node** | 128 GiB |
 
 1. Leave the **High availability** option unselected. In the high availability (HA) acknowledgment section, select **I understand**. Finally, select **Save** to persist your changes to the cluster tier.