This tutorial series demonstrates a pattern for building RAG solutions on Azure AI Search. It explains the components that you need to build, enumerates the dependencies, and provides optimizations for maximizing relevance and minimizing costs.
Sample data is a collection of PDFs uploaded to Azure Storage. The content is from NASA's Earth free e-book.
Sample code can be found in this Python notebook, but we recommend using the articles in this series for context, insights, and for exploring alternative approaches.
Choose your models for embeddings and chat
Design an index for conversational search
Design an indexing pipeline that loads, chunks, embeds, and ingests searchable content
Retrieve searchable content using queries and a chat model
Maximize relevance
Minimize storage and costs
We omitted a few aspects of a RAG pattern to reduce complexity:
No management of chat history and context. Chat history is typically stored and managed separately from your grounding data, which means extra steps and code. This tutorial assumes atomic question and answers from the LLM and the default LLM experience.
No per-user user security over results (what we refer to as "security trimming"). For more information and resources, start with Security trimming and make sure to review the links at the end of the article.
This series covers the fundamentals of RAG solution development. Once you understand the basics, continue with accelerators and other code samples that provide more abstraction or are otherwise better suited for production environments and more complex workloads.
Why use Azure AI Search for RAG?
Chat models face constraints on the amount of data they can accept on a request. You should use Azure AI Search because the quality of content passed to an LLM can make or break a RAG solution.
To deliver the highest quality inputs to a chat model, Azure AI Search provides a best-in-class search engine with AI integration and comprehensive relevance tuning. The search engine supports vector similarity search (multiple algorithms), keyword search, fuzzy search, geospatial search, and filters. You can build hybrid query requests that include all of these components, and you can control how much each query contributes to the overall request.