Forum Discussion
Fabric + Purview (Data Classification)
Hi @fabricpribeiro ,
Thanks for reaching out to the Microsoft Fabric Community forum.
At the moment, Purview’s Data Map scans for Microsoft Fabric do not yet perform content-based classification during the scan the way they do for some other sources like SQL or Databricks. Because of this limitation, the built-in Sensitive Information Types (SITs) and trainable classifiers are not automatically applied to Fabric assets during the metadata extraction phase.In practice, most organizations handle this in one of two ways: either they classify the data at the source system (for example in SQL or ADLS) where Purview scanning supports automatic classification, and then propagate that governance metadata into Fabric, or they apply classifications and sensitivity labels directly at the Fabric item level using Microsoft Purview Information Protection policies after the assets are discovered. Since Fabric scanning currently prioritizes metadata and lineage, classification often becomes a governance workflow step rather than an automatic scan outcome.
So for now, if classification based on SITs is required, it typically needs to happen upstream or through labeling policies, rather than being generated automatically during the Fabric metadata extraction process in Purview.
I hope this information helps. Please do let us know if you have any further queries.
Thank you
Hello, thank a lot for your replies. In this case I am speaking about classification during extraction. Sensitivty labels is another step. What I need to understand is how people are classififying based on the fact that Purview, for the time being, does not allow it for Fabric (as opposite to other sources like databricks or SQL)
Hi @fabricpribeiro ,
Thanks for reaching out to the Microsoft Fabric Community forum.
At the moment, Purview’s Data Map scans for Microsoft Fabric do not yet perform content-based classification during the scan the way they do for some other sources like SQL or Databricks. Because of this limitation, the built-in Sensitive Information Types (SITs) and trainable classifiers are not automatically applied to Fabric assets during the metadata extraction phase.
In practice, most organizations handle this in one of two ways: either they classify the data at the source system (for example in SQL or ADLS) where Purview scanning supports automatic classification, and then propagate that governance metadata into Fabric, or they apply classifications and sensitivity labels directly at the Fabric item level using Microsoft Purview Information Protection policies after the assets are discovered. Since Fabric scanning currently prioritizes metadata and lineage, classification often becomes a governance workflow step rather than an automatic scan outcome.
So for now, if classification based on SITs is required, it typically needs to happen upstream or through labeling policies, rather than being generated automatically during the Fabric metadata extraction process in Purview.
I hope this information helps. Please do let us know if you have any further queries.
Thank you