Would be helpful if we could use bookmarks to adjust column header widths in a visual. Currently, that information does not seem to be captured, even when using "Personalize Visuals" with the "Auto-size width" option turned off. ... View more

It would be very useful to have a centralized view for managing page properties, particularly filters. Instead of opening each page individually to configure or modify filters, users could manage all page filters and related settings in one place. This would save time, ensure consistency, and make report maintenance much more efficient. ... View more

The only step in my deployment for test and production switching that is still unsupported are DirectLake semantic model sources. I have been successful in some hacky fixes where I can parameterize the directlake source but it then breaks editing of the directlake semantic models.   Specifically toggling the url in the semantic model expression: expression 'DirectLake - kusa_accounting' = let Source = AzureStorage.DataLake("https://onelake.dfs.fabric.microsoft.com/workspaceid/lakehouseid", [HierarchicalNavigation=true]) in Source   If we could usue a parameter here, normal Deployment Pipeline rules could change this. Better would be detecting this data source and allowing for setting the url in a data source pipeline rule would save having to create a parameter myself.   Alternatively, I'm using Variable Libraries in my other areas of deployment, and if we could specify this url from the Variable Libraries would work. This would probably be better since I find Variable Libraries more flexible and usable even without Fabric Deployment Pipelines. ... 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

Re: API Call for Workspace Contacts in Workspace S... - Microsoft Fabric Community   Retrieve workspace contacts from workspace settings via REST API Call   I need to Track Capacity backed workspace contacts across the organization in a Workspace catalog So that i can ensure each workspace is properly administered and managed       ... View more

Smart Narrative provides dynamic summaries of data, which would greatly enhance contextual storytelling in tooltips. Currently, it’s not supported in tooltip pages. Enabling this would allow users to deliver richer insights on hover-over interactions.   #SmartNarrativeTooltip ... 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

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

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

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

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

There is a limitation with the What if parameter:　 "Parameters can have at most 1,000 unique values. If a parameter has more than 1,000 unique values, the parameter values get evenly sampled." https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-what-if#considerations-and-limitations In a single-value slicer, I want all values—even those exceeding 1,000—to be displayed as unique, rather than being sampled. ... 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

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

Please make the Power BI Workspace taskflow pane default as minimized. I am watching users open workspaces and the first step they take is minimizing the task flow pane. Users have also requested that it be minimized by default. ... View more

Increase the supported unique value limit for slicers and parameters beyond 1,000. ... 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 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