Lineage Limitation on Wide Power BI Semantic Models & Built-in Classification Rule Sets
Hello everyone, I’m evaluating the new Microsoft Purview Governance Portal for our finance data governance needs. Previously with the Azure Purview classic version we had a couple of blocking issues such as it failed to scan wide semantic models. But now we're migrating to Fabric and we'd like to try the new Microsoft Purview Governance Portal. I’d appreciate any insights or confirmation from the product team or the community. Lineage Limitation on Wide Power BI Semantic Models Background: When we first ran the Purview Data Map Scanner against our finance semantic model, it failed once the total column count across all tables exceeded roughly 500 columns. In our case, a single SAP table alone has about 450 columns—so the scan wouldn’t complete, and we couldn’t capture any lineage. Questions: Has Purview removed or raised any “hidden” column-count limits for Power BI semantic models? Is there any official documentation on maximum supported column counts (e.g. 200, 500, or otherwise)? Are there recommended workarounds for very wide models—such as splitting into sub-datasets, using incremental scans, etc. to get full lineage? 2. Built-in Classification Rule Sets Background: Purview ships with a set of Microsoft-provided “Sensitive Information Types” that appear in every scan rule set. In many of our scans these defaults aren’t needed, and they clutter the results. Questions: Can we delete or permanently disable the built-in classification rules? If not, what’s the best way to ensure they’re not applied during a full scan? Are there any APIs or PowerShell commands that let us automate the exclusion of Microsoft’s defaults from our scan rule sets? Thank you in advance for any pointers, documentation links, or best-practice advice!
Purview API: When can a DataSet have many attachedSchema?
In the definition of a DataSet, there is a relationshipDef for attachedSchema that supports more than one schema. In what scenario would there be more than one attached schema for a single data set? I am trying to extract the schema for an azure_datalake_gen2_resource_set based on a delta table. I have been just using the first attachedSchema in the returned list, but am wondering if that is safe to do. Definition of the relationship: { "name": "attachedSchema", "typeName": "array<schema>", "isOptional": true, "cardinality": "SET", "valuesMinCount": -1, "valuesMaxCount": -1, "isUnique": false, "isIndexable": false, "includeInNotification": false, "relationshipTypeName": "dataset_attached_schemas", "isLegacyAttribute": false }` Example of what is returned from the purview API (when could there be more than one entry in the "attachedSchema" list?): { "entity": { "typeName": "azure_datalake_gen2_resource_set", "relationshipAttributes": { "attachedSchema": [ { "guid": "guid", "typeName": "parquet_schema", "entityStatus": "ACTIVE", "displayText": "parquet_schema", "relationshipType": "dataset_attached_schemas", "relationshipGuid": "relid", "relationshipStatus": "ACTIVE", "relationshipAttributes": { "typeName": "dataset_attached_schemas" } } ] } } }