Currently, each premium workspace must be linked to Log Analytics manually, which is time-consuming. Introduce an option to select and assign all premium workspaces to a Log Analytics workspace in a single click, simplifying the process and saving effort. ... View more

Power BI Semantic Data Modeling - More than one relationship.  If this option is enabled, we can avoid creating more calcualted columns to define the key for establishing the relationship.  ... View more

As a Fabric Admin, we noticed there are restrictions when it comes to accessing cloud connections throughout our Microsoft Fabric environment. Access is controlled by ownership and specific permissions, which means even Fabric Admins can’t view or manage these connections unless they’re given explicit access. This can make it challenging to troubleshoot, audit, or assist users in different departments efficiently. ... 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

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

During Lakehouse deletion operations in Microsoft Fabric, users may observe that the associated SQL Endpoint and Semantic Model are not automatically removed. These orphaned artifacts may cause downstream deployment errors or stale resource references.   There is one available API to remove it, but it is not very user friendly and also requires admin rights so developers cannot do this on their own. It is mentioned here: Solved: Can't delete orphaned lakehouse SQL analytics endo... - Microsoft Fabric Community   The idea is to make this option available in the UI or at least provide more user friendly ways to do it. ... View more

Increase the supported unique value limit for slicers and parameters beyond 1,000. ... View more

If it was possible to offer a robust and customizable style management system for the matrix, it could be the key to enhancing the professional appearance of tables and matrices. Further, giving report creators the ability to adjust gridlines, color, style, and the addition of custom icons, bars, sparklines, and other elements, along with a variety of pre-designed styles, would significantly improve style management options for tabular elements. ... View more

Enable individual users / freelancers to study and practice fabric with a per-user license similar to Premium Per User in Power BI. F2 is a price point that is too high for them. Strong limitations in time and resources available would make sense, but there should be a clear monthly cap that cannot be like the current F2. ... View more

Allow horizontal scrolling in source control frame instead of triiming the object names ... View more

Quire is a collaborative project management platform built to help teams plan, track, and execute projects with clarity. From simple task lists to complex workflows, Quire enables users to break big goals into manageable steps, visualize progress through List, Board, Timeline, Table, and Calendar views, and collaborate seamlessly in real time.   By integrating Quire with Power BI, teams can transform their workflow data into dynamic visual reports. This integration allows users to analyze project progress, track KPIs, and uncover performance trends effectively and directly from Quire data. ... View more

I am following the documentation at https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-gen2-parameterized-dataflow to parameterize my dataflow and pass in the parameters from my variable library. I am able to pass the parameters to the dataflow from the pipeline to the dataflow but once I try to parameterize the workspace id and dataflow id in the pipeline, the dataflow parameters option disappears.   I've found a temporary workaround by saving it both ways and then manually merging the source file, but every time I open the pipeline to make edits, any saves overwrite my work around.   Can the UI be updated to show the dataflow parameters when variables are used for the dataflow?   Passing Parameterized values to the dataflow:          parameterizing the dataflow connection breaks/hides the ability to pass the parameters to the dataflow:       Manually edited pipeline-content.json:     ... View more

Description: In Power BI Report (PBIR) metadata, every visual already has an isHidden property that controls its visibility. Today, however, this property can only be set manually in the UI (via the Selection pane). There is no way to drive this property dynamically using a DAX expression. This is a major limitation because one of the most common use cases for Bookmarks is to simulate conditional visibility (show/hide visuals depending on user selection or business logic). While bookmarks work, they are cumbersome, static, and hard to maintain at scale. Proposal: Enable a new “Visibility” binding for visuals in the format pane, where authors can assign a DAX measure (fx) returning TRUE/FALSE (or 0/1). If the measure evaluates to TRUE → visual is shown. If FALSE → visual is hidden (not rendered). Benefits: Much more flexibility for UX/UI design. Reduces dependency on complex bookmarks. Simplifies scenarios such as: Show a chart only if a slicer is selected. Hide detailed visuals until a KPI passes a threshold. Display different layouts per user role or context. Aligns with the existing isHidden property already in PBIR at visual level, making it available for dynamic scenarios. Why now Conditional visibility is a frequent request feature in the community. Users of other Microsoft data platform solutions, such as Power Apps, are accustomed to having the ability to modify this property. PBI developers already simulate this via workarounds (blank measures, bookmarks, overlaid shapes with managed transparency).   A native solution would make reports more dynamic, performant, and easier to maintain.   @Miguel_Myers  ... View more

It would be extremely helpful to have a built-in feature in Power BI that allows administrators to identify inactive users segmented by license type (Free, Pro, Premium Per User, Embedded, etc.). ... View more

Currently, only Pie and Donut charts can automatically show data labels as a percentage of total. For all other visuals (like Bar, Column, Line, or Treemap), users must manually create a DAX measure to calculate “% of total.” This creates extra complexity for report authors and is inconsistent with the simplicity of Pie charts. Add a visual-level option (in the Format or Data labels pane) to “Show value as → Percent of total”, similar to Excel’s “Show Values As” or Power BI’s existing “Show Value As” feature for Table / Matrix visuals. The visual should handle the denominator automatically based on current filters and slicers, no custom measure required. ... View more

When using the Branch Out Option in Git Integration, Items created in the New Workspace still have Lineage tied to Items from the Source Workspace. This should be updated to allow for easier branching out without having to manually change lineage of Items that require dependancies. For Example, if Workspace A has Lakehouse A and Notebook A that is attached to Lakehouse A, you branch out to Workspace B which would create Notebook B. In the current scenario, Notebook B would still be attached to Lakehouse A in Workspace A. Rather, it would be better if Git Integration automatically changed Notebook B to the correct Lakehouse B whenever you branch out. This may require that Lakehouse Views are also carried over and tracked in Git.  ... View more

We recently implemented programmatic pausing and resuming of Microsoft Fabric capacity using the API. While testing this setup with a Power BI embedded report, we noticed an interesting behavior. When filters are applied to the embedded report and the report is left idle for a few minutes, the Fabric capacity automatically transitions to a paused state. Later, when we try to access the report again, the capacity begins to resume, but during this process, the report throws an error. Once the capacity becomes active, the report refreshes automatically—however, this refresh clears all previously applied filters and resets the report to its default page.   Our goal is to maintain the applied filters even after the capacity resumes.  ... View more

Currently the only option for connecting to a lakehouse using a cloud connection is an organisational account. Adding in Service Principal as an option would avoid the reliance on single user accounts and would bring the lakehouse connector into parity with the warehouse connector. ... View more

Considering the most powerful and versatile machines are being built on ARM processors and many developers preferring these machines due to the extended battery life, or performance per watt, I think it would be critical for Microsoft to start developing Power BI Desktop to be fully compatible with ARM64 processors. Windows ARM with a snapdragon processor is a great machine. It is where all machines are going. It's time for Power BI Desktop to get up to speed with everything else. ... View more