Azure AI Search makes OneLake catalog integration generally available for knowledge sources, so customers can register a OneLake item once and reuse it across multiple knowledge sources and agents. The integration honors existing OneLake item-level permissions, sensitivity labels, and lineage, so when a Fabric admin restricts access in OneLake the change flows through to every dependent agent on the next query. Developers pick a catalog entry instead of pasting a path, and the knowledge source picks up schema metadata, freshness signals, and item ownership without extra configuration. Teams already organizing data in OneLake can extend that catalog to Foundry agents and search workloads with no duplicate registration. The integration is available in all regions where Azure AI Search and OneLake operate together.
Learn more.