Hi @amirabedhiafi,

Unity Catalog volumes are a storage layer for files, so it’s normal that you can read JSON files from /Volumes/... with Python or SQL, but not have those same files show up as searchable document content in the workspace search experience. Databricks documents volume file access separately from workspace search and from working with files in Unity Catalog volumes.

The fact that the files are present and readable in the volume does not automatically mean their contents are indexed for search. JSON is absolutely supported as a file format in volumes and can be read programmatically, including with READ_FILES or standard Spark/Python workflows. But the built-in document-ingestion path for files in volumes, such as Knowledge Assistant, currently supports txt, pdf, md, ppt/pptx, and doc/docx for files-in-volume sources, which is why raw JSON files won’t behave like indexed documents there.

If the goal is to make the JSON content searchable, the pattern is to first load the JSON into a Delta table, for example, using read_files(..., format => 'json'), and then, if needed, build a Databricks AI Search index on that table. AI Search indexes are created from Delta tables rather than directly from raw files in a volume.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.