Currently, OneLake Security Roles must be configured individually within each Lakehouse. For organizations managing multiple Lakehouses based on data domains, this results in significant manual effort and duplication. Additionally, maintaining both Active Directory (AD) groups and separate OneLake Security Roles adds complexity and increases the risk of misalignment. ... View more

Metadata refresh failure in the Lakehouse SQL catalog due to Error "exceeding the database request limit". This resulted in SQL query failures linked to the DataflowsStagingLakehouse SQL Endpoint, which is not visible in the Fabric UI.     Customer is looking for Lakehouse SQL Endpoint to be visible in Power BI service UI.        ... View more

Currently the ability to use time travel in directlake models is not available. I need to be able to connect to the Base deltalake table folders and access cdc functionality to use version as of functionality to return time travel data as fast as possible on the fly. This is currently not supported.  ... View more

This is purely for aesthetic and usability reasons.   Now that a default semantic model is no longer generated when creating a new Lakehouse, could we consider streamlining the user experience by merging the Lakehouse and its SQL analytics endpoint into a single item? At the moment, having them listed separately feels a bit redundant and visually inconsistent. Consolidating them would make the interface cleaner and more intuitive.       ... View more

Description: Currently, Fabric Pipelines connect to native Fabric Lakehouses and Warehouses using user-bound tokens that expire approximately every 90 days. When these tokens expire, pipelines that invoke Warehouse or Lakehouse activities fail with authentication errors. The only workaround today is to manually open and re-save each pipeline, which regenerates the token. This approach becomes impractical and error-prone as the number of pipelines and workspaces grows across enterprise environments. Impact: Pipelines fail unpredictably in production after token expiry. Requires manual intervention across dozens or hundreds of pipelines. Causes disruption to scheduled ETL/ELT workflows. Inconsistent behavior compared to external connectors, which already support Workspace Identity. Typical Error Message: ErrorCode=UserAuthFailedToGetToken Message=Failed to get User Auth access token. AADSTS700003: Device object was not found in the tenant directory. This occurs after token expiration and causes pipelines to fail until re-saved. Proposed Enhancement: Add support for Workspace Identity Authentication for native Fabric Lakehouse and Warehouse connections in Pipelines. This would allow Fabric pipelines to: Authenticate using the workspace’s managed identity (non-user-dependent). Automatically renew tokens without user re-login. Align authentication behavior with Dataflows Gen2, Notebooks, and other Fabric connectors that already support Workspace Identity. Business Justification: Enterprise tenants typically operate multiple Fabric workspaces and dozens of pipelines per domain. Removing token dependencies will: Ensure reliable, unattended execution of production data pipelines. Eliminate recurring manual maintenance. Improve operational scalability and governance consistency. ... View more

Because of the Proxy authenication issue (currently Onelake explorer does NOT support proxy autheniciation via Kerberos/ NTLM), it is not possible to use Onelake within company network environment, in where the Proxy is used for accessing Internet.   And i believe many many Corp.s have this setup, So if this idea could be realized, it will be benefit lots of Fabric users.   ... View more

Please can you make the feature available for sql scripts created in the sql end point of a lakehouse to be migrated to the next workspace using the cicd pipelines.   Please can you also have he metadata of the tables be stored in the git repository linked to the workspace ... View more

Problem: Currently, when a dataset is connected to a Lakehouse as a datasource in Power BI Fabric, it defaults to a cloud connection mapped to SSO. In embedded mode, reports built on these datasets fail due to a lack of identity, as they do not inherit authentication from the service principal. To resolve this, users must manually adjust the datasource settings via the Power BI service https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-fixed-identity   Proposed Solution: Introduce a new REST API or extend the current API functionality to allow programmatic setting (or re-setting) of the connection to the service principal, including updating datasources. Benefits: Automates the process, reducing manual intervention Minimizes downtime for embedded reports Enhances developer experience and deployment efficiency Ensures consistency in authentication settings across different environments Impact: This feature will significantly improve the workflow for organizations embedding Power BI reports using service principals, ensuring seamless and automated datasource authentication. ... View more

