Merge pull request #252585 from seesharprun/cosmos-pr-fixes

Cosmos DB | Various GitHub issue fixes

Author: prmerger-automator[bot]

articles/cosmos-db/audit-control-plane-logs.md

@@ -46,6 +46,8 @@ Use the following steps to enable logging on control plane operations:
 
 1. Select **ControlPlaneRequests** for log type and select the **Send to Log Analytics** option.
 
+1. Optionally, send the diagnostic logs to Azure Storage, Azure Event Hubs, Azure Monitor, or a third party.
+
 You can also store the logs in a storage account or stream to an event hub. This article shows how to send logs to log analytics and then query them. After you enable, it takes a few minutes for the diagnostic logs to take effect. All the control plane operations performed after that point can be tracked. The following screenshot shows how to enable control plane logs:
 
 :::image type="content" source="./media/audit-control-plane-logs/enable-control-plane-requests-logs.png" alt-text="Enable control plane requests logging":::

articles/cosmos-db/consistency-levels.md

@@ -179,6 +179,9 @@ The exact RTT latency is a function of speed-of-light distance and the Azure net
 > [!NOTE]
 > The RU/s cost of reads for Local Minority reads are twice that of weaker consistency levels because reads are made from two replicas to provide consistency guarantees for Strong and Bounded Staleness.
 
+> [!NOTE]
+> The RU/s cost of reads for the strong and bounded staleness consistency levels consume approximately two times more RUs while performing read operations when compared to that of other relaxed consistency levels.
+
 ## <a id="rto"></a>Consistency levels and data durability
 
 Within a globally distributed database environment, there's a direct relationship between the consistency level and data durability in the presence of a region-wide outage. As you develop your business continuity plan, you need to understand the maximum period of recent data updates the application can tolerate losing when recovering after a disruptive event. The time period of updates that you might afford to lose is known as **recovery point objective** (**RPO**).

articles/cosmos-db/how-to-configure-private-endpoints.md

@@ -275,9 +275,46 @@ You can set up Private Link by creating a private endpoint in a virtual network
 
 Use the following code to create a Resource Manager template named *PrivateEndpoint_template.json*. This template creates a private endpoint for an existing Azure Cosmos DB vAPI for NoSQL account in an existing virtual network.
 
+### [Bicep](#tab/arm-bicep)
+
+```bicep
+@description('Location for all resources.')
+param location string = resourceGroup().location
+param privateEndpointName string
+param resourceId string
+param groupId string
+param subnetId string
+
+resource privateEndpoint 'Microsoft.Network/privateEndpoints@2019-04-01' = {
+  name: privateEndpointName
+  location: location
+  properties: {
+    subnet: {
+      id: subnetId
+    }
+    privateLinkServiceConnections: [
+      {
+        name: 'MyConnection'
+        properties: {
+          privateLinkServiceId: resourceId
+          groupIds: [
+            groupId
+          ]
+          requestMessage: ''
+        }
+      }
+    ]
+  }
+}
+
+output privateEndpointNetworkInterface string = privateEndpoint.properties.networkInterfaces[0].id
+```
+
+### [JSON](#tab/arm-json)
+
 ```json
 {
-    "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
+    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
     "contentVersion": "1.0.0.0",
     "parameters": {
         "location": {
@@ -332,13 +369,17 @@ Use the following code to create a Resource Manager template named *PrivateEndpo
 }
 ```
 
+---
+
 **Define the parameters file for the template**
 
 Create a parameters file for the template, and name it *PrivateEndpoint_parameters.json*. Add the following code to the parameters file:
 
+### [Bicep / JSON](#tab/arm-bicep+arm-json)
+
 ```json
 {
-    "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
+    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
     "contentVersion": "1.0.0.0",
     "parameters": {
         "privateEndpointName": {
@@ -357,6 +398,8 @@ Create a parameters file for the template, and name it *PrivateEndpoint_paramete
 }
 ```
 
+---
+
 **Deploy the template by using a PowerShell script**
 
 Create a PowerShell script by using the following code. Before you run the script, replace the subscription ID, resource group name, and other variable values with the details for your environment.

articles/cosmos-db/nosql/how-to-manage-consistency.md

