I understand that you're successfully scanning your Databricks Unity Catalog with Microsoft Purview and capturing lineage, but you're seeing Notebook IDs instead of Notebook Names, which makes it less meaningful for your use case.
Currently, Microsoft Purview captures lineage information from Azure Databricks Unity Catalog primarily using identifiers like Notebook IDs, as these are unique and directly reference the notebook within the Databricks environment. The Notebook Name, while more human-readable, isn't natively included in the lineage metadata that Purview pulls from Unity Catalog's system tables or APIs.
Why Notebook IDs Are Used
Notebook IDs are likely used because they are immutable and uniquely identify a notebook, even if its name changes over time. Names, on the other hand, can be edited by users, potentially leading to ambiguity in lineage tracking. However, I completely agree that for usability, seeing the Notebook Name would be far more intuitive.
I hope this information helps. Please do let us know if you have any further queries.
Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Thank you.