The primary axis are outdated and require significant improvement when compared to Excel. This makes it difficult for report creators and often leads to problems when trying to manage and style them effectively. By offering more format settings, greater control over displayed data can be provided, especially if axis ticks, new gridlines, and separators are also included. ... View more

We have a customer who is overseeing Power BI usage across their organization, and he is looking for a way to analyze user adoption and engagement trends over a broader time horizon. Specifically, they would like to request an enhancement to extend the data retention period in the Monitoring Hub from the current 30 days to at least 90 days. Issue Summary: Currently, usage metrics in both the Feature Usage and Adoption Report and Content Sharing Report are limited to approximately 28–30 days of visibility. Advanced filtering options also do not retrieve older data reliably. While we explored alternative options—such as using Audit Logs and Usage Metrics Reports—they provide fragmented insights and do not offer the comprehensive, user-centric dashboard that Monitoring Hub delivers. Having a 90-day window would allow teams like ours to: Conduct quarterly trend analysis Identify adoption lags and training needs Prepare more meaningful management reports Make better-informed decisions on resource planning and governance Thank you in advance, we believe this enhancement would significantly improve its utility for administrators. ... 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

I want to restrict the purchase of custom visuals for Power BI regardless of certification. ... View more

Currently, when a report has a large number of subscribers, any edits made to its email subscription such as adding or removing recipients do not appear in the audit logs. This is due to a backend design limitation where the audit log file size must remain under 4KB. This limitation poses a challenge for users who lack premium capacity and cannot manage subscriptions via security groups. Without proper logging, it's difficult to track who made changes to the subscription settings, which impacts transparency ... View more

After clicking on "Update All" button in "Updates" tab in "Source Control" pane - a dialog pops up indicating failure because the action would cause duplication in the workspace of an item name and type.   Customer would like to request a feature that after the Git update in the source control syncs the artifacts with existing artifacts if they have the same name. ... View more

The option should be visible for the admin to manage delegate settings for other admins. Currently, the Delegate settings to other admins option isn't available because it's automatically delegated to capacity admins. Enable Microsoft Fabric for your organization - Microsoft Fabric | Microsoft Learn ... View more

Designing RLS based on department affiliation requires separate management of which users are linked to which departments, which makes maintenance difficult. This information may be held in EntraID job information, and using that information in RLS would resolve the issue. ... View more

Please allow changing the connector type—not just the data source—in an already published report, such as from ODBC to the Snowflake connector. ... View more

Excel Pivot Tables have the capability to drill-through (double-clicking numbers in the pivot table), which direct lake models don't seem to support.   In the models themselves, we can define detail rows expressions just fine, and the DAX DETAILROWS function also works fine, but the MDX equivalent that Excel generates does not.   Idea is to add capability for Pivot Table drill-through against Direct Lake semantic models.   Thanks! ... View more

To address the challenges of organizing and presenting data due to the limitations of column and row headers, a potential solution would be to implement a new matrix visual with customizable controls, allowing report creators to adjust the dimensions of columns and rows, group them hierarchically, apply diverse styles, and use conditional formatting. ... View more

At the moment if you add in a button to apply all slicers this stops the insteration between visuals on the page until the button is clicked. It would be helpful to have more granular control of what visuals you want to be affected by the "Apply all Slicers" button ... View more

Hello Dear Fabric Team,  it is very painful for all of us interoducing Microsoft Fabric in Big Enterprises where Security and Governance have a big role. My suggestion is to be transparent and clear to add in appropriate Place (Power BI / Fabric Admin Portal or in Azure Portal) just a list of needed endpoints including required Ports and a yes/no check-status if the connection to each endpoint/host:port possible or not.   if it is not possible the IT-Sec Team must setup the right Firewalls/Proxy configuration Thanks Best Regards ZN ... View more

Bookmarks are currently not supported in PowerBI org apps. Could this feature please be added? ... View more

Currently the only way I have found for Power BI to recognize my hierarchy/WBS codes for which I organize my data is by creating new columns based on the delimiter then, when out of transform, turning it into a hierarchy. If there was a data type that was recognized as a hierarchy we could use it to organize our data, sort it, and filter it based on levels of the Hierarchy. Furthermore, my WBS has a name associated so once I deconstruct then reconstruct it no longer recognizes the name. While I know there are always other ways of creating a heirarchy, just having a data type that recognizes the data as such would cut out a lot of steps. ... View more

There is a lineage view issue when a manually created Mashup query is used to build a semantic model that connects to a dataflow. The document mentioned that lineage between semantic models and dataflows is not guaranteed if a manually created Mashup query is used to connect to the dataflow. Lineage in Fabric - Microsoft Fabric | Microsoft Learn When connecting to the dataflow on the desktop and using the Power Query advanced editor, I tried entering the dataflow name and workspace name instead of the dataflow ID and workspace ID before publishing. However, they were unable to see the dataflow in the lineage view.   The customer requested a feature that allows the mashup query, which includes the dataflow name and workspace name and publishing it to display the lineage view correctly.     ... View more

Please make it possible to use Managed Identity with Fabric items like Notebooks and Data Pipeline.   Benefits: No need to handle credentials. The item won't be related to a physical person. Then, we can give the Managed Identity access to read (and write to) data storage items in other Fabric workspaces, Azure SQL, ADLS, Dataverse, etc.   So that we don't need to rely on human users, and also don't need to handle credentials. ... View more

Introduce a dedicated split-view or detachable pop-out editor within Power BI Desktop for writing and tweaking DAX measures, DAX queries, and TMDL definitions. This live-editing pane would sit alongside the report canvas, either docked (right-hand side) or in a separate floating window - allowing users to: Write and modify DAX measures with full IntelliSense and formatting support See live updates reflected in the report visuals without switching tabs or having the formula bar get in the way Run DAX queries (via DAX Studio or Performance Analyzer-like pane) and instantly see results Author or tweak TMDL model definitions with immediate visual and metadata feedback This would drastically improve productivity, support iterative analysis, and bring parity with modern IDE workflows. It removes the constant context-switching between visuals and the model pane, making development faster, more responsive, and much more intuitive. ... View more

To address the limitations of our current slicers, which are less advanced and potentially confusing compared to our competitors, a new and enhanced list and dropdown slicer should be designed with a wider range of customization options, incorporating industry best practices, and include innovative features like the ability to copy and paste lists. ... View more