It's fairly minor, but can the width and height boxes be swapped round? I always think of width first. Also the boxes below are horizontal and then vertical so it would be consistent. Sometimes I make mistakes because I naturally assume it's width first. Many thanks.     ... View more

How are we supposed to do version control if there is no option to export to JSON like we had with Gen1? I don't want to commit changes using git integration. ... View more

WHY is the Ribbon not customizable in Power-BI? WHY is there no option to hide the AI if one does not want to use it?! ... View more

While creating an app and adding the audience, all people who are added can view all the reports in single app curretly. It would be great if there is an ability to select audience to view only some reports in app and other audience can view other reports not all in same app. ... View more

Implementing this would make Direct Lake on OneLake a true superset of onSQL, combining its unique benefits with greater query reliability and flexibility. Currently, when using Direct Lake on OneLake, guardrails are enforced for each table (such as the 1.5 billion rows/F64 limit). When these limits are reached, queries cannot be executed due to memory constraints. This is a significant restriction, especially given the many advantages of building models on OneLake—such as applying OneLake Security and leveraging multi-artifact model creation. Although this is a common limitation of Direct Lake, in onSQL-based models, this issue was effectively mitigated through Direct Query (DQ) fallback—meaning that when Direct Lake could not handle a query, it would automatically switch to DQ and allow the query to continue. I propose enabling the same Direct Query fallback mechanism for Direct Lake on OneLake. If a table hits the memory or row limit and the query cannot be executed in Direct Lake mode, the system should automatically fall back to Direct Query. ... View more

Admins need to be able to see a summary of CU usage for Fabric Trial capacities. Just a maximum % used figure would be enough to plan for sizing a new Fabric capacity purchase.   Thanks. ... View more

Often there are multiple posts submitted here by different people for the same or very similar idea. We should be able to suggest merging them so that there is only one post per idea. This way, everyone can vote on the same post and the level of support will be more accurate instead of spread out over multiple posts. ... View more

We would like to explore the possibility of enabling support for connecting Microsoft Power BI Report Server (PBIRS) to ClickHouse using DirectQuery. As our organization is actively considering migrating key datasets to ClickHouse, establishing a seamless DirectQuery connection with PBIRS would be a critical enabler for delivering real-time analytics and ensuring our reporting infrastructure remains efficient and responsive. Currently, Power BI Desktop RS supports ClickHouse connectors; however, after publishing reports to PBIRS, we encounter limitations that prevent DirectQuery from functioning as expected. This has a significant impact on our ability to fully leverage ClickHouse within our reporting workflows. ... View more

It would be helpful to have a feature that allows users to select multiple tables directly from the lakehouse and delete them in bulk, without the need to write and execute notebook code.     ... View more

In the new org app, if there was an option to add page level permissions for a report that'd be ideal! ... View more

Hi Team,   There is a gap with the Fabric REST APIs for Deployment Pipelines, we can't assign access via an automated method.   Required APIs: List Deployment Pipelines Role Assignment Add Deployment Pipelines Role Assignment Update Deployment Pipelines Role Assignment Delete Deployment Pipelines Role Assignment   We can how create deployment pipelines via Terraform since v1.3.0 fabric_deployment_pipeline | Resources | microsoft/fabric | Terraform | Terraform Registry   But we still have a manual task to provision access, please can this gap be closed in REST APIs so Terraform can build a module once it exists.   Thanks     ... View more

Hi Community,  Together with my team and our Client, we have multiple reports created in Report Builder. We would like to make the reports more users-friendly/accessible for our end users by allowing to change the order of columns in the reports. In reports with many columns, it is very essential to have this ability as end users often have different needs/priorities on what they want to analyze. It would be nice if such an option was introduced, as now all that is left is to export data and change manually in Excel or Word files. ... View more

It would be a great idea if it would be possible to dynamicly update field names in parameter via slicers currently you need to do a model refresh for that to update having the ability via slicers would be a great helpIt would be highly beneficial to have the capability to dynamically update field names in parameters using slicers. Currently, a model refresh is required to update these field names. Implementing this functionality via slicers would significantly enhance the user experience and streamline data analysis workflows. It would be highly beneficial to have the capability to dynamically update field names in parameters using slicers. Currently, a model refresh is required to update these field names. Implementing this functionality via slicers would significantly enhance the user experience and streamline data analysis workflows. ... View more

Feature Request to support change connection to DriectLake: Currently users only have options to change connection between direct Query, import, or Dual. We would like DriectLake to be included so that we don't have to recreate all the calculated fields ... View more

Add a metadata or description field to Groups, Reports, Datasets, Dashboards, etc.   We are using embedded reports. It would be helpful if the API returned a field that could hold a string, such as a JSON string or plain text. Our application making use of embedded reports could then use that field to help the user find the report they desire. ... View more

Description: The “Allow report readers to personalize visuals” feature in Power BI is highly valuable for enhancing user experience by enabling interactive customization. However, when this feature is enabled, users are granted the ability to use the “Add a field” option—allowing them to insert unused fields from the data model into visualizations.   Need: In many enterprise reporting scenarios, it is crucial to limit users' personalization capabilities to predefined fields only. While actions such as changing axes, sorting, or selecting existing fields are acceptable, allowing users to add new fields can break the intended structure of the visual or lead to misinterpretation of data.   Suggestion: Introduce a separate permission or toggle under the visual personalization setting that controls the “Add a field” functionality. For example:   Personalization: Enabled Add new fields: Disabled / Enabled   This would give report authors more granular control over what aspects of a visual can be modified, while still empowering users with some level of interactivity.   Benefit: Such a setting would help maintain data integrity and consistency across reports—especially in governed, standardized reporting environments—while still supporting interactive exploration within clearly defined boundaries. ... View more