What to plan before building an Azure RAG system
A production RAG solution on Azure needs an overall design before the itself is built. The scope includes the full data , the Azure services required, security and rules, data ingestion, indexing, and the Azure the client must provision.
The data may come from several places, including databases, PDF, Word, Excel and CSV files, APIs, , and other systems. The main need is guidance on how to design an -scale RAG setup on Azure, not how to code the RAG app.
Key points
- The goal is to design a production RAG solution on Azure.
- The work is about , not building the app itself yet.
- The design must cover Azure services, security, , ingestion, and indexing.
- Data may come from databases, office files, APIs, , and other systems.
- The client needs an estimate of the Azure to provision.