Share via

Issue in Scanning Azure Databricks Unity Catalog

Sai Madhuri Rasamsetty 0 Reputation points
2025-01-17T15:57:21.3566667+00:00

Identified an issue with Azure DataBricks Unity Catalog. Unlike the standard Azure Databricks functionality, Unity Catalog does not support selecting specific tables for operations while scanning to Microsoft Purview. This Limitation will impact our workflows as we require granular control over table selection to manage our data more effectively.

Could you confirm if there is a workaround available or if there are plans to address this limitation in future updates? Appreciate your assistance in resolving this issue

Azure Data Catalog
Azure Data Catalog
An Azure service that serves as a system of registration and system of discovery for enterprise data assets.
110 questions
Microsoft Purview
Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
1,471 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Chandra Boorla 10,570 Reputation points Microsoft External Staff
    2025-01-17T20:27:43.8266667+00:00

    @Sai Madhuri Rasamsetty

    Greetings & Welcome to Microsoft Q&A forum! Thanks for posting your query!

    Thank you for bringing this to our attention. You're correct that currently, scanning Unity Catalog with Purview doesn't offer the same granular table selection as scanning regular Databricks workspaces. This can indeed impact workflows requiring precise control over scanned data.

    Identified Limitation

    Currently, when scanning Azure Databricks Unity Catalog with Microsoft Purview, you can choose to scan the entire Unity Catalog or scope the scan to a subset of catalogs, but not to specific tables. This limitation means that granular control over table selection during scans is not supported at this time.

    Workaround and Future Updates

    Unfortunately, there is no direct workaround available at this time for this specific limitation and we don't have any ETA on this. It is advisable to monitor updates from Azure Databricks, as they may address this issue in future releases. Keeping an eye on the release notes or announcements from Databricks can provide insights into any enhancements related to Unity Catalog.

    Appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.

    I hope this information helps. Please do let us know if you have any further queries.

    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.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.