@@ -7,7 +7,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: azure-ai-search
 ms.topic: how-to
-ms.date: 08/29/2025
+ms.date: 10/10/2025
 ---
 
 # Create a blob knowledge source
@@ -219,19 +219,7 @@ After the knowledge agent is configured, use the retrieve action to query the kn
 
 ## Delete a knowledge source
 
-If you no longer need the knowledge source, or if you need to rebuild it on the search service, use this request to delete the current object.
-
-```http
-# Delete agent
-DELETE {{search-url}}/knowledgeSources/{{ks-name}}?api-version=2025-08-01-preview
-api-key: {{api-key}}
-```
-
-> [!IMPORTANT]
-> Before you can delete a knowledge source, you must first update the knowledge agent to remove all references to the knowledge source.
->
-> Deleting a blob knowledge source also deletes the objects it created. The indexer, data source, skillset, and index are automatically deleted when the blob knowledge source is deleted.
->
+[!INCLUDE [Delete knowledge source](includes/how-tos/knowledge-source-delete-rest.md)]
 
 ## Learn more
 

@@ -7,7 +7,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: azure-ai-search
 ms.topic: how-to
-ms.date: 08/29/2025
+ms.date: 10/10/2025
 ---
 
 # Create a search index knowledge source
@@ -121,13 +121,7 @@ Within the knowledge agent, there are more properties to set on the knowledge so
 
 ## Delete a knowledge source
 
-If you no longer need the knowledge source, or if you need to rebuild it on the search service, use this request to delete the current object.
-
-```http
-# Delete agent
-DELETE {{search-url}}/knowledgeSources/{{ks-name}}?api-version=2025-08-01-preview
-api-key: {{api-key}}
-```
+[!INCLUDE [Delete knowledge source](includes/how-tos/knowledge-source-delete-rest.md)]
 
 ## Learn more
 

@@ -1,52 +1,71 @@
 ---
-title: Create a knowledge source
+title: What is a knowledge source
 titleSuffix: Azure AI Search
-description: Learn how to create a knowledge source for agentic retrieval workloads in Azure AI Search.
+description: Learn about the knowledge source object used for agentic retrieval workloads in Azure AI Search.
 manager: nitinme
 author: HeidiSteen
 ms.author: heidist
 ms.service: azure-ai-search
-ms.topic: how-to
-ms.date: 10/01/2025
+ms.topic: concept-article
+ms.date: 10/09/2025
 ---
 
-# Create a knowledge source
+# What is a knowledge source?
 
 [!INCLUDE [Feature preview](./includes/previews/preview-generic.md)]
 
 A knowledge source wraps a search index with extra properties for agentic retrieval. It's a required definition in a knowledge agent. We provide guidance on how to create specific knowledge sources, but generally, you can:
 
-+ Create multiple knowledge sources as top-level resources on your search service.
++ Create a knowledge source as a top-level resource on your search service. Each knowledge source points to exactly one index, and that index must [meet the criteria for agentic retrieval](agentic-retrieval-how-to-create-index.md).
 
-+ Reference one or more knowledge sources in a knowledge agent. In an agentic retrieval pipeline, it's possible to query against multiple knowledge sources in single request. Subqueries are generated for each knowledge source. Top results are returned in the retrieval response.
++ Reference one or more knowledge sources in a knowledge agent. In an agentic retrieval pipeline, it's possible to query against multiple knowledge sources in a single request. Subqueries are generated for each knowledge source. Top results are returned in the retrieval response.
 
-Make sure you have at least one knowledge source before creating a knowledge agent. The full specification of a knowledge source and a knowledge agent is in the [REST API reference](/rest/api/searchservice). 
++ Use a knowledge source definition to generate a full indexer pipeline (data source, skillset, indexer, and index) that works for agentic retrieval. Instead of creating multiple objects manually, information in the knowledge source is used to generate all objects, including a populated and searchable index.
 
-## Key points about a knowledge source
+Make sure you have at least one knowledge source before creating a knowledge agent. The full specification of a knowledge source and a knowledge agent is in the [preview REST API reference](/rest/api/searchservice/operation-groups?view=rest-searchservice-2025-08-01-preview&preserve-view=true).
 
-+ Creation path: first create a knowledge source, then create a knowledge agent. Deletion path: update or delete knowledge agents, delete knowledge sources last.
+## Working with a knowledge source
 
-+ A knowledge source, its index, and the knowledge agent must all exist on the same search service.
++ Creation path: first create a knowledge source, then create a knowledge agent. 
+
++ Deletion path: update or delete knowledge agents to remove references to a knowledge source, and then delete the knowledge source last.
 
-+ Each knowledge source points to exactly one index, and that index must [meet the criteria for agentic retrieval](agentic-retrieval-how-to-create-index.md).
++ A knowledge source, its index, and the knowledge agent must all exist on the same search service.
 
