Forum Discussion
Microsoft Fabric metadata in Microsoft Purview
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.
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.
