Why Databricks Tables are searchable in Azure Purview but Not Schema

Question

Why Databricks Tables are searchable in Azure Purview but Not Schema

Priya Yadav 20

Hi Team,

We are scanning Azure Databricks (Unity Catalog) into Microsoft Purview.

All schemas are visible and open correctly except one specific schema.

For that schema:

It appears in the hierarchy under the metastore.

The child tables are visible and open correctly.

However, when clicking the schema itself, it shows:

"This item isn't available in the Data Catalog. To get more information about it, go to Contacts and reach out to the data owner."

User's image

Additional details:

I have Collection Admin, Data Curator, Data Source Admin, and Data Reader roles at the root collection level.

Other schemas in the same catalog open without issues when searching "Browse by Source Type"

This issue is happening only for one schema.

Has anyone faced this behavior with Unity Catalog scans?

Could this be a partial ingestion issue or metadata inconsistency?

Any guidance would be appreciated.

Thank you

Smaran Thoomu 33,920 Reputation points Microsoft External Staff Moderator

2026-03-02T06:24:37.5433333+00:00

@Priya Yadav Just checking in to see if the below answer provided is helped.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Priya Yadav 20 Reputation points

2026-03-02T08:56:50.2166667+00:00

Thank you for the explanation. When I re scan using unity catalog as data source , that brought the required schemas and tables in Purview. Thanks
Smaran Thoomu 33,920 Reputation points Microsoft External Staff Moderator

2026-03-09T06:12:49.4266667+00:00

@Priya Yadav Just checking in to see if the below answer helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

1 answer

Your answer

Smaran Thoomu 33,920 Reputation points Microsoft External Staff Moderator

2026-03-02T06:24:37.5433333+00:00

@Priya Yadav Just checking in to see if the below answer provided is helped.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Priya Yadav 20 Reputation points

2026-03-02T08:56:50.2166667+00:00

Thank you for the explanation. When I re scan using unity catalog as data source , that brought the required schemas and tables in Purview. Thanks
Smaran Thoomu 33,920 Reputation points Microsoft External Staff Moderator

2026-03-09T06:12:49.4266667+00:00

@Priya Yadav Just checking in to see if the below answer helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 1

Hi ,

Thanks for reaching out to Microsoft Q&A.

Yes, this usually points to a partial or inconsistent ingestion rather than a permissions issue.

In Purview, when scanning databricks UC, schemas and tables are indexed as separate assets. If tables open but the schema does not, it typically means the schema asset failed to register fully in the catalog index (often due to a transient scan error, lineage enrichment failure, or metadata API timeout during ingestion). Purview still shows the hierarchy node, but the catalog entry itself is missing or corrupted.

The practical fix is to re-run the scan for that catalog (or only that schema if scoped scanning is enabled) and verify the scan run details for warnings. If it persists, delete that schema asset from Purview (if visible in management view) and rescan to force clean ingestion.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

Share via

Why Databricks Tables are searchable in Azure Purview but Not Schema

1 answer

Your answer