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

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

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

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

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

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

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

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

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

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

Enable to read files from sharepoint folders directly within Fabric using OneLake Shortcuts. ... 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

Microsoft Fabric should introduce a native Workday connector, similar to existing connectors for platforms like Salesforce and SAP, enabling seamless ingestion, transformation, and analysis of Workday data. Key Features Requested: Direct Data Extraction: Fetch Workday data via a low-code/no-code interface. Optimized Performance: Support for batch and incremental loading to minimize API calls and improve refresh speeds. Prebuilt Authentication: Simplified OAuth or SAML authentication for Workday. Schema Detection & Mapping: Auto-detect Workday objects (e.g., employees, payroll, financials) and enable easy transformations in Fabric. Real-Time & Scheduled Sync: Support real-time ingestion or scheduled data refresh for Workday data. ... View more

Hi Team,   Can we replicate the ADLS Gen2 Lifecycle Management options to OneLake please.   eg If a customer wants to build an archival type solution with data retension policies we can't recommend using OneLake as an alternative to ADLS Gen2 storage account as it doesn't have the same lifecycle policies to allow us to delete files.   We have this idea to bring add ability to do tiers but we need the liefcycle policy option on top please https://community.fabric.microsoft.com/t5/Fabric-Ideas/Add-storage-tiers-to-Fabric/idi-p/4508264   Thanks, Darren ... 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

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

The image URL should be a publicly accessible link. However, many users prefer to use image files securely. When opening a report, it is preferable to also authenticate the image.   ... View more

Would it be possible to have the option of archiving data or storing it in a cool data tier to save costs for the future? Otherwise data storage costs just grow infinitely. ... View more