Ability to delete system restore points in the data warehouse
Since the restore points count towards consumed (and billable) storage: "The creation of both system-created and user-defined restore points consume storage. The storage cost of restore points in OneLake includes the data files stored in parquet format. There are no storage charges incurred during the process of restore." we would like to be able to delete restore points. The current reasoning behind this option not being available is to meet the SLAs. I don't see it as valid reason as by deleting a restore point we acknowledge that meeting the recovery SLA is affected. We would like to be able to choose between paying for storage or having ability to restore a state from the past.
Potential Fabric Runtime 2.0 Issue - ANALYZE TABLE Fails for Fully Qualified Table Names
We have identified a potential issue in Microsoft Fabric Runtime 2.0 related to the ANALYZE TABLE ... COMPUTE STATISTICS FOR ALL COLUMNS command when used with schema-qualified Delta table names. Environment Microsoft Fabric Fabric Runtime 2.0 Delta Tables Schema-enabled Lakehouse Issue Details The table exists and is accessible through Spark SQL commands such as: DESCRIBE DETAIL schema_wrk.stg_table; This command executes successfully. However, when running: ANALYZE TABLE schema_wrk.stg_table COMPUTE STATISTICS FOR ALL COLUMNS; the command fails with: [TABLE_OR_VIEW_NOT_FOUND] The table or view 'stg_table' cannot be found. The stack trace references: UnresolvedRelation [stg_table] This suggests the command is attempting to resolve only the table name rather than the fully qualified table name. Workaround The same command succeeds after explicitly setting the schema context: USE schema_wrk; ANALYZE TABLE stg_table COMPUTE STATISTICS FOR ALL COLUMNS; Expected Behaviour The following command should execute successfully without requiring a preceding USE statement: ANALYZE TABLE schema_wrk.stg_table COMPUTE STATISTICS FOR ALL COLUMNS; Actual Behaviour The command fails with TABLE_OR_VIEW_NOT_FOUND, despite: The table existing DESCRIBE DETAIL working successfully No permission issues being present Observations Issue is reproducible across multiple tables. Fully qualified table names appear to work with DESCRIBE DETAIL. ANALYZE TABLE ... FOR ALL COLUMNS appears to internally resolve only the table name. Using USE <schema> is a valid workaround. This suggests a potential namespace resolution issue within the DeltaAnalyzeTableCommand path. fabriccommunity
Add Support for Higher Sensitivity Labels with Encryption in OneLake Shortcuts
Many Microsoft organisations use Sensitivity Labels with encryption to protect sensitive data and meet security, compliance, and governance requirements. While content protected with lower-sensitivity or non-encrypted labels can often be accessed by Fabric services, content protected by higher-sensitivity labels that apply encryption is not currently supported in all scenarios. This creates challenges for organisations that have adopted a "security first" approach and want to leverage Microsoft Fabric without compromising their data protection standards. Requested Enhancement Extend Fabric support to work with content protected by encrypted Sensitivity Labels, while fully respecting existing Microsoft Purview permissions, encryption policies, and user access controls. Fabric should be able to securely access and process protected content when the authenticated user or service identity already has the necessary rights to view the data. Benefits Better alignment between Fabric and Microsoft Purview Information Protection. Enables organisations to maintain strong security controls while adopting Fabric. Reduces the need for workarounds, duplicate data storage, or label downgrades. Supports enterprise compliance, governance, and zero-trust security strategies. Improves adoption of Fabric in highly regulated and security-conscious environments. As Sensitivity Labels with encryption become increasingly common across Microsoft 365, supporting these scenarios within Fabric would remove a significant barrier for many enterprise customers and help ensure that security and analytics capabilities can work together seamlessly.
Keep Fabric SQL Endpoint Up to Date
When data is updated in a Fabric Data Warehouse or Lakehouse, it's not always up to date immediately when querying the SQL Endpoint. The same thing happens in a Fabric SQL Database but this is even more noticeable - on the SQL Database object, the data is always up to date, but on the SQL Endpoint object of the same database, the data can lag. It is possible to refresh this as part of a pipeline by including the refresh SQL endpoint activity, but in my view the data should always be up to date through the endpoint as this can lead to discrepancies.
OneLake Catalog full-text and content search
Why is it not possible to search OneLake by item description or even content? So I was thinking about how a user can find a table if they don't know in which lakehouse it is located? Why can't you search the description to be able to only find a fabric item by its (sometimes "cryptic") name but by a description? Use-Case: I want to have a data mesh where people can make data sets available and share them easily. So how can someone find the lakehouse where financial data is shared (when the lakehouse is called FinRep) or where to find dim_account? Is this always a case for Purview? No way that we can make that available in Fabric directly?
Provide a Built-in Dashboard for OneLake Diagnostic Logs
Currently, OneLake Diagnostic Logs are available as JSON files, which provide valuable auditing and usage information. However, organizations must build their own ingestion, transformation, and reporting solutions before they can analyze the data effectively. It would be extremely useful if Microsoft provided out-of-the-box dashboards, reports, or analytics experiences for OneLake Diagnostic Logs. Examples include: ・ User activity trends ・ Most accessed items ・ Access frequency over time ・ Audit and governance insights ・ Workspace usage statistics ・ Storage and operational visibility A built-in monitoring experience or a standard Power BI report template would significantly reduce implementation effort and help customers gain value from OneLake diagnostics faster.Enable-Disable soft delete for Microsoft Fabric OneLake and provide storage breakdown with size
Hi Team, There are couple of suggestions based on last engagement. As default soft delete is 7 days but client is looking for enable disable so they have flexibility to control storage size and design solution accordingly as soft delete is not required for non-prod environments. Need breakdown of storage consumption at item levels within workspace capacity to drill down. Would be great help to enable the above abilities which seems like a gap at this stage. Thanks.
Create Shortcut to Tables in Power BI Semantic Models
Would it be possible to add an option to create Shortcuts in a Fabric Lakehouse to existing tables in Semantic Models? This would enable access to data which is only available through Calculated Columns in the Semantic Model to be reused in other processes.
