Purview Data Map scanning Microsoft Fabric and no classifications applied or scan rule sets

Microsoft Purview cannot currently apply built-in or custom classifications (including sensitive information types) to metadata discovered from Microsoft Fabric workspace scans. While Purview can register Fabric workspaces and extract structural metadata (workspaces, Lakehouses, Warehouses, tables, columns, and limited lineage), classification rules are not executed against Fabric assets in the same way they are for supported sources such as Azure SQL, ADLS Gen2, or on-prem databases.

This results in classification gaps across a core enterprise analytics platform.
Why This Is a Significant Service Omission
1. Breaks the Core Value Proposition of Purview
2. Undermines Regulatory and Risk Management Controls
3. Creates an Inconsistent Governance Experience
4. Blocks Downstream Purview Capabilities
5. Forces Anti-Patterns and Workarounds

The lack of automated classification support for Microsoft Fabric workspace data represents a material service omission in Microsoft Purview, significantly limiting its effectiveness as a unified data governance platform and introducing avoidable compliance, operational, and assurance risks—particularly in regulated environments.

Are there plans to improve this and if so what are the timescales?