Documentation

Routing for Connectors and Indexing

Our Retrieval Suite needs to have the following mandatory routes to function well.

Database

Routes

  1. Suite → Database Server

Explanation

For productive scenarios, our Suite must have access to a SQL database, i.e., either Microsoft SQL, Postgres SQL or Oracle. The database is used to store configurations and the internal state.

Authentication

Routes

  1. Suite → Entra Id

  2. Browser → Entra Id

Explanation

The administration interface is a registered Entra Id application and users must be able to execute OIDC flows against Entra Id, when accessing the administration interface. This does not mean that the administration interface is exposed to the internet. But the browser, e.g. on the same VM, must be allowed to execute this flow. Also the Suite must be able to access https://graph.microsoft.com to verify the user identity and token.

Connector Routing

Routes

  1. Suite → Content Source

  2. Suite → Search Engine

Explanation

A connector must be able to reach the content source and search engine for crawling. For Microsoft Search, the search engine APIs are behind https://graph.microsoft.com

Content Processing

Routes

  1. (Optional) Suite → LLM

Explanation

If you like to use vector search, then the Suite must be able to access your Azure Open AI deployment or a local LLM to calculate an embedding.

Update Checks

Not mandatory is the following route.

Route

  1. Suite → https://www.rheininsights.com

Explanation

Our Suite performs update checks every once in a while Update Check . The API endpoint is part of our public website.