Multi-Tenant Isolation

1. What exactly is Multi-Tenant Isolation?

Your support chatbot serves many different companies from one shared search index in Azure AI Search, with every company's help articles tagged by a company ID field. A customer of one company asks a question.

The search query never actually filters on that company ID field. Azure AI Search returns the closest matching passages across every company's articles, not just this customer's own company, and the chatbot answers using a different company's policy instead of the one that actually applies here.

The data needed to keep companies separate is already sitting on every record. Nothing in the query actually uses it. That's exactly what multi-tenant isolation fixes.

2. How would you fix it in Azure?

Multi-tenant isolation is just a filter you're missing: add one on the company ID field to every search query, set from the current conversation's own company, not from anything in the customer's message. Azure AI Search then only returns passages tagged with that one company, no matter how closely another company's wording matches.

Use: Azure AI Search (filter parameter)

One shared index is fine. One shared search across all of it, with nothing scoping it down, is not.

3. How can you visualize it in everyday terms?

A shared filing cabinet has a drawer for each company, each folder labeled with its company's name.

A clerk who searches by keyword across every drawer at once, ignoring the labels, can hand a customer a folder that belongs to a different company entirely.

Check the label on the drawer before you open it, not search across all of them at once.