Merge pull request #4833 from MicrosoftDocs/main

learn-build-service-prod[bot] · web-flow · commit f59316932d52 · 2026-04-15T17:07:58.000Z
Auto Publish – main to live - 2026-04-15 17:05 UTC
diff --git a/articles/cosmos-db/access-key-vault-managed-identity.md b/articles/cosmos-db/access-key-vault-managed-identity.md
@@ -31,7 +31,7 @@ Azure Cosmos DB may need to read secret/key data from Azure Key Vault. For examp
 1. In a terminal or command window, store the names of your Azure Key Vault resource, Azure Cosmos DB account, and resource group as shell variables named ``keyVaultName``, ``cosmosName``, and ``resourceGroupName``.
 
     ```azurecli-interactive
-    # Variable for function app name
+    # Variable for Key Vault name
     keyVaultName="msdocs-keyvault"
     
     # Variable for Azure Cosmos DB account name
diff --git a/articles/cosmos-db/data-explorer-shortcuts.md b/articles/cosmos-db/data-explorer-shortcuts.md
@@ -22,7 +22,7 @@ These shortcuts are used with the toolbar present in the Data Explorer.
 
 | | Windows | macOS |
 | --- | --- | --- |
-| **Close tab** | <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>W</kbd> | <kbd>Cmd</kbd>+<kbd>Opt</kbd>+<kbd>W |
+| **Close tab** | <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>W</kbd> | <kbd>Cmd</kbd>+<kbd>Opt</kbd>+<kbd>W</kbd> |
 | **Discard edit Query/Item/Stored Procedure/Trigger/UDF** | <kbd>Esc</kbd> | <kbd>Esc</kbd> |
 | **Download Query to Disk** | <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>S</kbd> | <kbd>Cmd</kbd>+<kbd>Shift</kbd>+<kbd>S</kbd> |
 | **Enable/Disable Copilot** | <kbd>Ctrl</kbd>+<kbd>P</kbd> | <kbd>Cmd</kbd>+<kbd>P</kbd> |
diff --git a/articles/cosmos-db/diagnostic-queries.md b/articles/cosmos-db/diagnostic-queries.md
@@ -108,7 +108,7 @@ Common queries are shown in the resource-specific and Azure Diagnostics tables.
    AzureDiagnostics
    | where Category == "QueryRuntimeStatistics"
    //specify collection and database
-   //| where databasename_s == "DBNAME" and collectioname_s == "COLLECTIONNAME"
+   //| where databasename_s == "DBNAME" and collectionname_s == "COLLECTIONNAME"
    | join kind=inner operationsbyUserAgent on activityId_g
    | summarize max(responseLength_s1) by querytext_s
    | order by max_responseLength_s1 desc
@@ -138,7 +138,7 @@ Common queries are shown in the resource-specific and Azure Diagnostics tables.
    | where TimeGenerated >= now(-1d)
    | where Category == 'PartitionKeyRUConsumption'
    //specify collection and database
-   //| where databasename_s == "DBNAME" and collectioname_s == "COLLECTIONNAME"
+   //| where databasename_s == "DBNAME" and collectionname_s == "COLLECTIONNAME"
    // filter by operation type
    //| where operationType_s == 'Create'
    | summarize sum(todouble(requestCharge_s)) by toint(partitionKeyRangeId_s)
@@ -169,7 +169,7 @@ Common queries are shown in the resource-specific and Azure Diagnostics tables.
    | where TimeGenerated >= now(-1d)
    | where Category == 'PartitionKeyRUConsumption'
    //specify collection and database
-   //| where databasename_s == "DBNAME" and collectioname_s == "COLLECTIONNAME"
+   //| where databasename_s == "DBNAME" and collectionname_s == "COLLECTIONNAME"
    // filter by operation type
    //| where operationType_s == 'Create'
    | summarize sum(todouble(requestCharge_s)) by partitionKey_s, partitionKeyRangeId_s
diff --git a/articles/cosmos-db/find-request-unit-charge.md b/articles/cosmos-db/find-request-unit-charge.md
@@ -169,7 +169,7 @@ request_charge = container.client_connection.last_response_headers["x-ms-request
 
 ```python
 existing_item = container.read_item(
-    item="aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb"
+    item="aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb",
     partition_key="61dba35b-4f02-45c5-b648-c6badc0cbd79"
 )
 
diff --git a/articles/cosmos-db/free-tier.md b/articles/cosmos-db/free-tier.md
@@ -99,7 +99,7 @@ If the option to create a free-tier account is disabled or if you receive an err
 
 After you create a free tier account, you can start building apps with Azure Cosmos DB.
 
