Forum Discussion
Fabric - MirroredAzureDatabricksCatalog DataSource/Catalog name
- 8 months ago
Hi Max_701 , Thank you for reaching out to the Microsoft Community Forum.
This is expected behavior. Currently, Microsoft Fabric does not expose source or connection metadata for Azure Databricks (Unity Catalog) mirrored items through any public REST API. Although these artifacts appear in /v1/workspaces/{workspaceId}/items as MirroredAzureDatabricksCatalog, they are modeled as a different artifact type than database mirrors and therefore do not appear in /mirroredDatabases. The getDefinition endpoint also does not return any definition parts for this item type, even after the long running operation completes successfully.
For lineage or governance scenarios, this means there is currently no supported API to retrieve Databricks workspace URL, catalog name or authentication details for these mirrored items. The only partial alternative is the Admin Workspace Info / Scanner API with lineage=true, which may surface high level upstream relationships but not detailed Databricks metadata.
If that is insufficient, the best thing to do for this to happen is submitting this clearly via Microsoft Fabric Ideas if you haven’t already, and get as many upvotes as possible. Microsoft monitors it for feature updates and enhancements, who knows, with enough upvotes this idea may be implemented as feature in the near future.
Hi Max_701 , Thank you for reaching out to the Microsoft Community Forum.
This is expected behavior. Currently, Microsoft Fabric does not expose source or connection metadata for Azure Databricks (Unity Catalog) mirrored items through any public REST API. Although these artifacts appear in /v1/workspaces/{workspaceId}/items as MirroredAzureDatabricksCatalog, they are modeled as a different artifact type than database mirrors and therefore do not appear in /mirroredDatabases. The getDefinition endpoint also does not return any definition parts for this item type, even after the long running operation completes successfully.
For lineage or governance scenarios, this means there is currently no supported API to retrieve Databricks workspace URL, catalog name or authentication details for these mirrored items. The only partial alternative is the Admin Workspace Info / Scanner API with lineage=true, which may surface high level upstream relationships but not detailed Databricks metadata.
If that is insufficient, the best thing to do for this to happen is submitting this clearly via Microsoft Fabric Ideas if you haven’t already, and get as many upvotes as possible. Microsoft monitors it for feature updates and enhancements, who knows, with enough upvotes this idea may be implemented as feature in the near future.
- Max_7018 months agoHelper II
Hi v-hashadapu - Thanks for confirming that this isn't possible(atleast for time being) 🙂