Update search-indexer-howto-access-private.md

Author: HeidiSteen

articles/search/search-indexer-howto-access-private.md

@@ -10,7 +10,7 @@ ms.service: azure-ai-search
 ms.custom:
   - ignite-2024
 ms.topic: how-to
-ms.date: 05/28/2025
+ms.date: 07/01/2025
 ---
 
 # Make outbound connections through a shared private link
@@ -28,14 +28,15 @@ Shared private link is a premium feature that's billed by usage. When you set up
 
 Azure AI Search makes outbound calls to other Azure resources in the following scenarios:
 
++ Knowledge agent connections to Azure OpenAI for agentic retrieval workflows
 + Indexer or query connections to Azure OpenAI, Azure AI Vision, or the Azure AI Foundry model catalog for vectorization
 + Indexer connections to supported data sources
 + Indexer (skillset) connections to Azure Storage for caching enrichments, debug session sate, or writing to a knowledge store
 + Indexer (skillset) connections to Azure AI services for billing purposes
 + Encryption key requests to Azure Key Vault
 + Custom skill requests to Azure Functions or similar resource
 
-Shared private links only work for Azure-to-Azure connections. If you're connecting to OpenAI or another external model, the connection must be over the public internet.
+Shared private links only work for Azure-to-Azure connections. If you're connecting to OpenAI or another external model provider, the connection must be over the public internet.
 
 Shared private links are for operations and data accessed through a [private endpoint](/azure/private-link/private-endpoint-overview) for Azure resources or clients that run in an Azure virtual network.
 
@@ -51,7 +52,7 @@ Once you set up the private link, it's used automatically whenever the search se
 
 There are two scenarios for using [Azure Private Link](/azure/private-link/private-link-overview) and Azure AI Search together.
 
-+ Scenario one: create a shared private link when an *outbound* (indexer) connection to Azure requires a private connection.
++ Scenario one: create a shared private link when an *outbound* (indexer or knowledge agent) connection to Azure requires a private connection.
 
 + Scenario two: [configure search for a private *inbound* connection](service-create-private-endpoint.md) from clients that run in a virtual network.
 
@@ -80,6 +81,7 @@ When evaluating shared private links for your scenario, remember these constrain
   | Indexers without skillsets | Basic and higher | None | None |
   | Skillsets with embedding skills ([integrated vectorization](vector-search-integrated-vectorization.md)) | Basic and higher | [High capacity regions](search-limits-quotas-capacity.md#partition-storage-gb) | [After April 3, 2024](search-how-to-upgrade.md#check-your-service-creation-or-upgrade-date) |
   | Skillsets using other [built-in](cognitive-search-predefined-skills.md) or custom skills | Standard 1 (S1) and higher | None | [After April 3, 2024](search-how-to-upgrade.md#check-your-service-creation-or-upgrade-date) |
+  | Knowledge agents calling Azure OpenAI for query planning or passing search results | Basic and higher | None | None |
 
 + Permissions on both Azure AI Search and the Azure resource: