Skip to content

Commit 890772b

Browse files
committed
more updates
1 parent 90cb9bc commit 890772b

File tree

3 files changed

+17
-14
lines changed

3 files changed

+17
-14
lines changed

articles/search/retrieval-augmented-generation-overview.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -28,12 +28,14 @@ The decision about which information retrieval system to use is critical because
2828

2929
+ Integration with embedding models for indexing, and chat models or language understanding models for retrieval.
3030

31-
Azure AI Search is a [proven solution for information retrieval](https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/README.md) in a RAG architecture. It provides indexing and query capabilities, with the infrastructure and security of the Azure cloud. Through code and other components, you can design a comprehensive RAG solution that includes all of the elements for generative AI over your proprietary content.
31+
Azure AI Search is a [proven solution for information retrieval](https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/README.md) in a RAG architecture. It provides indexing and query capabilities, with the infrastructure and security of the Azure cloud. Through code and other components, you can design a comprehensive RAG solution that includes all of the elements for generative AI over your proprietary content.
32+
33+
You can choose between two approaches for RAG workloads: agentic retrieval, or the original query architecture for classic RAG.
3234

3335
> [!NOTE]
3436
> New to copilot and RAG concepts? Watch [Vector search and state of the art retrieval for Generative AI apps](https://www.youtube.com/watch?v=lSzc1MJktAo).
3537
36-
## Modern RAG with Agentic Retrieval
38+
## Option 1: Modern RAG with Agentic Retrieval
3739

3840
Azure AI Search now provides **agentic retrieval**, a specialized pipeline designed specifically for RAG patterns. This approach uses large language models to intelligently break down complex user queries into focused subqueries, executes them in parallel, and returns structured responses optimized for chat completion models.
3941

@@ -49,7 +51,7 @@ You need new objects for this pipeline: one or more knowledge sources, a knowled
4951

5052
For new RAG implementations, we recommend starting with [agentic retrieval](agentic-retrieval-overview.md). For existing solutions, consider migrating to take advantage of improved accuracy and context understanding.
5153

52-
## Classic RAG pattern for Azure AI Search
54+
## Option 2: Classic RAG pattern for Azure AI Search
5355

5456
A RAG solution can be implemented on Azure AI Search using the original query execution environment. This approach is faster and simpler with fewer components, and depending on your application requirements it can be the best choice. There's no LLM query planning or LLM integration in the query pipeline. Your application sends a single query request to Azure AI Search, the search engine executes the query and returns search results. There's no query execution details in the response, and citations are built into the response only if you have fields in your index that provide a parent document name or page.
5557

@@ -79,14 +81,6 @@ The information retrieval system provides the searchable index, query logic, and
7981

8082
The LLM receives the original prompt, plus the results from Azure AI Search. The LLM analyzes the results and formulates a response. If the LLM is ChatGPT, the user interaction might consist of multiple conversation turns. An Azure solution most likely uses Azure OpenAI, but there's no hard dependency on this specific service.
8183

82-
## Choosing between agentic retrieval and classic RAG
83-
84-
Try a few quickstarts using your own data to understand the development effort and compare outcomes:
85-
86-
+ [Quickstart: Agentic search](search-get-started-agentic-retrieval.md)
87-
88-
+ [Quickstart: Classic RAG using grounding data from Azure AI Seach](search-get-started-rag.md)
89-
9084
## Searchable content in Azure AI Search
9185

9286
In Azure AI Search, all searchable content is stored in a search index that's hosted on your search service. A search index is designed for fast queries with millisecond response times, so its internal data structures exist to support that objective. To that end, a search index stores *indexed content*, and not whole content files like entire PDFs or images. Internally, the data structures include inverted indexes of [tokenized text](https://lucene.apache.org/core/7_5_0/test-framework/org/apache/lucene/analysis/Token.html), vector indexes for embeddings, and unaltered plain text for cases where verbatim matching is required (for example, in filters, fuzzy search, regular expression queries).
@@ -233,6 +227,12 @@ We recommend the [Azure OpenAI demo](https://github.com/Azure-Samples/azure-sear
233227

234228
There are many ways to get started, including code-first solutions and demos.
235229

230+
For help with choosing between agentic retrieval and classic RAG, try a few quickstarts using your own data to understand the development effort and compare outcomes:
231+
232+
+ [Quickstart: Agentic search](search-get-started-agentic-retrieval.md)
233+
234+
+ [Quickstart: Classic RAG using grounding data from Azure AI Seach](search-get-started-rag.md)
235+
236236
### [**Docs**](#tab/docs)
237237

238238
+ [Try this agentic retrieval quickstart](search-get-started-rag.md) to walk through the new and recommended approach for RAG.

articles/search/search-get-started-rag.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,17 @@ ms.service: azure-ai-search
88
ms.custom:
99
- ignite-2024
1010
ms.topic: quickstart
11-
ms.date: 07/09/2025
11+
ms.date: 10/15/2025
1212
zone_pivot_groups: programming-languages-ai-search-rag-qs
1313
---
1414

1515
# Quickstart: Classic generative search (RAG) using grounding data from Azure AI Search
1616

1717
In this quickstart, you send queries to a chat completion model for a conversational search experience over your indexed content on Azure AI Search. After setting up Azure OpenAI and Azure AI Search resources in the Azure portal, you run code to call the APIs.
1818

19+
> [!NOTE]
20+
> We now recommend [agentic retrieval](search-get-started-agentic-retrieval.md) for RAG workflows, but classic RAG is simpler. If it meets your application requirements, it's still a good choice.
21+
1922
::: zone pivot="csharp"
2023

2124
[!INCLUDE [.NET quickstart](includes/quickstarts/search-get-started-rag-dotnet.md)]

articles/search/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -152,9 +152,9 @@ items:
152152
href: tutorial-document-extraction-image-verbalization.md
153153
- name: Verbalize images from a structured document layout
154154
href: tutorial-document-layout-image-verbalization.md
155-
- name: RAG tutorials
155+
- name: Classic RAG tutorials
156156
items:
157-
- name: Build a RAG solution
157+
- name: Build a classic RAG solution
158158
href: tutorial-rag-build-solution.md
159159
- name: Choose models
160160
href: tutorial-rag-build-solution-models.md

0 commit comments

Comments
 (0)