Fabric Warehouse is not extracting metadata like tables and its columns in Purview

[Naresh_inaganti]

Hello Team,
Good Evening..!

We noticed that the metadata in Datawarehouse is not extracting Schema(Tab) which contains Tables and its columns
We scanned Lakehouse using Service prinicple where metadata extraction is done as expected but it is not the same in Data Warehouse after the scan completes.

Are there any other options to get that metadata extracted under warehouse ?

Please guide us the best possible methods to handle this situation.

Regards,
Naresh Inaganti

[v-mdharahman]

Hi @Naresh_inaganti,

Thanks for reaching out to the Microsoft fabric community forum.

From what you've shared, it looks like you're running metadata scans on both the Lakehouse and the Data Warehouse using a service principal. While the Lakehouse scan successfully retrieves full metadata including schemas (tabs), tables, and columns, the same is not happening for the Data Warehouse. After the scan completes for the Warehouse, the schema (tab) level and its child metadata (like tables and columns) are missing.

This typically points to a difference in how metadata extraction works between the two storage layers or potentially a configuration gap specific to the Data Warehouse scan. Can you check few things to move forward:

* Ensure that the service principal used has read access at the workspace level and object-level permissions inside the Data Warehouse. Unlike Lakehouse, the Data Warehouse might require explicit permissions on each schema or object for metadata to be extracted.

* Double-check the configuration used for scanning the Data Warehouse. If you're using Microsoft Purview or Microsoft Fabric’s built-in scanning capability, confirm that the correct collection or workspace is targeted and that schema discovery is enabled (if applicable).

* Also confirm whether the scanning tool you’re using supports schema-level metadata extraction for the Microsoft Fabric Data Warehouse. Some scanning tools extract only table-level metadata unless explicitly configured otherwise.

If you've already validated permissions and configuration but still aren't getting schema-level metadata, I’d recommend raising a support request with Microsoft Fabric Support. They can verify if this is expected behavior or an issue specific to your environment.

Please refer below link on how to raise a contact support or support ticket.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

I would also take a moment to thank @burakkaragoz, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

[burakkaragoz]

Hi @Naresh_inaganti ,

Yeah, this is a known gap right now. When scanning Data Warehouses with Purview, it often misses out on schema-level metadata, especially the detailed info like tables and columns. The Lakehouse integration is a bit more mature in this sense.

A couple things you can try:

• Make sure you’re using the latest Purview connector for Fabric. Sometimes new features roll out quietly that improve metadata extraction.
• If possible, try granting Purview more granular permissions or running the scan as a user with higher-level access, not just a service principal. Sometimes column-level metadata needs extra permissions.
• As a workaround, some teams export warehouse metadata to files or views and let Purview scan those as external sources. Not perfect, but at least you’ll get something indexed.

Honestly, at the moment, there isn’t a full fix unless Microsoft updates the integration to support deeper scans for Fabric Data Warehouses. It’s worth keeping an eye on roadmap announcements for improvements here.

Hope this helps a bit, even if there’s no magic solution yet!

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.