Many data sources are not supporting query folding, and for those that do, if users perform transitions such as merging, changing data types, or duplicating columns, it breaks the query folding. It would be helpful if they could manage transitions along with query folding. ... View more

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

Currently, when using the “Apply to: Labels” option in matrix visuals for conditional formatting, Power BI applies the formatting to all row headers, including both regular rows and subtotal rows. This behavior is consistent across both Power BI Desktop and the Power BI Service, and it is not configurable to scope the formatting to only subtotals. This limitation causes confusion and inconsistent visual behavior—especially in scenarios where users want to highlight only subtotal rows for clarity in large hierarchical matrices. In semantic model .pbix files, the formatting may appear more scoped due to local model context, but in live-connected reports, the formatting engine lacks the metadata granularity to distinguish between subtotal and non-subtotal labels. Proposed Enhancement:  Introduce a new option in the “Apply to” dropdown for matrix visuals that allows users to apply conditional formatting only to subtotal labels. This would provide parity with the existing “Apply to: Values,” “Totals,” and “Subtotals” options and give report authors more precise control over formatting behavior. Benefits Enables cleaner, more intuitive matrix visuals in both semantic models and live-connected reports. Reduces formatting inconsistencies between development and production environments. Improves accessibility and readability for end users by clearly distinguishing subtotal rows. Eliminates the need for workarounds such as importing models or using custom themes. Reference:  @https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-conditional-table-formatting @https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-matrix-visual-format-settings?tabs=powerbi-desktop   ... View more

Python and R visuals are currently not supported when publishing a report to web. It would be really helpful if this was supported, for creating and sharing custom visuals. ... View more

It would be great to have a custom option to send subscription the Friday before or Monday after when the chosen days in the "Subscription Schedule, Repeat Monthly, Every month day(s)" fall on a weekend then the option to select a prior business day or next business day option.   ... View more

The current card visual forces users to overlap elements or waste copious amounts of time creating custom visuals. The new card feature should give users the ability to create multiple cards in a single container and provide a greater level of customization. ... View more

It would be beneficial to incorporate features from Pivot tables that allow for the expansion and collapse of columns and hierarchical column groups within tabular visuals. This would not only solve the current limitations of matrices but also provide report creators with the flexibility to hide and show rows and columns, saving these settings for future use, thus eliminating the need to scroll through irrelevant data. ... View more

Enabling customized calculations at the query level for subtotals and grand totals would offer greater flexibility in reporting and preserve performance. Efficient organization of control settings to modify the style of these totals separately will empower report creators to achieve their desired appearance, while addressing their need for more control and customization in reporting. ... View more

Imagine a world where report creators can automatically apply slicer and filter selections based on specific logic, revolutionizing data analysis and user experience. This innovative approach eliminates any need for complex workarounds, optimizes slicer functionality, and paves the way for more efficient and effective data reporting. ... 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

We have a dashboard where we have the date format as 01-Jan-2025 as this particular dashboard is accessed by users from other regions as well. But as per the official document from Microsoft, when we use a slicer to display or set a range of dates, the dates display in the Short Date format (DD-MM-YYYY or MM-DD-YYYY) and it is the user's browser or operating system locale that determines the date format. This is the display format no matter what the data type settings are for the underlying data or model. However, this can create confusion with users belonging from different regions who are accessing the dashboards. We would request you to come up with different date formats for the between style of date slicer.   ... View more

If you export a PDF when you are resizing the campus size of a report, the visual size will be reduced and displayed within one page. We would like the campus size and visual size to be fixed, so that when the PDF export exceeds the page size, the page is automatically split. ... View more

Interpreting visuals without a clear legend to indicate logic behind specific styles can lead to confusion and decision-making errors. An idea to enhance clarity and transparency by ensuring legends and tooltips accurately display colors, patterns, and other visual components influenced by logics, would enable report consumers to easily understand the applied logic and make more effective decisions. ... View more

We have developed lot of templated dashboards that have key insights for each customer as a semantic model & reports by handling them as parameters in Power query to dynamically load basis the value - only difference is the employee dimension table that has different column names for each customer. There is currently no mechanism to centrally propagate changes—such as updates to visuals or metrics—across all customer-specific reports at once. Any modification made to a visual or measure in one report must be manually replicated in each of the PBIX files. Impact: High Maintenance Overhead: Every update requires manual intervention across all reports, consuming significant time and resources. Increased Risk of Inconsistency: Manual updates increase the likelihood of discrepancies between reports, leading to potential data integrity and trust issues. Delayed Rollouts: Implementing even minor changes across all reports can delay delivery timelines and responsiveness to business needs. Scalability Limitations: As the number of customer reports grows, the current approach becomes increasingly unsustainable Proposed Solution: Need for an centralized update propagation mechanism within Microsoft Fabric or Power BI ecosystem. This could take the form of: Linked Visuals and Measures: Allow visuals and DAX measures to be referenced from a central repository or template file. Template Binding: Enable PBIX files to inherit layout and logic from a master template, with the ability to override only non customer-specific elements. Impact: Implementing such a mechanism would dramatically reduce development effort, improve consistency, and enable faster, more reliable rollouts—making Power BI a more scalable and enterprise-ready solution for multi-tenant reporting scenarios. ... View more

I’d like to suggest adding the ability to configure quotas for Microsoft Fabric workspaces, applicable to both new and existing workspaces. This feature would allow administrators to set limits on compute capacity (CUs) and storage usage, helping organizations better manage resources, control costs, and prevent overconsumption. Having workspace-level quota controls—similar to those in other Azure services—would greatly enhance governance and operational efficiency across larger environments where multiple teams or departments share Fabric capacity. ... View more

Regarding the Vnet Data Gateway public documents, please state whether or not DataPipeline / Dataflow Gen2 is supported on a per connector basis.   Cx is confused as to why it is supported by Datapipeline / Dataflow Gen2 but not available on some connectors. This is a matter that could be avoided by providing explicit documentation, but Cx is also frustrated by the lack of documentation.   Providing this information would greatly benefit users. ... View more

We suggest the idea that it becomes possible to add column and table descriptions directly to Lakehouse tables in Fabric.    Currently, it is only possible to add column and table descriptions to tables in semantic models in Fabric.   In Microsoft Purview, data quality scans are no longer possible on semantic model tables (SQL endpoint tables), instead only data quality scans on Lakehouse tables are possible. We would like to be able to see the column and table descriptions in these scans, similarly as how these could be seen in Purview for semantic model column descriptions from Fabric. For this the possibility to add the descriptions to the Lakehouse directly in Fabric is needed. ... View more

End users would like to see the "Start" date as well as the "Due" date on the top page of the scorecard.  Those without edit access cannot see the start date. Workaround has been to use "time period" in Notes, but this is not a great solution.  ... View more

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