-+ For each knowledge source, the knowledge agent provides extra properties for query execution. [KnowledgeSourceReference](/rest/api/searchservice/knowledge-agents/create-or-update#knowledgesourcereference?view=rest-searchservice-2025-08-01-preview&preserve-view=true) properties affect query planning. [KnowledgeAgentOutputConfiguration](/rest/api/searchservice/knowledge-agents/create-or-update#knowledgeagentoutputconfiguration?view=rest-searchservice-2025-08-01-preview&preserve-view=true) properties affect query output.
++ For each knowledge source, the knowledge agent provides extra properties for query execution. [`"knowledgeSources"`](/rest/api/searchservice/knowledge-agents/create-or-update#knowledgesourcereference?view=rest-searchservice-2025-08-01-preview&preserve-view=true) properties affect query planning. [`"outputConfiguration"`](/rest/api/searchservice/knowledge-agents/create-or-update#knowledgeagentoutputconfiguration?view=rest-searchservice-2025-08-01-preview&preserve-view=true) properties affect query output.
 
 ## Supported knowledge sources
 
 Here are the knowledge sources you can create in this preview:
 
-+ [Search index knowledge source (an existing index)](agentic-knowledge-source-how-to-search-index.md)
-+ [Blob knowledge source](agentic-knowledge-source-how-to-blob.md)
++ [`"searchIndex"`](/rest/api/searchservice/knowledge-sources/create-or-update#searchindexknowledgesource?view=rest-searchservice-2025-08-01-preview&preserve-view=true) wraps an existing index
++ [`"azureBlob"`](/rest/api/searchservice/knowledge-sources/create-or-update#azureblobknowledgesource?view=rest-searchservice-2025-08-01-preview&preserve-view=true) generates an indexer pipeline that pulls from a blob container
 
-A platform-specific knowledge source like the blob knowledge source includes specifications for generating an entire indexing pipeline that provides all extraction, enrichment and transformations over blob content, and a viable index. You can modify the pipeline and rerun the indexer, but you can't rename the objects.
+A platform-specific knowledge source like the blob knowledge source includes specifications for generating an entire indexing pipeline that provides extraction, skillset processing, and a viable index. You can modify the pipeline and rerun the indexer, but you can't rename the objects.
 
 > [!NOTE]
-> `WebKnowledgeSource` (also referred to as `WebParameters` in REST APIs) isn't currently available in the 2025-08-01-preview.
+> `WebKnowledgeSource` (also referred to as `WebParameters` in REST APIs) isn't currently operational in the 2025-08-01-preview.
+
+## Creating knowledge sources
+
+You must have [**Search Service Contributor** permissions](search-security-rbac.md) to create objects on a search service.  You also need **Search Index Data Contributor** permissions to load an index if you're using a knowledge source that creates an indexer pipeline. Alternatively, you can [use an API admin key](search-security-api-keys.md) instead of roles.
+
+You must use the REST API or an Azure SDK preview package to create a knowledge source. There's no portal support at this time. The following links provide instructions for creating a knowledge source:
+
++ [How to create a search index knowledge source (wraps an existing index)](agentic-knowledge-source-how-to-search-index.md)
++ [How to create a blob knowledge source (generates an indexer pipeline)](agentic-knowledge-source-how-to-blob.md)
+
+After the knowledge source is created, you can reference it in a knowledge agent.
+
+## Using knowledge sources
+
+Properties on the [*knowledge agent*](agentic-retrieval-how-to-create-knowledge-base.md) determine whether and how the knowledge source is used.
 
-## Control knowledge source usage
++ [`"knowledgeSources"`](/rest/api/searchservice/knowledge-agents/create-or-update#knowledgesourcereference?view=rest-searchservice-2025-08-01-preview&preserve-view=true) array specifies the knowledge sources available to the knowledge agent and informs the query logic.
 
-Properties on the knowledge agent determine whether and how the knowledge source is used. The [KnowledgeSourceReference](/rest/api/searchservice/knowledge-agents/create-or-update#knowledgesourcereference?view=rest-searchservice-2025-08-01-preview&preserve-view=true) array specifies the knowledge sources available to the knowledge agent.
++ [`"outputConfiguration"`](/rest/api/searchservice/knowledge-agents/create-or-update#knowledgeagentoutputconfiguration?view=rest-searchservice-2025-08-01-preview&preserve-view=true) properties affect query output.
+
+The knowledge agent uses the [retrieve action](agentic-retrieval-how-to-retrieve.md) to send queries to the index specified in the knowledge source.
 
 ### Use multiple knowledge sources simultaneously
 
@@ -57,7 +76,7 @@ When you have multiple knowledge sources, set the following properties to bias q
 
 Retrieval instructions are sent as a user-defined prompt to the large language model (LLM) used for query planning. This prompt is helpful when you have multiple knowledge sources and want to provide guidance on when to use each one. For example, if you have separate indexes for product information, job postings, and technical support, the retrieval instructions might say "use the jobs index only if the question is about a job application."
 
-The `alwaysQuerySource` property overrides `retrievalInstructions`. You should set `alwaysQuerySource` to false when providing retrieval instructions.
+The `alwaysQuerySource` property overrides `retrievalInstructions`. Set `alwaysQuerySource` to false when providing retrieval instructions.
 
 ### Attempt fast path processing
 
@@ -94,36 +113,3 @@ To achieve the fastest possible response times, follow these best practices:
    + Set `knowledgeSources.includeReferenceSourceData` to false if you don't need the verbatim content from the index. Omitting this information simplifies the response and makes it more readable.
 
 1. In the [retrieve action](agentic-retrieval-how-to-retrieve.md), provide a single message query that's fewer than 512 characters.
-
-## Delete a knowledge source
-
-Before you can delete a knowledge source, you must delete or update any knowledge agent that references it. The associated index is a standalone object in Azure AI Search and doesn't need to be deleted or updated in tandem with the knowledge source, but no references to the knowledge source can exist if you want to delete it.
-
-If you try to delete a knowledge source that's in use, the action fails and a list of affected knowledge agents is returned.
-
-1. Get the knowledge agent definition to confirm knowledge source references.
-
-    ```http
-    ### Get the knowledge agent
-    GET {{search-endpoint}}/agents/hotels-index-ka?api-version=2025-08-01-preview
-    api-key: {{api-key}}
-    Content-Type: application/json
-    ```
-
-1. Either update the knowledge agent by removing the knowledge source, or delete the knowledge agent. This example shows deletion.
-
-    ```http
-    ### Delete knowledge agent
-    DELETE {{search-endpoint}}/agents/hotels-index-ka?api-version=2025-08-01-preview
-    api-key: {{api-key}}
-    Content-Type: application/json
-    ```
-
-1. Delete the knowledge source.
-
-    ```http
-    ### Delete a knowledge source definition
-    GET {{search-endpoint}}/knowledgeSources/hotels-index-ks?api-version=2025-08-01-preview
-    api-key: {{api-key}}
-    Content-Type: application/json
-    ```

@@ -0,0 +1,89 @@
+---
+manager: nitinme
+author: heidisteen
+ms.author: heidist
+ms.service: azure-ai-search
+ms.topic: include
+ms.date: 10/10/2025
+---
+
+If you no longer need the knowledge source, or if you need to rebuild it on the search service, use this request to delete the current object.
+
+Before you can delete a knowledge source, you must delete any knowledge agent that references it, or remote the references in an update action. The associated index and any indexer pipeline objects created from the knowledge source are standalone objects and don't need to be deleted or updated in tandem with the knowledge source.
+
+If you try to delete a knowledge source that's in use, the action fails and a list of affected knowledge agents is returned.
+
+1. Start by getting a list of all knowledge agents. This request returns all knowledge agents on your search service.
+
+    ```http
+    ### Get the knowledge agent
+    GET {{search-endpoint}}/agents?api-version=2025-08-01-preview&$select=name
+    api-key: {{api-key}}
+    Content-Type: application/json
+    ```
+
+   An example response might look like the following:
+
+   ```json
+    {
+        "@odata.context": "https://my-demo-search-service.search.windows.net/$metadata#agents(name)",
+        "value": [
+        {
+            "name": "earth-blob-ka"
+        },
+        {
+            "name": "hotels-sample-ka"
+        }
+        ]
+    }
+   ```
+
+1. Get the individual knowledge agent definition to check for knowledge source references.
+
+    ```http
+    GET {{search-endpoint}}/agents/hotels-sample-ka?api-version=2025-08-01-preview
+    api-key: {{api-key}}
+    Content-Type: application/json
+    ```
+
+   An example response might look like the following:
+
+   ```json
+    {
+      "name": "hotels-sample-ka",
+      "description": null,
+      "retrievalInstructions": null,
+      "knowledgeSources": [
+        {
+          "name": "hotels-sample-ks",
+          "alwaysQuerySource": false,
+          "includeReferences": true,
+          "includeReferenceSourceData": false,
+          "maxSubQueries": null,
+          "rerankerThreshold": null
+        }
+      ],
+      "models": [ trimmed for brevity ],
+      "outputConfiguration": { trimmed for brevity },
+      "requestLimits": { trimmed for brevity},
+      "encryptionKey": null
+    }
+   ```
+
+1. Either [update the knowledge agent](/rest/api/searchservice/knowledge-agents/create-or-update?view=rest-searchservice-2025-08-01-preview&preserve-view=true) by removing the knowledge source if you have multiple sources, or delete the knowledge agent. This example shows deletion.
+
+    ```http
+    ### Delete knowledge agent
+    DELETE {{search-endpoint}}/agents/hotels-sample-ka?api-version=2025-08-01-preview
+    api-key: {{api-key}}
+    Content-Type: application/json
+    ```
+
+1. Delete the knowledge source.
+
+    ```http
+    ### Delete a knowledge source definition
+    GET {{search-endpoint}}/knowledgeSources/hotels-sample-ks?api-version=2025-08-01-preview
+    api-key: {{api-key}}
+    Content-Type: application/json
+    ```