Fabric scan is ingesting Lakehouse schemas but not Warehouse schemas in my environment.

Chaz Abetz 40 Reputation points
2026-09-09T04:51:25.44+00:00

Hi All

I am trying to scan my Fabric environment into Purview but I have hit a snag, I want to be able to drill down into the my datawarehouse to extract the Tables and Views, but I am not sure how to do it

When I open the Lineage in the scanned warehouse I get

"Unable to map columns for this asset. The asset doesn't have a schema."

Yet, if I look in the actual Warehouse under Tables or Views, there are schemas there.

User's image

Lakehouse is fine, but Warehouse doesn't work.

Please guide me on what I need to configure to achieve this? If it is a limitation of Purview, can you please look into making this possible because, essentially it makes Purview useless for our Data Stewards otherwise.

TIA

Chaz

Azure Data Factory
Azure Data Factory

An Azure service for ingesting, preparing, and transforming data at scale.

0 comments
Answer accepted by question author
Vinodh247-1375 44,556 Reputation points Volunteer Moderator
2026-09-09T07:03:25.8533333+00:00

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:

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.

Was this answer helpful?

1 person found this answer helpful.
0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Chaz Abetz 40 Reputation points
    2026-09-09T23:07:45.9666667+00:00

    Thanks, this appears to be so, disappointing

    Is there another way to get the Data Warehouse objects into Purview that aren't Fabric related?

    Thanks

    Chaz

    Was this answer helpful?

    0 comments

Your answer

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