Merge pull request #4879 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-21 17:07 UTC

Author: learn-build-service-prod[bot]

articles/cosmos-db/TOC.yml

@@ -315,6 +315,8 @@
       href: throughput-serverless.md?context=/azure/cosmos-db/context/context
     - name: Best practices for scaling provisioned throughput
       href: scaling-provisioned-throughput-best-practices.md?context=/azure/cosmos-db/context/context
+    - name: Understanding request unit consumption
+      href: understand-request-unit-consumption.md?context=/azure/cosmos-db/context/context
     - name: Burst capacity
       items:
         - name: Burst capacity overview

articles/cosmos-db/best-practices-javascript.md

@@ -32,7 +32,7 @@ This guide includes best practices for solutions built using the latest version
 
 - The request charge of a specified operation correlates directly to the size of the document. We recommend reducing the size of your documents as operations on large documents cost more than operations on smaller documents.
 - Some characters are restricted and can't be used in some identifiers: '/', '\\', '?', '#'. The general recommendation is to not use any special characters in identifiers like database name, collection name, item ID, or partition key to avoid any unexpected behavior.
-- The Azure Cosmos DB indexing policy also allows you to specify which document paths to include or exclude from indexing by using indexing paths `IndexingPolicy#getIncludedPaths()` and `IndexingPolicy#getExcludedPaths()`.  Ensure that you exclude unused paths from indexing for faster writes.  For more information, see [creating indexes using the SDK sample](performance-tips-java-sdk-v4.md#indexing-policy).
+- The Azure Cosmos DB indexing policy also allows you to specify which document paths to include or exclude from indexing by using indexing paths `includedPaths` and `excludedPaths`. Ensure that you exclude unused paths from indexing for faster writes. For more information, see [creating indexes using the SDK sample](how-to-manage-indexing-policy.md#use-the-nodejs-sdk).
 
 ## Host characteristics
 

articles/cosmos-db/cassandra/support.md

@@ -350,7 +350,7 @@ Azure Cosmos DB supports Azure role-based access control (Azure RBAC) for provis
 
 ## Keyspace and Table options
 
-The options for region name, class, replication_factor, and datacenter in the `CREATE KEYSPACE` command are ignored currently. The system uses the underlying Azure Cosmos DB's [global distribution](../global-distribution.md) replication method to add the regions. If you need the cross-region presence of data, you can enable it at the account level with PowerShell, CLI, or the Azure portal. For more information, see [Add regions to your database account](../how-to-manage-database-account.yml#add-remove-regions-from-your-database-account).
+The options for region name, class, replication_factor, and datacenter in the `CREATE KEYSPACE` command are ignored currently. The system uses the underlying Azure Cosmos DB's [global distribution](../global-distribution.md) replication method to add the regions. If you need the cross-region presence of data, you can enable it at the account level with PowerShell, CLI, or the Azure portal. For more information, see [Add regions to your database account](../how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account).
 
 Durable_writes can't be disabled because Azure Cosmos DB ensures every write is durable. In every region, Azure Cosmos DB replicates the data across the replica set that is made up of four replicas and this replica set [configuration](../global-distribution.md) can't be modified.
 

articles/cosmos-db/change-feed-processor.md

@@ -22,10 +22,12 @@ The main benefit of using the change feed processor is its fault-tolerant design
 
 ## Supported SDKs
 
-|  .NET V3  |   Java    |  Node.JS  |  Python   |
+|  .NET V3  |   Java    |  Node.js  |  Python   |
 | --------- | --------- | --------- | --------- |
 |     ✓     |    ✓     |     ✕     |    ✕     |
 
+For Python and Node.js, use the [change feed pull model](change-feed-pull-model.md), which provides direct access to the change feed with manual checkpoint management, because the change feed processor library is only available for .NET and Java.
+
 ## Components of the change feed processor
 
 The change feed processor has four main components:

articles/cosmos-db/conceptual-resilient-sdk-applications.md

@@ -28,6 +28,9 @@ Gateway mode is always used to fetch metadata such as the account, container, an
 
 In summary, for SDKs in Gateway mode, you can expect HTTP traffic, while for SDKs in Direct mode, you can expect a combination of HTTP and TCP traffic under different circumstances, such as initialization, fetching metadata, or routing information.
 
+> [!NOTE]
+> Direct mode is available only in the .NET and Java SDKs. All other Azure Cosmos DB SDKs use Gateway mode. The error status codes and retry guidance in this article apply across all SDKs. For more information, see [connectivity modes](sdk-connection-modes.md).
+
 ## Client instances and connections
 
 Regardless of the connectivity mode, it's critical to maintain a singleton instance of the SDK client per account per application. Connections, both HTTP and TCP, are scoped to the client instance. Most compute environments have limitations in terms of the number of connections that can be open at the same time. When these limits are reached, connectivity is affected.

articles/cosmos-db/data-residency.md

@@ -20,7 +20,7 @@ In Azure Cosmos DB, you can configure your data and backups to remain in a singl
 
 ## Residency requirements for data
 
-In Azure Cosmos DB, you must explicitly configure the cross-region data replication. Learn how to configure geo-replication using [Azure portal](how-to-manage-database-account.yml#add-remove-regions-from-your-database-account), [Azure CLI](scripts/cli/common/regions.md). To meet data residency requirements, you can create an Azure Policy definition that allows certain regions to prevent data replication to unwanted regions.
+In Azure Cosmos DB, you must explicitly configure the cross-region data replication. Learn how to configure geo-replication using [Azure portal](how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account), [Azure CLI](scripts/cli/common/regions.md). To meet data residency requirements, you can create an Azure Policy definition that allows certain regions to prevent data replication to unwanted regions.
 
 ## Residency requirements for backups
 

articles/cosmos-db/distribute-data-globally.md

@@ -65,6 +65,6 @@ With Azure Cosmos DB, you can add or remove the regions associated with your acc
 * [Global distribution - under the hood](global-distribution.md)
 * [How to configure multi-region writes in your applications](how-to-multi-master.md)
 * [Configure multiple write-regions](how-to-manage-database-account.yml#configure-multiple-write-regions)
-* [Add or remove regions from your Azure Cosmos DB account](how-to-manage-database-account.yml#add-remove-regions-from-your-database-account)
+* [Add or remove regions from your Azure Cosmos DB account](how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account)
 * [Create a custom conflict resolution policy for API for NoSQL accounts](how-to-manage-conflicts.md#create-a-custom-conflict-resolution-policy)
 * [Programmable consistency models in Azure Cosmos DB](consistency-levels.md)