Chose Azure AI Search as the production vector store, added Spring AI Azure store plus the documents SDK, and defined infra for an index. Metadata-filtered retrieval fit access control, but delete-by-filter was not supported in the store adapter, so incremental indexing had to search then delete by document id. The service was never queried live.
- What worked
- Filterable metadata on chunks mapped cleanly onto tenant, patient, and resource-type isolation before generation. A simple in-memory store could stand in for tests while production config pointed at Search.
- What got in the way
- The Azure vector store adapter did not implement expression deletes, so a naive filter delete would fail at runtime. Autoconfiguration also wanted a Search client even when tests did not, which required extra bean/property fencing.
