I'm a Jetbrains user and I would like to use the SQL capabilities to connect Fabric Lakehouses and Warehouses inside their products ... 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

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

Currently service princaipals can't read and write to OneLake storage when Tenant Setting:  "Allow apps running outside of Fabric to access data via OneLake" is disabled   Enabling this setting to able access is enabling to much access to OneLake and a more restrcitive option is required. We need a similar setting to this one for OneLake storage access:  "Service principals can call Fabric public APIs"   eg "Service principals can access OneLake storage"   ... View more

I’m encountering a significant limitation when working with Power BI reports connected to Direct Lake semantic models (via Fabric Lakehouse). After migrating a dataset from an Import model to Direct Lake using ALM Toolkit, I can no longer replace the existing report in the Power BI Service by publishing from Power BI Desktop — even though the dataset is correctly updated and the report is connected to the same semantic model. Issue: Publishing from Desktop only replaces the dataset, not the report. The report visuals remain unchanged, even though the PBIX contains updated pages. This behavior is inconsistent with reports using Import or DirectQuery models, where publishing replaces both dataset and report. Manual editing in the Power BI Service is not a viable alternative due to limited functionality and the complexity of the report. Deleting and re-uploading the report breaks bookmarks, links, and Analyze in Excel connections, which is unacceptable in a production environment. Request: Please consider enabling one or more of the following: Allow full report replacement from Desktop for reports connected to Direct Lake models, with a warning if bookmarks or personal views exist. Provide a “safe replace” option that updates report visuals while preserving user bookmarks and links. Improve documentation and tooling around managing reports connected to shared semantic models (especially Direct Lake). Enable Deployment Pipelines or ALM Toolkit to update both dataset and report in a single operation for Direct Lake scenarios. This limitation is a major blocker for teams adopting Fabric and Direct Lake, and it undermines the benefits of centralized semantic models. Thank you for considering this feedback. ... 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

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’m aware that Lakehouse Git integration in Microsoft Fabric is currently in preview. However, I believe some critical support is missing that would significantly enhance the usability and maturity of this feature.   At the moment, Git integration does not support versioning or tracking of critical Lakehouse objects such as: Tables Views User-defined functions Stored procedures These objects are essential components of any data platform, and not being able to track their definitions in source control limits our ability to: Perform proper code reviews Roll back changes Maintain consistent environments across workspaces Collaborate effectively in larger teams Follow DevSecOps best practices Suggestion: Please extend Git integration in Fabric Lakehouses to include full support for these objects. For example, warehouse git integration supports all of those objects. This enhancement would greatly improve DevOps practices in Fabric and align with modern data engineering workflows. ... 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

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

Enabling automatic or scheduled mirroring of OneLake data across Azure regions would significantly enhance the platform's suitability for global enterprise scenarios. Key benefits of this capability include: Improved resilience through cross-region redundancy for disaster recovery and high availability Reduced latency by allowing data access from geographically closer regions Simplified data operations, eliminating the need for manual synchronization via Dataflow Gen2 or ADF pipelines Potential cost optimization, especially if replication avoids outbound data transfer charges Recommended configuration options: Selecting destination regions for mirroring Choosing between read-only and read/write replicas Defining sync intervals (e.g., near real-time, hourly, daily) This feature would align OneLake with enterprise expectations for multi-region data availability and performance. ... View more

To support business users, provide a GUI-based table creation feature that requires no coding. ... View more

In our setup, we work with multiple environments (Dev, Test, and Prod), each represented by its own workspace. To streamline deployment via pipelines, we keep Lakehouses and Notebooks named identical across workspaces.   Previously, when opening a Notebook, we could clearly see which Lakehouse it was connected to, including the workspace name it belonged to.  This made it easy to identify if a Notebook was referencing, for example the Dev Lakehousem while working in the Prod workspace. We could then simply disconnect and re-add the correct reference.   However, with recent UI changes, only the Lakehouse name is visible, not the workspace it is contained in. This creates confusion when multiple Lakehouses share the same name across different workspaces. Even when adding a new source, the explorer does not clearly show which reference is from which workspace. This makes it far too easy to mistakenly remove or connect the wrong Lakehouse especially in production environments.   This seemingly small UI regression significantly affects productivity and introduces potential risks during deployment or debugging. Please consider restoring the visibility of workspace names to Lakehouse references in Notebooks.   Before: Screenshot from google E.g: Workspace Dev -LakehouseA -LakehouseB .... Workspace Prod -LakehouseA -LakehouseB ....   After:   Only lakehouse name   We use same lakehouse name in each workspace   ... View more

As a service provider for customers to build a data platform with Fabric and implement Power BI reports. It would be good if guest accounts were supported in the same way as native accounts as customers prefer using guest accounts rather than native accounts.   ... View more

ISSUE: In a Fabric pipeline, after creating for the first time a new table or writing to a lakehouse table with a Copy Data activity, pipeline execution moves on to the next activity in the pipeline faster than the lakehouse has time to update and show that there is new data available to downstream activities.  When these activities try to read from the lakehouse table, of course, this causes an error.  If this happens right after the table was created for the first time, the pipeline environment does not see the table as existing yet since the execution thread is moving forward faster than the lakehouse can update and tell the pipeline that now it has a new table or new data.   POSSIBLE SOLUTIONS:   1__Have an option in the Settings tab that when checked, causes the Copy Data activity to start waiting for a response from the lakehouse.  After the lakehouse sends the response that the all the data or table has been committed, clear the wait flag, and Copy Data activity completes its execution, and the pipeline execution resumes with the next activity.   OR    2__Provide a new activity called "Wait for I/O commit", which would pause the pipeline execution and wait for the lakehouse that is specified in its settings to send a message that the data is now available for read operations. Upon receipt of said message, this activity would allow pipeline executoin to resume.     2 simple, elegant, and user-friendly ways to once and for all get rid of this synchronization headache. ... 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

queryinsights currently supports only ASCII characters.   Specifically, both the command column in queryinsights.exec_requests_history and the last_run_command column in queryinsights.frequently_run_queries have non-ASCII characters converted to “? ”and the last_run_command column of queryinsights.frequently_run_queries are converted to “? ”.   In order to use queryinsights in auditing, it would be effective and useful to support non-ASCII characters.   We have been informed from a Microsoft support request that this limitation will be removed in a future feature addition. We therefore hope to have this resolved as soon as possible. ... View more

Hi,   Currently, it is not possible to trigger a Fabric notebook run via the REST API, when the notebook is communicating with a lakehouse that has schemas enabled.   This feature is marked as 'Public preview', but there are several threads suggesting a fix would have been in place by late 2024: https://community.fabric.microsoft.com/t5/Data-Engineering/Error-when-writing-data-into-schema-enabled-lakehouse-using/td-p/4111069   The workaround suggested does not work either. It seems very strange that it works without the schemas enabled. The underlying issue seems to be:   INFO notebookUtils [Thread-62]: [FabricClient][ListWorkspaceByMssparkutils][get] Completed request url https://api.fabric.microsoft.com/v1/workspaces/ with correlation id X, requestId: X, activityId: , status code: 403, total cost 173ms, request cost 166ms   A timeline of when this feature would be supported will be appreciated.   Regards,   Oliver ... View more

Our firewall has blocked the traffic to connect Fabric database, they only allow strict encrytion connection type in SSMS, but there is no such kind of option in Power BI Desktop, hope you can add it. ... View more