Forum Discussion

sashakorniakUK's avatar
sashakorniakUK
Brass Contributor
Jul 28, 2026

Microsoft Fabric metadata in Microsoft Purview

I’ve been mapping how Microsoft Fabric metadata is surfaced in Microsoft Purview through Data Map scanning, and I’ve created this visual to make the relationship easier to understand.

The diagram separates:

Documented mappings – such as Fabric items, Lakehouse tables, schema and item-level lineage.

Metadata known to be scanned, but where the exact Purview UI location needs confirmation.
? Areas still needing validation – particularly Lakehouse table/column descriptions and tags.

The principle I’m exploring is:

Microsoft Fabric → Purview Data Map Scan → Purview Data Asset → Purview governance enrichment

Importantly, a Fabric asset does not automatically become a Purview Data Product. It is first represented as a Data Asset, which can then be governed, enriched and associated with a Data Product.

I’d really appreciate feedback from anyone working hands-on with Microsoft Fabric and Microsoft Purview:

Does this mapping match what you are seeing in your environment?

I’m particularly interested in confirming:

Lakehouse table descriptions → Purview Asset Description?
Lakehouse column descriptions → Purview Schema → Column Description?
Lakehouse table/column tags → where exactly are these surfaced in Purview?

Corrections, screenshots or practical experience would be very welcome.

3 Replies

  • vincentiusindrayanto's avatar
    vincentiusindrayanto
    Copper Contributor
    Jul 29, 2026

    Thanks, Sasha. That explanation makes the process much clearer.

    It helps to understand that metadata synchronization depends on the Data Map scan schedule rather than happening in real time. The distinction between refreshing technical metadata and applying governance enrichment in Purview also makes a lot of sense.

    I'm looking forward to your findings on the Lakehouse table and column descriptions and tags. Practical validation like this is often more valuable than documentation alone, especially for features that are still evolving.

    Please keep us updated when you've completed your testing. I'm sure the results will be valuable for many people working with Microsoft Fabric and Microsoft Purview.

    Thanks again for taking the time to share your research and experience.

  • vincentiusindrayanto's avatar
    vincentiusindrayanto
    Copper Contributor
    Jul 28, 2026

    Thank you for sharing this detailed visualization.
    I'm currently learning Microsoft Fabric while preparing for the DP-700 certification, and your diagram helped me better understand the relationship between Fabric assets and Microsoft Purview governance.

    One question I have is about metadata synchronization. In production environments, is the metadata from Fabric typically reflected in Purview Data Map almost in real time, or should some delay be expected after changes are made?

    I'd also be interested to hear whether anyone has experience validating Lakehouse column descriptions and tags in Purview.

    Thanks again for sharing such a helpful resource.

    • sashakorniakUK's avatar
      sashakorniakUK
      Brass Contributor
      Jul 29, 2026

      Thanks Vincentius......glad the diagram helped.

       

      On metadata synchronisation, I would not describe Fabric → Purview Data Map as real-time, No. The metadata is surfaced through the Purview scanning process, so some delay should be expected between making a change in Fabric and seeing that change reflected in Purview. In practice, it depends on when the Data Map scan runs and completes. Microsoft also provides the scan history and individual scan-run status in Data Map so you can check when the source was last processed. - For me, my scan schedules are monthly or longer. 

      I believe scanning a Fabric tenant brings Fabric metadata and lineage into Purview. For most Fabric items this is at item level, while Lakehouse tables and files now support sub-item metadata scanning in preview.

      The Lakehouse column descriptions and tags are actually the area I am specifically testing at the moment. I want to separate what Microsoft documents as supported from what I can validate hands-on in the Purview UI after a scan.

       

      So my working model is:

      Fabric metadata change → Purview Data Map scan → refreshed technical metadata in the Purview Data Asset → governance enrichment in Purview.

      I’ll update the mapping as I confirm exactly where the Lakehouse table and column descriptions/tags surface.