![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 81%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECA%3C/text%3E%3C/svg%3E)
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
Based on the current Purview documentation, this appears to be a product limitation rather than a configuration issue.
When Microsoft Purview scans a Fabric tenant, Warehouse assets are discovered at the item level, but Warehouse tables, views, schemas, and columns are not currently exposed as separate scanned assets. In contrast, Lakehouse tables and files support sub-item metadata scanning, which is why you can browse schema details for Lakehouse content but not for Warehouse content. [learn.microsoft.com], [learn.microsoft.com]
As a result, the message:
"Unable to map columns for this asset. The asset doesn't have a schema."
is consistent with the current Fabric-Purview integration when viewing a Warehouse asset. The Warehouse may contain schemas, tables, and views within Fabric, but those objects are not currently surfaced in Purview's Data Map in the same way that Lakehouse tables are. [learn.microsoft.com], [learn.microsoft.com]
The key distinction is:
- Lakehouse -> item-level metadata + table/file-level metadata (preview) [learn.microsoft.com], [learn.microsoft.com]
- Warehouse -> item-level metadata and lineage only [learn.microsoft.com], [learn.microsoft.com]
Therefore, if your Fabric scan is successfully discovering the Warehouse asset itself, I would not expect additional permissions or scan settings to make Warehouse table and view schemas appear in Purview today.
For organisations that require steward-level discovery of Warehouse tables, columns, and column-level lineage, this capability would need to be added to the Fabric-Purview integration. At present, the documented support for Fabric Warehouse scanning does not include Warehouse object-level metadata extraction. [learn.microsoft.com], [learn.microsoft.com]
Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.