-* [Quickstart: Use Azure Cosmos DB for NoSQL with Azure SDK for .NET](create-sql-api-dotnet-v4.md)
+* [Quickstart: Use Azure Cosmos DB for NoSQL with Azure SDK for .NET](quickstart-dotnet.md)
 * [Quickstart: Use Azure Cosmos DB for MongoDB with Node.js](mongodb/quickstart-nodejs.md)
 * [Tutorial: Create a Jupyter Notebook to analyze data in your Azure Cosmos DB for NoSQL account](tutorial-create-notebook-vscode.md)
 * [Understand your Azure Cosmos DB bill](understand-your-bill.md)
diff --git a/articles/cosmos-db/get-started-change-data-capture.md b/articles/cosmos-db/get-started-change-data-capture.md
@@ -104,7 +104,7 @@ Now create and configure a source to flow data from the Azure Cosmos DB account'
 
 ### Working with source options
   
-When you check any of the `Capture intermediate updates`, `Capture Deltes`, and `Capture Transactional store TTLs` options, your CDC process will create and populate the `__usr_opType` field in sink with the following values:
+When you check any of the `Capture intermediate updates`, `Capture Deletes`, and `Capture Transactional store TTLs` options, your CDC process will create and populate the `__usr_opType` field in sink with the following values:
 
 | Value | Description | Option
 | --- | --- | --- |