@@ -80,17 +80,17 @@ documentClient = new DocumentClient(new Uri(endpoint), authKey, connectionPolicy
 // Override consistency at the request level via request options
 RequestOptions requestOptions = new RequestOptions { ConsistencyLevel = ConsistencyLevel.Eventual };
 
-var response = await client.CreateDocumentAsync(collectionUri, document, requestOptions);
+var response = await client.ReadDocumentAsync(collectionUri, document, requestOptions);
 ```
 
 # [.NET SDK V3](#tab/dotnetv3)
 
 ```csharp
 // Override consistency at the request level via request options
-ItemRequestOptions requestOptions = new ItemRequestOptions { ConsistencyLevel = ConsistencyLevel.Strong };
+ItemRequestOptions requestOptions = new ItemRequestOptions { ConsistencyLevel = ConsistencyLevel.Eventual };
 
 var response = await client.GetContainer(databaseName, containerName)
-    .CreateItemAsync(
+    .ReadItemAsync(
         item,
         new PartitionKey(itemPartitionKey),
         requestOptions);

articles/cosmos-db/nosql/how-to-manage-indexing-policy.md

@@ -227,10 +227,10 @@ It's optional to specify the order. If not specified, the order is ascending.
     "compositeIndexes":[  
         [  
             {  
-               "path":"/name",
+               "path":"/name"
             },
             {  
-               "path":"/age",
+               "path":"/age"
             }
         ]
     ]

articles/cosmos-db/nosql/how-to-use-stored-procedures-triggers-udfs.md

@@ -232,7 +232,7 @@ new_item =   {
       "description":"Pick up strawberries",
       "isComplete":False
    }
-result = container.scripts.execute_stored_procedure(sproc=created_sproc,params=[[new_item]], partition_key=new_id) 
+result = container.scripts.execute_stored_procedure(sproc=created_sproc,params=[new_item], partition_key=new_id) 
 ```
 
 ---
@@ -402,7 +402,8 @@ The following code shows how to call a pretrigger using the Python SDK:
 ```python
 item = {'category': 'Personal', 'name': 'Groceries',
         'description': 'Pick up strawberries', 'isComplete': False}
-container.create_item(item, {'pre_trigger_include': 'trgPreValidateToDoItemTimestamp'})
+
+result = container.create_item(item, pre_trigger_include='trgPreValidateToDoItemTimestamp')
 ```
 
 ---

articles/cosmos-db/nosql/transactional-batch.md

@@ -89,7 +89,7 @@ if (response.IsSuccessStatusCode)
 ```
 
 > [!IMPORTANT]
-> If there's a failure, the failed operation will have a status code of its corresponding error. All the other operations will have a 424 status code (failed dependency). In the example below, the operation fails because it tries to create an item that already exists (409 HttpStatusCode.Conflict). The status code enables one to identify the cause of transaction failure.
+> If there's a failure, the failed operation will have a status code of its corresponding error. All the other operations will have a 424 status code (failed dependency). If the operation fails because it tries to create an item that already exists, a status code of 409 (conflict) is returned. The status code enables one to identify the cause of transaction failure.
 
 ### [Java](#tab/java)
 
@@ -136,7 +136,7 @@ if (response.isSuccessStatusCode())
 ```
 
 > [!IMPORTANT]
-> If there's a failure, the failed operation will have a status code of its corresponding error. All the other operations will have a 424 status code (failed dependency). In the example below, the operation fails because it tries to create an item that already exists (409 HttpStatusCode.Conflict). The status code enables one to identify the cause of transaction failure.
+> If there's a failure, the failed operation will have a status code of its corresponding error. All the other operations will have a 424 status code (failed dependency). If the operation fails because it tries to create an item that already exists, a status code of 409 (conflict) is returned. The status code enables one to identify the cause of transaction failure.
 
 ---
 

articles/cosmos-db/partitioning-overview.md

@@ -123,7 +123,10 @@ If your container could grow to more than a few physical partitions, then you sh
 
 ## Use item ID as the partition key
 
-If your container has a property that has a wide range of possible values, it's likely a great partition key choice. One possible example of such a property is the *item ID*. For small read-heavy containers or write-heavy containers of any size, the *item ID* is naturally a great choice for the partition key.
+> [!NOTE]
+> This section primarily applies to the API for NoSQL. Other APIs, such as the API for Gremlin, do not support the unique identifier as the partition key.
+
+If your container has a property that has a wide range of possible values, it's likely a great partition key choice. One possible example of such a property is the *item ID*. For small read-heavy containers or write-heavy containers of any size, the *item ID* (`/id`) is naturally a great choice for the partition key.
 
 The system property *item ID* exists in every item in your container. You may have other properties that represent a logical ID of your item. In many cases, these IDs are also great partition key choices for the same reasons as the *item ID*.
 

articles/cosmos-db/scripts/cli/nosql/create.md

@@ -51,6 +51,9 @@ This script uses the following commands. Each command in the table links to comm
 | [az cosmosdb sql container create](/cli/azure/cosmosdb/sql/container#az-cosmosdb-sql-container-create) | Creates an Azure Cosmos DB for NoSQL container. |
 | [az group delete](/cli/azure/resource#az-resource-delete) | Deletes a resource group including all nested resources. |
 
+> [!IMPORTANT]
+> Use `az cosmsodb sql database create` to create a NoSQL database. The `az cosmosdb database create` command is deprecated.
+
 ## Next steps
 
 For more information on the Azure Cosmos DB CLI, see [Azure Cosmos DB CLI documentation](/cli/azure/cosmosdb).