You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/search/retrieval-augmented-generation-overview.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,12 +28,14 @@ The decision about which information retrieval system to use is critical because
28
28
29
29
+ Integration with embedding models for indexing, and chat models or language understanding models for retrieval.
30
30
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.
32
34
33
35
> [!NOTE]
34
36
> 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).
35
37
36
-
## Modern RAG with Agentic Retrieval
38
+
## Option 1: Modern RAG with Agentic Retrieval
37
39
38
40
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.
39
41
@@ -49,7 +51,7 @@ You need new objects for this pipeline: one or more knowledge sources, a knowled
49
51
50
52
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.
51
53
52
-
## Classic RAG pattern for Azure AI Search
54
+
## Option 2: Classic RAG pattern for Azure AI Search
53
55
54
56
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.
55
57
@@ -79,14 +81,6 @@ The information retrieval system provides the searchable index, query logic, and
79
81
80
82
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.
81
83
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:
+[Quickstart: Classic RAG using grounding data from Azure AI Seach](search-get-started-rag.md)
89
-
90
84
## Searchable content in Azure AI Search
91
85
92
86
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
233
227
234
228
There are many ways to get started, including code-first solutions and demos.
235
229
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:
# Quickstart: Classic generative search (RAG) using grounding data from Azure AI Search
16
16
17
17
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.
18
18
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.
0 commit comments