Enterprise customers adopting Microsoft Fabric want to standardize on OneLake as the unified storage layer for both structured data (Lakehouse tables, Warehouse data) and unstructured data (files stored in OneLake). This data may originate from external systems (ADLS, S3, databases, SaaS) or be created natively within Fabric workloads. A growing number of regulated customers have Infosec and compliance requirements to enforce retention policies consistently across all data in OneLake, regardless of source or workload. Today, customers are explicitly asking for a OneLake‑scoped retention capability that they can reason about as a storage‑level control, similar in intent to ADLS lifecycle policies.   A native, Purview‑governed OneLake retention model would materially reduce this adoption barrier and strengthen the OneLake governance story. ... View more

Need Purview data source connector in Power BI desktop ... View more

OpenLineage lets you trace a large number of ETL jobs that mutates tables, letting you trace changes to tables significantly easier. Databricks Unity Catalog has support for Column Level Lineage and it's highly useful: View data lineage using Unity Catalog - Azure Databricks | Microsoft Learn Databricks Demo   AWS also supports OpenLineage:  Amazon DataZone introduces OpenLineage-compatible data lineage visualization in preview | AWS Big Data Blog It's actually quite easy to get OpenLineage working in Fabric Spark since you already have the JAR pre-installed: Column level lineage in Fabric Spark with OpenLineage and stashing the lineage in Delta Lake | Raki Rahman   All we need is a way to store and query historical state (e.g. in Delta Lake), and a UI component that hooks into the Lakehouse catalog and offers an API on top of OpenLineage schema. The OneLake Catalog UI could look like this:   To prove this can be fairly easily achieved since the OpenLineage events are robust with a stable schema, I vibe-coded this little static site that works with the default Fabric Spark OpenLineage events: Marquito — OpenLineage Visualizer       ... View more

Enable automated authentication for Snowflake connections in Power BI Gateway to eliminate dependency on expiring user credentials. This would prevent dataset refresh failures caused by password expiry and ensure uninterrupted, secure data refresh for enterprise environments. ... View more

It’s challenging and time-consuming for both new and experienced report creators to organize data when trying to split cards into categories. By introducing small multiples, it could be a familiar and easy way for report creators to intuitively categorize data, especially if they had more control over layout and formatting. ... View more

Today, semantic model version history helps restore snapshots for a single semantic model, but it doesn’t provide an environment‑to‑environment diff or reconciliation report. Customers need an automated compare/diff view (tables/measures/relationships/RLS) across environments to safely replicate PROD changes into UAT and audit “who changed what”. Request: extend/version history & deployment experience to include cross‑environment change tracking and comparisons (not just per‑model snapshots). ... View more

User was granted Viewer access to a Power BI Workspace App only, without any permissions at the workspace level. Despite this limited access, when the user selected “View semantic model”, the full semantic model details including schema, tables, and measures were visible. To verify this behavior, we performed multiple tests: Created a Power BI App and assigned Viewer access to a test user. The user could view the report. The user could also see the semantic model contents when clicking View semantic model. Assigned Viewer role at the workspace level. The behavior remained the same the semantic model’s tables and measures were still visible. Removed all workspace roles and shared the report directly with the user. The user was still able to view the semantic model schema via the App. User want to hide the view semantic model option, tables and measures to other users.  ... View more

Power BI Apps currently expose the Embed option only for reports, while dashboards included in the same app do not show any embed option in the Power BI Service UI. This inconsistency causes confusion for users, as reports and dashboards are commonly delivered together within a single app experience. We request native support to generate Embed URL / Embed configuration for dashboards directly from Power BI Apps, similar to reports, to ensure consistency and simplify embedding scenarios. ... View more

While creating a SQL Server connection using Service Principal, we have two options. One is to provide the client secret directly and the other is to reference the secret from Azure Key Vault. Both connections get created successfully, but in the current UI both appear exactly the same. Because of this, it is not possible to easily identify which connection is using the direct secret and which one is using the Azure Key Vault reference. In environments where multiple connections are created, this makes it difficult for administrators and developers to manage and verify whether Key Vault is being used for credential management. It would be helpful if the UI could show a clear difference for connections created using Azure Key Vault. For example, showing the credential source, displaying the Key Vault reference, or adding a small indicator in the connection details. This would improve visibility and make connection management easier. ... View more

Currently high concurrency session is available only under strict rules.  as of now: Session sharing conditions include: Sessions should be within a single user boundary. Sessions should have the same default lakehouse configuration. Sessions should have the same Spark compute properties. If we could reuse high concurrency session between multiple users, that would improve usability in big teams where a lot of people run may small task at the same time. All other conditions can be met. ... View more

