Merge pull request #234963 from Rodrigossz/main

Azure Storage Info and link

Author: prmerger-automator[bot]

articles/cosmos-db/analytical-store-introduction.md

@@ -448,7 +448,7 @@ the MongoDB `_id` field is fundamental to every collection in MongoDB and origin
 
 The example below works on Spark 2.x and 3.x versions:
 
-```Python
+```Scala
 val df = spark.read.format("cosmos.olap").option("spark.synapse.linkedService", "xxxx").option("spark.cosmos.container", "xxxx").load()
 
 val convertObjectId = udf((bytes: Array[Byte]) => {
@@ -552,8 +552,10 @@ After the analytical store is enabled, based on the data retention needs of the
 
 Analytical store relies on Azure Storage and offers the following protection against physical failure:
 
- * By default, Azure Cosmos DB database accounts allocate analytical store in Locally Redundant Storage (LRS) accounts.
- * If any geo-region of the database account is configured for zone-redundancy, it is allocated in Zone-redundant Storage (ZRS) accounts. Customers need to enable Availability Zones on a region of their Azure Cosmos DB database account to have analytical data of that region stored in ZRS.
+ * By default, Azure Cosmos DB database accounts allocate analytical store in Locally Redundant Storage (LRS) accounts. LRS provides at least 99.999999999% (11 nines) durability of objects over a given year.
+ * If any geo-region of the database account is configured for zone-redundancy, it is allocated in Zone-redundant Storage (ZRS) accounts. Customers need to enable Availability Zones on a region of their Azure Cosmos DB database account to have analytical data of that region stored in ZRS. ZRS offers durability for storage resources of at least 99.9999999999% (12 9's) over a given year.
+
+For more information about Azure Storage durability, click [here](https://learn.microsoft.com/azure/storage/common/storage-redundancy).
 
 ## Backup
 

articles/cosmos-db/get-started-change-data-capture.md

@@ -7,15 +7,19 @@ ms.author: rosouz
 ms.reviewer: sidandrews
 ms.service: cosmos-db
 ms.topic: how-to
-ms.date: 03/23/2023
+ms.date: 04/18/2023
 ---
 
-# Get started with change data capture in the analytical store for Azure Cosmos DB
+# Get started with change data capture in the analytical store for Azure Cosmos DB (Preview)
 
 [!INCLUDE[NoSQL, MongoDB](includes/appliesto-nosql-mongodb.md)]
 
 Use Change data capture (CDC) in Azure Cosmos DB analytical store as a source to [Azure Data Factory](../data-factory/index.yml) or [Azure Synapse Analytics](../synapse-analytics/index.yml) to capture specific changes to your data.
 
+
+> [!NOTE]
+> Please note that the linked service interface for Azure Cosmos DB for MongoDB API is not available on Dataflow yet. However, you would be able to use your account’s document endpoint with the “Azure Cosmos DB for NoSQL” linked service interface as a work around until the Mongo linked service is supported. On a NoSQL linked service, choose “Enter Manually” to provide the Cosmos DB account info and use account’s document endpoint (eg: https://<accturi>.documents.azure.com:443/) instead of the MongoDB endpoint (eg: mongodb://<accturi>.mongo.cosmos.azure.com:10255/)  
+
 ## Prerequisites
 
 - An existing Azure Cosmos DB account.