Merge pull request #277521 from jcocchi/bypass-cache-ga

Cosmos DB: remove preview tag from bypass cache docs

Author: prmerger-automator[bot]

articles/cosmos-db/how-to-configure-integrated-cache.md

@@ -132,15 +132,15 @@ container.query_items(
 ---
 
 
-## Bypass the integrated cache (Preview)
+## Bypass the integrated cache
 
 Use the `BypassIntegratedCache` request option to control which requests use the integrated cache. Writes, point reads, and queries that bypass the integrated cache won't use cache storage, saving space for other items. Requests that bypass the cache are still routed through the dedicated gateway. These requests are served from the backend and cost RUs.
 
 Bypassing the cache is supported in these versions of each SDK:
 
 | SDK | Supported versions |
 | --- | ------------------ |
-| **.NET SDK v3** | *>= 3.35.0-preview* |
+| **.NET SDK v3** | *>= 3.39.0* |
 | **Java SDK v4** | *>= 4.49.0* |
 | **Node.js SDK** | Not supported |
 | **Python SDK**  | Not supported |

articles/cosmos-db/integrated-cache.md

@@ -132,11 +132,11 @@ To better understand the `MaxIntegratedCacheStaleness` parameter, consider the f
 
 [Learn to configure the `MaxIntegratedCacheStaleness`.](how-to-configure-integrated-cache.md#adjust-maxintegratedcachestaleness)
 
-## Bypass the integrated cache (Preview)
+## Bypass the integrated cache
 
-The integrated cache has a limited storage capacity determined by the dedicated gateway SKU provisioned. By default, all requests from clients configured with the dedicated gateway connection string go through the integrated cache and take up cache space. You can control which items and queries are cached with the bypass integrated cache request option, currently in preview. This request option is useful for item writes or read requests that aren't expected to be frequently repeated. Bypassing the integrated cache for items with infrequent access saves cache space for items with more repeats, increasing RU saving potential and reducing evictions. Requests that bypass the cache are still routed through the dedicated gateway. These requests are served from the backend and cost RUs.
+The integrated cache has a limited storage capacity determined by the dedicated gateway SKU provisioned. By default, all requests from clients configured with the dedicated gateway connection string go through the integrated cache and take up cache space. You can control which items and queries are cached with the bypass integrated cache request option. This request option is useful for item writes or read requests that aren't expected to be frequently repeated. Bypassing the integrated cache for items with infrequent access saves cache space for items with more repeats, increasing RU saving potential and reducing evictions. Requests that bypass the cache are still routed through the dedicated gateway. These requests are served from the backend and cost RUs.
 
-[Learn to bypass the integrated cache.](how-to-configure-integrated-cache.md#bypass-the-integrated-cache-preview)
+[Learn to bypass the integrated cache.](how-to-configure-integrated-cache.md#bypass-the-integrated-cache)
 
 ## Metrics