Field Parameters currently treat all selected columns as a flat list, ignoring any hierarchical relationships that exist between those columns in the data model. This prevents the creation of asymmetric reports with proper grouped/parent-child structures. This feature request asks for Field Parameters to automatically detect and honor existing hierarchies between the columns included in the parameter, enabling grouped asymmetric reporting without requiring any complex and slow workarounds like switch statements in DAX and disconnected tables. What is an Asymmetric Report? An asymmetric report displays different measures or data combinations for different columns . For example: Budget vs. Actuals by Time Period: 2024 ├─ Budget ├─ Actuals └─ Variance 2025 ├─ Budget └─ Forecast (no Actuals yet)   Proposed Solution Instead of omplex workarounds, make Field Parameters automatically detect and respect hierarchical relationships when used in the Columns area of a matrix visual How It Would Work: 1. Enhanced Field Parameter Definition with Parent Column: Users define parent-child relationships directly in the Field Parameter using a "Parent" column: DAX Year Metrics = DATATABLE( "Column Header", STRING, "Field", STRING, "Sort", INTEGER, "Parent", STRING, { {"2024", "", 1, ""}, {"Budget", "[Budget]", 2, "2024"}, {"Actuals", "[Actuals]", 3, "2024"}, {"Variance", "[Variance]", 4, "2024"}, {"2025", "", 5, ""}, {"Budget", "[Budget]", 6, "2025"}, {"Forecast", "[Forecast]", 7, "2025"}, {"2026", "", 8, ""}, {"Budget", "[Budget]", 9, "2026"} }) Where: Column Header: Display name for the column Field: Measure reference (empty for parent headers that are just labels) Sort: Order of columns Parent: References the "Column Header" value of the parent (empty = top-level)   2. Display in Matrix Visual Columns: When this Field Parameter is added to the Columns area of a matrix, it would display as:     Products on Rows     | 2024                                    | 2025                                  | Budget | Actuals | Variance  | Budget | Forecast Product A                 | 100      | 95        |             -5 | 110       | 105 Product B                 | 200     | 210      |          +10 | 220        | 215   With proper: Parent column headers spanning their children Each parent column having its own unique set of child columns True asymmetric column structure   3. Performance: No performance degradation for flat Field Parameters Hierarchical column Field Parameters perform similarly to manually created column structures     ... View more

Please make it possible to interactively run a Notebook as a Workspace Identity, Service Principal or Managed Identity.   Purpose: This would allow us to connect to resources that our personal user account doesn't have access to. This would allow us to interactively test notebooks using the Workspace Identity, Service Principal or Managed Identity before we include the notebook in a pipeline. This way, we could test: the identity's access to data sources and the notebook code's functional compatibility with running as SPN/WI/MI (because not all notebook functionality like semantic link is compatible with SPN, we'd like to be able to test this interactively before including the notebook in a pipeline). ... View more

Please create a directory in Lakehouses where we can put folders and files that we wish to check in to Git.   For example, we would like to put configuration files in a Git-tracked folder.   Fabric Deployment Pipelines should also be able to deploy this directory and its contents to Test and Prod. ... View more

When multiple slicers are based on the same date dimension (e.g., a Month slicer and a Date slicer in “Between” mode), the Date slicer does not visually update when filtered by the Month slicer, even though the model is correctly filtered. It would significantly improve UX if the “Between/Before/After” date slicers could optionally auto-sync their visible range with the current filter context. A toggle such as “Synchronize with filter context” would make date filtering behavior more intuitive and consistent across slicer types. ... View more

As per the Microsoft Learn documentation “Troubleshooting dataflow issues – connection to the data source”, dataflow connections are not automatically removed when they are no longer used by a dataflow. Instead, they must be manually deleted or trimmed, otherwise they continue to appear under Dataflow connections. Troubleshooting dataflow issues - connection to the data source - Power Query | Microsoft Learn Observed Behavior When a connection is removed/unlinked from a specific dataflow, it still appears in the dataflow connections list. This behavior is expected according to the documentation, as dataflows maintain associations with previously created data source connections unless a manual trim is performed. The issue becomes more noticeable when: The same connection is reused across multiple dataflows The connection is no longer required for the current dataflow, but is still needed elsewhere [Troublesho...soft Learn | Learn.Microsoft.com] Challenges / Impact There is no direct way to remove or hide unused connections only for a specific dataflow. Manual cleanup (gateway switching / connection trimming) must be performed per dataflow. In environments with hundreds of dataflows, this process becomes: Time‑consuming Operationally expensive Difficult to manage at scale This increases the risk of: Confusion around which connections are actively used Accidental deletion of shared connections used by other dataflows Reference Microsoft Learn documentation confirms that: Old or deleted data source connections can continue to appear Cleanup requires a manual user‑initiated trim process There is currently no automated or bulk cleanup option [Troublesho...soft Learn | Learn.Microsoft.com] Ask / Feedback for Fabric Team The dataflow connections should be updated automatically when they are unlinked or removed from the dataflow, as it is inconvenient to manually remove the connections from Manage Connections and then click Save and Close in the dataflow. We kindly request the Fabric team to implement this update as soon as possible. ... View more

Im using a design for my power bi reports, in which i allow the user to select what measure they want to look at, from a dropdown, instead of having a new sheet for each measure.  This can lead to some filters becoming redunant for certain measures. As to not confuse the user, I am removing the filter options dynamically, depending on the selected measure, using the "filter on this visual".  If the user already has checked some values and left some unchecked not all values are removed. It would be nice to have the option of removing all filters.  Se this thread for a discussion: https://community.fabric.microsoft.com/t5/Desktop/Dynamically-remove-options-on-slicer-regardless-on-checked-state/m-p/5124123#M1460507 ... View more

Currentluy On-premises data gateways aren't supported and fail to register when Private Link is enabled. kindly Support On‑premises Data Gateway when Private Link is enabled ... View more

Adding Page-Level Conditional Formatting Rules in Power BI, a feature that allows users to define one rule and have it automatically applied across all visuals on the page. Ideally, it should also support applying the rule across all fields in a row for consistent, row-level highlighting. I’m suggesting this idea because I’ve personally struggled with managing conditional formatting efficiently in my reports. When I need consistent highlighting across a dashboard, for example, marking negative values or high-risk records, I have to repeat the same formatting steps visual by visual and column by column. This becomes time-consuming and hard to maintain. This feature would also help address another limitation: Power BI currently doesn’t support row-level conditional formatting. Page-level rules would be a practical solution that simplifies the process, ensures consistency, and reduces repetitive work for report developers like me. ... View more

If multiple users want to work with the same Dataflow Gen 2, they currently need to take over ownership, which can be challenging for users in the future. It would be helpful to have an option like workspace permission support, allowing users to edit Gen 2 without needing ownership. ... View more