Skip to content

Commit 679e526

Browse files
committed
refresh pass on rag article
1 parent 43cf241 commit 679e526

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: cognitive-search
1010
ms.custom:
1111
- ignite-2023
1212
ms.topic: conceptual
13-
ms.date: 08/15/2024
13+
ms.date: 09/03/2024
1414
---
1515

1616
# Retrieval Augmented Generation (RAG) in Azure AI Search
@@ -47,18 +47,18 @@ Curated approaches make it simple to get started, but for more control over the
4747
+ [JavaScript](https://aka.ms/azai/js)
4848
+ [Java](https://aka.ms/azai/java)
4949

50-
The remainder of this article explores how Azure AI Search fits into a custom RAG solution.
50+
If tools and templates don't satisfy your application requirements, you can build a custom RAG solution using Azure AI Search APIs. The remainder of this article explores how Azure AI Search fits into a custom RAG solution.
5151

5252
## Custom RAG pattern for Azure AI Search
5353

5454
A high-level summary of the pattern looks like this:
5555

5656
+ Start with a user question or request (prompt).
5757
+ Send it to Azure AI Search to find relevant information.
58-
+ Send the top ranked search results to the LLM.
58+
+ Return the top ranked search results to an LLM.
5959
+ Use the natural language understanding and reasoning capabilities of the LLM to generate a response to the initial prompt.
6060

61-
Azure AI Search provides inputs to the LLM prompt, but doesn't train the model. In RAG architecture, there's no extra training. The LLM is pretrained using public data, but it generates responses that are augmented by information from the retriever.
61+
Azure AI Search provides inputs to the LLM prompt, but doesn't train the model. In RAG architecture, there's no extra training. The LLM is pretrained using public data, but it generates responses that are augmented by information from the retriever, in this case, Azure AI Search.
6262

6363
RAG patterns that include Azure AI Search have the elements indicated in the following illustration.
6464

@@ -71,7 +71,7 @@ RAG patterns that include Azure AI Search have the elements indicated in the fol
7171

7272
The web app provides the user experience, providing the presentation, context, and user interaction. Questions or prompts from a user start here. Inputs pass through the integration layer, going first to information retrieval to get the search results, but also go to the LLM to set the context and intent.
7373

74-
The app server or orchestrator is the integration code that coordinates the handoffs between information retrieval and the LLM. One option is to use [LangChain](https://python.langchain.com/docs/get_started/introduction) to coordinate the workflow. LangChain [integrates with Azure AI Search](https://python.langchain.com/docs/integrations/retrievers/azure_ai_search/), making it easier to include Azure AI Search as a [retriever](https://python.langchain.com/docs/modules/data_connection/retrievers/) in your workflow. [Semantic Kernel](https://devblogs.microsoft.com/semantic-kernel/announcing-semantic-kernel-integration-with-azure-cognitive-search/) is another option.
74+
The app server or orchestrator is the integration code that coordinates the handoffs between information retrieval and the LLM. Common solutions include [LangChain](https://python.langchain.com/docs/get_started/introduction) to coordinate the workflow. LangChain [integrates with Azure AI Search](https://python.langchain.com/docs/integrations/retrievers/azure_ai_search/), making it easier to include Azure AI Search as a [retriever](https://python.langchain.com/docs/modules/data_connection/retrievers/) in your workflow. [LlamaIndex](https://github.com/run-llama/llama_index/tree/main/llama-index-integrations/vector_stores/llama-index-vector-stores-azureaisearch) and [Semantic Kernel](https://devblogs.microsoft.com/semantic-kernel/announcing-semantic-kernel-integration-with-azure-cognitive-search/) are other options.
7575

7676
The information retrieval system provides the searchable index, query logic, and the payload (query response). The search index can contain vectors or nonvector content. Although most samples and demos include vector fields, it's not a requirement. The query is executed using the existing search engine in Azure AI Search, which can handle keyword (or term) and vector queries. The index is created in advance, based on a schema you define, and loaded with your content that's sourced from files, databases, or storage.
7777

0 commit comments

Comments
 (0)