There should be a mechanism in place to recover deleted items in fabric. I would think having a recycle bin of sorts would be great to have for items and/or delta files so its easy to recover these items on delete. Recently We found that its not easy to recover a deleted lakehouse or warehouse, while its very easy to delete items with levels as low as a member to workspace. This can cause greater issues as people are co-working in workspaces.  ... View more

With the rising adoption of Multi-Factor Authentication (MFA) across our organization and industry best practices, we are seeking a more robust and streamlined authentication method for connecting Power BI to Snowflake. Currently, Power BI primarily relies on username/password or OAuth 2.0 via Microsoft Entra ID. While these methods are functional, they can become cumbersome and less secure in MFA-enabled environments. We propose the implementation of RSA key pair authentication for Snowflake connections within Power BI. ... View more

In the OneLake File Explorer, you need to use the new security roles introduced for Lakehouse management (which allow reading and writing file contents) to grant access, so that users can read and write files without conflicts with their workspace roles. For example, if User-A has a Viewer role in the workspace, you can assign them a new Lakehouse-managed security role (with read/write permissions to file contents). This allows User-A to open files directly from OneLake File Explorer, modify them locally, and save changes that automatically sync back to the Lakehouse. ... View more

Make it possible to see storage consumption at Item level in the Capacity Metrics App.   At the moment, we can only see storage consumption at Workspace level, and this makes it difficult to pinpoint exactly which items (lakehouses, warehouses) consume most storage in our workspace.   Displaying the storage size (gigabytes) at Item level would increase the usability of the Storage page in Capacity Metrics App. ... View more

I would like to be able to grant write permissions on a directory-by-directory basis to individual users or target groups in OneLake's "Manage OneLake Data Access."   Currently, "Manage OneLake Data Access" only has settings for "Read" and "ReadAll."   The roles that are automatically granted write permissions are the "Workspace Admin Role," "Member Role," and "Contributor Role." However, as the above are write permissions for the entire lake house, please add a function to grant write permissions on a directory-by-directory basis. ... View more

We need insights into the storage consumption of active files and soft deleted files.   The Capacity Metrics App's Storage page should have the ability to show the storage size of soft deleted files and the storage size of active files. And the total.   Today, it is not possible to differentiate between storage size of soft deleted files and active files in the Capacity Metrics App. ... View more

Idea: We are preparing to implement Microsoft Fabric in our organization and identified a need for more granular control over item creation within workspaces. Currently, any user who can create items has access to all Fabric item types, which makes it difficult to enforce separation of responsibilities. We propose adding functionality to restrict item creation by type, so administrators can configure which roles (or user groups) are authorized to create certain Fabric items. For example: Data Engineers – allowed to create Get Data, Prepare Data, and Store Data items. Data Scientists – allowed to create Analyze Data, Train Data, Track Data, and Visualize Data items. Report Developers – allowed to create only Visualize Data items. Additionally, in our environment, Data Science (DS) and Data Analytics (DA) users must not be able to add third-party data sources or external data stores into OneLake. While this seems possible through notebooks, we need the ability to restrict it explicitly. In particular, Dataflows and Data Pipelines should be blockable for these users. Why this matters: Enforces proper data governance. Prevents accidental or unauthorized creation of sensitive pipelines. Provides organizations with flexibility to align Fabric usage with their operating model. Enhances security and compliance in multi-team environments. ... View more

Currently, when creating a shortcut in Fabric to ADLS Gen2 containing delta table, it does not work properly when checkpointPolicy configuration is set to v2.  Reference: https://github.com/delta-io/delta/blob/master/PROTOCOL.md#v2-spec From time to time it fails with an error: Delta table 'X' with '_last_checkpoint' file references version 'X' but the associated checkpoint file is missing from the _delta_log directory. But it is not missing, it just stored in the sidecars folder which is a new addition in v2. ... View more

Is it possible to add more write access roles for specific folders in a lakehouse? It seems that the folder-based access currently only has the option of providing read access to other users. We are thinking of a data landing lakehouse for external users to upload data into specific folders they are provided access to. ... View more

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? ... View more