diff --git a/articles/cosmos-db/how-to-always-encrypted.md b/articles/cosmos-db/how-to-always-encrypted.md
@@ -282,13 +282,13 @@ await database.DefineContainer("my-container", "/partition-key")
 
 ```java
 ClientEncryptionIncludedPath path1 = new ClientEncryptionIncludedPath();
-path1.setClientEncryptionKeyId("my-key"):
+path1.setClientEncryptionKeyId("my-key");
 path1.setPath("/property1");
 path1.setEncryptionType(CosmosEncryptionType.DETERMINISTIC.getName());
 path1.setEncryptionAlgorithm(CosmosEncryptionAlgorithm.AEAES_256_CBC_HMAC_SHA_256.getName());
 
 ClientEncryptionIncludedPath path2 = new ClientEncryptionIncludedPath();
-path2.setClientEncryptionKeyId("my-key"):
+path2.setClientEncryptionKeyId("my-key");
 path2.setPath("/property2");
 path2.setEncryptionType(CosmosEncryptionType.RANDOMIZED.getName());
 path2.setEncryptionAlgorithm(CosmosEncryptionAlgorithm.AEAES_256_CBC_HMAC_SHA_256.getName());
diff --git a/articles/cosmos-db/how-to-define-unique-keys.md b/articles/cosmos-db/how-to-define-unique-keys.md
@@ -20,7 +20,7 @@ This article presents the different ways to define [unique keys](unique-keys.md)
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 
-1. [Create a new Azure Cosmos DB account](create-sql-api-dotnet.md#create-account) or select an existing one.
+1. [Create a new Azure Cosmos DB account](how-to-create-account.md) or select an existing one.
 
 1. Open the **Data Explorer** pane and select the container that you want to work on.
 
diff --git a/articles/cosmos-db/how-to-develop-emulator.md b/articles/cosmos-db/how-to-develop-emulator.md
@@ -72,7 +72,7 @@ To get started, get the Windows-variant of the container image from the [Microso
 To get started, download and install the latest version of Azure Cosmos DB Emulator on your local computer.
 
 > [!TIP]
-> The [emulator release notes](local-emulator-release-notes.md) article lists all the available versions and the feature updates that were made in each release.
+> The [emulator release notes](emulator-release-notes.md) article lists all the available versions and the feature updates that were made in each release.
 
 1. Download the [Azure Cosmos DB emulator](https://aka.ms/cosmosdb-emulator).
 
@@ -111,7 +111,7 @@ The Docker (Windows) container image doesn't support the API for MongoDB.
 To get started, download and install the latest version of Azure Cosmos DB Emulator on your local computer.
 
 > [!TIP]
-> The [emulator release notes](local-emulator-release-notes.md) article lists all the available versions and the feature updates that were made in each release.
+> The [emulator release notes](emulator-release-notes.md) article lists all the available versions and the feature updates that were made in each release.
 
 1. Download the [Azure Cosmos DB emulator](https://aka.ms/cosmosdb-emulator).
 
@@ -134,7 +134,7 @@ The Docker container variant (Linux or Windows) of the emulator doesn't support
 To get started, download and install the latest version of Azure Cosmos DB Emulator on your local computer.
 
 > [!TIP]
-> The [emulator release notes](local-emulator-release-notes.md) article lists all the available versions and the feature updates that were made in each release.
+> The [emulator release notes](emulator-release-notes.md) article lists all the available versions and the feature updates that were made in each release.
 
 1. Download the [Azure Cosmos DB emulator](https://aka.ms/cosmosdb-emulator).
 
diff --git a/articles/cosmos-db/how-to-dotnet-read-item.md b/articles/cosmos-db/how-to-dotnet-read-item.md
@@ -41,7 +41,7 @@ The following example point reads a single item asynchronously and returns a des
 
 :::code language="csharp" source="~/cosmos-db-nosql-dotnet-samples/275-read-item/Program.cs" id="read_item" :::
 
-The [``Database.ReadItemAsync<>``](/dotnet/api/microsoft.azure.cosmos.container.readitemasync) method reads an item and returns an object of type [``ItemResponse<>``](/dotnet/api/microsoft.azure.cosmos.itemresponse-1). The **ItemResponse<>** type inherits from the [``Response<>``](/dotnet/api/microsoft.azure.cosmos.response-1) type, which contains an implicit conversion operator to convert the object into the generic type. To learn more about implicit operators, see [user-defined conversion operators](/dotnet/csharp/language-reference/operators/user-defined-conversion-operators).
+The [``Container.ReadItemAsync<>``](/dotnet/api/microsoft.azure.cosmos.container.readitemasync) method reads an item and returns an object of type [``ItemResponse<>``](/dotnet/api/microsoft.azure.cosmos.itemresponse-1). The **ItemResponse<>** type inherits from the [``Response<>``](/dotnet/api/microsoft.azure.cosmos.response-1) type, which contains an implicit conversion operator to convert the object into the generic type. To learn more about implicit operators, see [user-defined conversion operators](/dotnet/csharp/language-reference/operators/user-defined-conversion-operators).
 
 Alternatively, you can return the **ItemResponse<>** generic type and explicitly get the resource. The more general **ItemResponse<>** type also contains useful metadata about the underlying API operation. In this example, metadata about the request unit charge for this operation is gathered using the **RequestCharge** property.
 
diff --git a/articles/cosmos-db/how-to-python-create-container.md b/articles/cosmos-db/how-to-python-create-container.md
@@ -47,7 +47,7 @@ The following example creates a container with the [``DatabaseProxy.create_conta
 
 ### Create a container asynchronously
 
-You can also create a database asynchronously using similar object and methods in the [azure.cosmos.aio](/python/api/azure-cosmos/azure.cosmos.aio) namespace. For example, use the [DatabaseProxy.create_database](/python/api/azure-cosmos/azure.cosmos.aio.databaseproxy#azure-cosmos-aio-databaseproxy-create-container) method or the [CosmoClient.create_database_if_not_exists](/python/api/azure-cosmos/azure.cosmos.aio.databaseproxy#azure-cosmos-aio-databaseproxy-create-container-if-not-exists) method.
+You can also create a container asynchronously using similar object and methods in the [azure.cosmos.aio](/python/api/azure-cosmos/azure.cosmos.aio) namespace. For example, use the [DatabaseProxy.create_container](/python/api/azure-cosmos/azure.cosmos.aio.databaseproxy#azure-cosmos-aio-databaseproxy-create-container) method or the [CosmosClient.create_container_if_not_exists](/python/api/azure-cosmos/azure.cosmos.aio.databaseproxy#azure-cosmos-aio-databaseproxy-create-container-if-not-exists) method.
 
 Working asynchronously is useful when you want to perform multiple operations in parallel. For more information, see [Using the asynchronous client](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos#using-the-asynchronous-client).
 
diff --git a/articles/cosmos-db/how-to-python-create-database.md b/articles/cosmos-db/how-to-python-create-database.md
@@ -47,7 +47,7 @@ The following example creates a database with the [`CosmosClient.create_database
 
 ### Create a database asynchronously
 
