Azure AI Search
Description
Azure AI Search can be used as the backing implementation for Flex vector similarity search. Your application code should depend on IFlexVectorStore, while the provider implementation handles index access and SDK wiring.
Important concepts
IFlexVectorStoreis the contract: app code performs upserts and similarity search through the shared interface, not Azure SDK types.Upsert + search: generated handlers typically call
UpsertAsync(id, vector, metadata, content), and generated queries callSearchAsync(queryVector, topK, filter, minScore).Collections: Azure AI Search also supports
IFlexVectorStoreWithCollectionsfor collection/index operations when needed.
Configuration in DI
Add the provider in your DI composition root (commonly in EndPoints/...CommonConfigs/OtherApplicationServicesConfig.cs or wherever you centralize registrations).
// using Sumeru.Flex; // IFlexVectorStore
public static class OtherApplicationServicesConfig
{
public static IServiceCollection AddOtherApplicationServices(
this IServiceCollection services,
IConfiguration configuration)
{
var section = configuration.GetSection("FlexBase:DataStores:Vector:AzureAISearch");
services.AddFlexAzureAISearchVectorStore(options =>
{
section.Bind(options);
});
// Flex auto-wires generated Queries/Handlers/Plugins that *use* IFlexVectorStore.
return services;
}
}appsettings.json
Configuration is read from FlexBase:DataStores:Vector:AzureAISearch.
Examples (template-based)
These examples mirror the generated Query and PostBus handler templates. You do not register these types manually—Flex discovers and wires generated Queries/Handlers/Plugins automatically.
Similarity search (Query)
Upsert a vector record (PostBus handler)
Azure AI Search considerations
Dimensionsmust match the embedding model you use.Ensure the index exists (or is provisioned) with a vector field compatible with your dimensions.
If you want Managed Identity auth, use
AddFlexAzureAISearchVectorStoreWithManagedIdentity(...)instead of providingApiKey.
Last updated