@@ -297,7 +297,17 @@ await foreach (SearchResult<SearchDocument> result in results.GetResultsAsync())
 
 A hybrid query can be tuned to control how much of each subquery contributes to the combined results. Setting `maxTextRecallSize` specifies how many BM25-ranked results are passed to the hybrid ranking model.
 
-If you use `maxTextRecallSize`, you might also want to set `CountAndFacetMode`. This parameter determines whether the `count` and `facets` should include all documents that matched the search query, or only those documents retrieved within the `maxTextRecallSize` window. The default value is "countAllResults".
+If your request includes facets, use nonvector fields that are marked as `facetable` in the index. Vector fields aren't facetable.
+
+Facet counts depend on the query type:
+
++ In a text-only query, facets count the documents that match the text query.
++ In a vector-only query, facets count the `k` documents returned by the vector query.
++ In a hybrid query, facets account for both vector and text results. The vector side contributes the `k` nearest documents. The text side contributes BM25-ranked documents. The `countAndFacetMode` parameter determines whether count and facet calculations use all text matches or only the text matches that are retrieved for ranking.
+
+If you use `maxTextRecallSize`, you might also want to set `countAndFacetMode`. This parameter determines whether `count` and `facets` include all documents that matched the text query, or only documents retrieved within the `maxTextRecallSize` window. The default value is `countAllResults`.
+
+With the default `countAllResults` mode, counts and facets can include text-side documents that aren't retrieved for RRF ranking because they fall outside the `maxTextRecallSize` window. Increasing `maxTextRecallSize` increases the number of BM25-ranked documents available for ranking, but doesn't increase the vector contribution beyond `k`. Use `countRetrievableResults` if you want count and facet calculations scoped to the documents retrieved for hybrid ranking.
 
 We recommend the [latest preview REST API](/rest/api/searchservice/documents/search-post?view=rest-searchservice-2025-11-01-preview&preserve-view=true) for setting these options.
 
@@ -310,7 +320,7 @@ We recommend the [latest preview REST API](/rest/api/searchservice/documents/sea
 
    + `maxTextRecallSize` specifies the number of BM25-ranked results to provide to the Reciprocal Rank Fusion (RRF) ranker used in hybrid queries. The default is 1,000. The maximum is 10,000.
 
-   + `countAndFacetMode` reports the counts for the BM25-ranked results (and for facets if you're using them). The default is all documents that match the query. Optionally, you can scope "count" to the `maxTextRecallSize`.
+   + `countAndFacetMode` reports the count and facet scope for a hybrid query. The default, `countAllResults`, uses the full hybrid result set, including all documents that match the text query, even if some of those text matches aren't retrieved for RRF ranking because they fall outside the `maxTextRecallSize` window. Use `countRetrievableResults` to scope count and facets to the documents retrieved for ranking, including `maxTextRecallSize` BM25-ranked documents and the `k` vector matches.
 
 1. Set `maxTextRecallSize`:
 
@@ -320,7 +330,7 @@ We recommend the [latest preview REST API](/rest/api/searchservice/documents/sea
 
 The following REST examples show two use-cases for setting `maxTextRecallSize`. 
 
-The first example reduces `maxTextRecallSize` to 100, limiting the text side of the hybrid query to just 100 document. It also sets `countAndFacetMode` to include only those results from `maxTextRecallSize`.
+The first example reduces `maxTextRecallSize` to 100, limiting the text side of the hybrid query to just 100 documents. It also sets `countAndFacetMode` to include only retrievable documents in count and facet calculations.
 
 ```http
 POST https://[service-name].search.windows.net/indexes/[index-name]/docs/search?api-version=2025-11-01-preview 

@@ -5,8 +5,10 @@ author: haileytap
 ms.author: haileytapia
 ms.service: azure-ai-search
 ms.topic: include
-ms.date: 04/16/2026
+ms.date: 05/19/2026
 ---
 
 > [!NOTE]
 > Some agentic retrieval features are generally available in the 2026-04-01 REST API version via programmatic access. The Azure portal and Microsoft Foundry portal continue to provide preview-only access to all agentic retrieval features. For migration guidance, including a breakdown of what's generally available and what remains in preview, see [Migrate agentic retrieval code to the latest version](../../agentic-retrieval-how-to-migrate.md).
+>
+> If you choose to use a preview REST API version, you can access agentic retrieval capabilities that aren't yet generally available. Preview features are provided without a service-level agreement and aren't recommended for production workloads. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
\ No newline at end of file

@@ -5,8 +5,10 @@ author: haileytap
 ms.author: haileytapia
 ms.service: azure-ai-search
 ms.topic: include
-ms.date: 04/16/2026
+ms.date: 05/19/2026
 ---
 
 > [!NOTE]
 > This agentic retrieval feature is generally available in the 2026-04-01 REST API version via programmatic access. The Azure portal and Microsoft Foundry portal continue to provide preview-only access to all agentic retrieval features. For migration guidance, see [Migrate agentic retrieval code to the latest version](../../agentic-retrieval-how-to-migrate.md).
+>
+> If you choose to use a preview REST API version, you can access capabilities that aren't yet generally available for this feature. Preview features are provided without a service-level agreement and aren't recommended for production workloads. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
\ No newline at end of file

@@ -9,4 +9,4 @@ ms.date: 04/16/2026
 ---
 
 > [!NOTE]
-> Some agentic retrieval features are generally available in the 2026-04-01 REST API version. However, this article uses the 2025-11-01-preview to demonstrate the full feature set, including features that remain in preview. Preview features are provided without a service-level agreement and aren't recommended for production workloads. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
\ No newline at end of file
+> Some agentic retrieval features are generally available in the 2026-04-01 REST API version. However, this article uses the latest preview REST API version to demonstrate the full feature set, including features that remain in preview. Preview features are provided without a service-level agreement and aren't recommended for production workloads. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
\ No newline at end of file