-You can also create a database asynchronously using similar object and methods in the [azure.cosmos.aio](/python/api/azure-cosmos/azure.cosmos.aio) namespace. For example, use the [`CosmosClient.create_database`](/python/api/azure-cosmos/azure.cosmos.aio.cosmosclient#azure-cosmos-aio-cosmosclient-create-database) method or the ['CosmoClient.create_database_if_not_exists](/python/api/azure-cosmos/azure.cosmos.aio.cosmosclient#azure-cosmos-aio-cosmosclient-create-database-if-not-exists) method.
+You can also create a database asynchronously using similar object and methods in the [azure.cosmos.aio](/python/api/azure-cosmos/azure.cosmos.aio) namespace. For example, use the [`CosmosClient.create_database`](/python/api/azure-cosmos/azure.cosmos.aio.cosmosclient#azure-cosmos-aio-cosmosclient-create-database) method or the [`CosmosClient.create_database_if_not_exists`](/python/api/azure-cosmos/azure.cosmos.aio.cosmosclient#azure-cosmos-aio-cosmosclient-create-database-if-not-exists) method.
 
 Working asynchronously is useful when you want to perform multiple operations in parallel. For more information, see [Using the asynchronous client](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos#using-the-asynchronous-client).
 
diff --git a/articles/cosmos-db/how-to-query-container.md b/articles/cosmos-db/how-to-query-container.md
@@ -42,7 +42,7 @@ SELECT * FROM c WHERE c.DeviceId > 'XMS-0001'
 The following query doesn't have a filter on the partition key (`DeviceId`). Therefore, it must fan out to all physical partitions where it's run against each partition's index:
 
 ```sql
-SELECT * FROM c WHERE c.Location = 'Seattle`
+SELECT * FROM c WHERE c.Location = 'Seattle'
 ```
 
 Each physical partition has its own index. Therefore, when you run a cross-partition query on a container, you're effectively running one query *per* physical partition. Azure Cosmos DB automatically aggregates results across different physical partitions.
diff --git a/articles/cosmos-db/how-to-time-to-live.md b/articles/cosmos-db/how-to-time-to-live.md
@@ -276,7 +276,7 @@ Container container = database.GetContainer("container");
 
 SalesOrder item = new (
     "SO05", 
-    "CO18009186470"
+    "CO18009186470",
     // Expire sales order in 30 days using "ttl" property
     ttl:  60 * 60 * 24 * 30
 );
diff --git a/articles/cosmos-db/kafka-connector-source-v2.md b/articles/cosmos-db/kafka-connector-source-v2.md
@@ -141,7 +141,7 @@ Alternatively, use the connector’s REST API:
 
 ```bash
 # Curl to Kafka connect service
-curl -X DELETE http://localhost:8083/connectors/cosmosdb-source-connector
+curl -X DELETE http://localhost:8083/connectors/cosmosdb-source-connector-v2
 ```
 
 To delete the created Azure Cosmos DB service and its resource group using Azure CLI, refer to these [steps](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/cosmos/azure-cosmos-kafka-connect/docs/CosmosDB_Setup.md#cleanup).
diff --git a/articles/cosmos-db/quickstart-portal.md b/articles/cosmos-db/quickstart-portal.md
@@ -96,8 +96,6 @@ Next, use the Data Explorer to create a database and container in-portal.
 
     :::image source="media/quickstart-portal/new-container-dialog.png" alt-text="Screenshot of the dialog to create a new database and container with the specified options filled.":::
 
-1. Create a new file named *demo.bicepparam* or (`demo.bicepparam`).
-
 1. Observe the newly created database and container in the Data Explorer's hierarchy.
 
     :::image source="media/quickstart-portal/data-explorer-tree.png" alt-text="Screenshot of the Data Explorer hierarchy with a database container present.":::
diff --git a/articles/cosmos-db/sdk-nodejs.md b/articles/cosmos-db/sdk-nodejs.md
@@ -23,7 +23,7 @@ appliesto:
 |API Documentation  |  [JavaScript SDK reference documentation](/javascript/api/%40azure/cosmos/)
 |SDK installation instructions  |  `npm install @azure/cosmos`
 |Contribute to SDK | [Contributing guide for azure-sdk-for-js repo](https://github.com/Azure/azure-sdk-for-js/blob/main/CONTRIBUTING.md)
-| Getting started tutorial | [Get started with the JavaScript SDK](sql-api-nodejs-get-started.md)
+| Getting started tutorial | [Get started with the JavaScript SDK](how-to-javascript-get-started.md)
 | Web app tutorial | [Build a Node.js web application using Azure Cosmos DB](quickstart-nodejs.md)
 | Current supported Node.js platforms | [LTS versions of Node.js](https://github.com/nodejs/release#release-schedule)
 
diff --git a/articles/cosmos-db/tune-connection-configurations-net-sdk-v3.md b/articles/cosmos-db/tune-connection-configurations-net-sdk-v3.md
@@ -36,7 +36,7 @@ You configure the connection mode when you create the `CosmosClient` instance in
 ```csharp
 CosmosClient client = new CosmosClient(
   "<nosql-account-endpoint>",
-  tokenCredential
+  tokenCredential,
   new CosmosClientOptions
   {
       ConnectionMode = ConnectionMode.Gateway // ConnectionMode.Direct is the default
@@ -58,7 +58,7 @@ Direct mode can be customized through the *CosmosClientOptions* passed to the *C
 | PortReuseMode      | PortReuseMode.ReuseUnicastPort     | PortReuseMode.ReuseUnicastPort  | This represents the client port reuse policy used by the transport stack. |
 
 > [!NOTE]
-> See also [Networking perfomance tips for direct connection mode](performance-tips-dotnet-sdk-v3.md?tabs=trace-net-core#networking)
+> See also [Networking performance tips for direct connection mode](performance-tips-dotnet-sdk-v3.md?tabs=trace-net-core#networking)
 
 #### Customizing gateway connection mode
 
diff --git a/articles/postgresql/compute-storage/concepts-storage-premium-ssd-v2.md b/articles/postgresql/compute-storage/concepts-storage-premium-ssd-v2.md
@@ -56,8 +56,11 @@ To learn more, see [Compute options in Azure Database for PostgreSQL](concepts-c
 Premium SSD v2 supports *High Availability, Geo-Redundant backups, Geo Replicas, Major Version Upgrade, CMK (Customer Managed Keys) and, Geo DR(Disaster Recovery)* features for Azure Database for PostgreSQL in below supported regions.
 
 **Americas**: Brazil South*, Brazil Southeast*, Canada Central, Canada East, Central US, East US, East US 2, North Central US, South Central US, West Central US, West US, West US 2, West US 3*.
+
 **Europe**: Austria East, France Central*, Germany West Central, Germany North, Italy North*, North Europe, Norway East, Norway West, Poland Central*, Spain Central*, Sweden Central*, Switzerland North, Switzerland West, UK South, UK West, West Europe.
-**Asia Pacific & Middle East**: Australia Central 2*, Australia East, Australia Southeast, Central India, East Asia, Indonesia Central*, Israel Central*, Japan East, Japan West, Korea Central*, Malaysia West*, New Zealand North*, South India, Southeast Asia, UAE North*.
+
+**Asia Pacific & Middle East**: Australia Central 2*, Australia East, Australia Southeast, Central India, East Asia, Indonesia Central*, Israel Central*, Japan East, Japan West, Jio India Central, Jio India West, Korea Central*, Malaysia West*, New Zealand North*, South India, Southeast Asia, UAE North*.
+
 **Africa**: South Africa North, South Africa West.
 
 Sovereign regions, including China North 3 and US Gov Virginia, support only standalone SSDv2 deployments and don't currently support these features. 
@@ -76,7 +79,7 @@ Sovereign regions, including China North 3 and US Gov Virginia, support only sta
 
 - You can adjust disk performance settings (IOPS or throughput) up to four times within a 24-hour period. For newly created disks, the limit is three adjustments during the first 24 hours.
 
-- For larger servers, the initial automated backup takes longer to complete and appears in the Azure portal after it completes. No action is required during this time. We recommend waiting for the initial backup to complete before performing any backup‑dependent operations, such as creating in‑region read replicas. After the initial backup, all subsequent backups are incremental and typically complete quickly.
+- For larger servers, the initial automated backup takes longer to complete and appears in the Azure portal after it completes. No action is required during this time. We recommend waiting for the initial backup to complete before performing any backup‑dependent operations, such as creating in‑region read replicas or performing major version upgrade. After the initial backup, all subsequent backups are incremental and typically complete quickly.
 
 
 - Online migration from Premium SSD to Premium SSD v2 isn't supported. To migrate between these storage types, you can either perform a [point-in-time-restore](../backup-restore/concepts-backup-restore.md#point-in-time-recovery) from a Premium SSD server to a new server using Premium SSD v2. Alternatively, you can create a read replica from a Premium SSD server to a Premium SSD v2 server and promote it after replication completes. Because storage autogrow isn't currently supported on Premium SSD v2, you must disable storage autogrow on the source Premium SSD server before starting the migration.

Original file line number	Diff line number	Diff line change
`@@ -169,7 +169,7 @@ request_charge = container.client_connection.last_response_headers["x-ms-request`
`169`	`169`
`170`	`170`	```python
`171`	`171`	`existing_item = container.read_item(`
`172`		`- item="aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb"`
	`172`	`+ item="aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb",`
`173`	`173`	`partition_key="61dba35b-4f02-45c5-b648-c6badc0cbd79"`
`174`	`174`	`)`
`175`	`175`