I know Explore and Org Apps are still in preview, but if Org Apps do not have explore immediately on the selected report, they lose a lot of their usefulness.   Please make sure that Explore feature is also included in Org Apps UI the same way as it is currently in ordinary Workspace Apps. ... 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

Description Power BI Desktop loads PBIP report artifacts only at open time. When PBIP files are modified externally (Git pulls, merge conflict resolutions, scripted refactors), those changes are not reflected in an already opened Desktop session, requiring manual close and reopen. This limits the effectiveness of PBIP in Fabric‑first, Git‑based, collaborative development scenarios.   Why This Matters (Fabric & Git) PBIP is foundational for Fabric CI/CD and Git integration. In real-world team workflows: Developers pull changes from Git while Desktop is open Merge resolutions and scripted updates modify PBIP files on disk Desktop cannot reload or apply those changes without restarting This breaks collaborative development, slows iteration, and makes applying Git merges to active reports error‑prone.   Proposed Solution Add an explicit “Reload from Disk” command for PBIP projects in Power BI Desktop. Discards in‑memory state Reloads PBIP artifacts from disk Equivalent to close & reopen, but controlled and safe (Optional future enhancement: detect external changes and prompt the user.)   Impact Enables Git‑collaborative PBIP workflows Allows applying merges and scripted refactors without restarting Desktop Improves Fabric CI/CD and developer productivity Increases PBIP adoption for enterprise teams ... View more

The user wants to customize default questions on Copilot. We believe that Copilot would be more effective if report viewers could select from prompts that the report developer has predefined, rather than having to type their own prompts. ... View more

We need to subscribe base on the report type. For example, subcribe for paginated reports and normal reports.  ... View more

If multiple users want to work with the same Dataflow Gen 2, they currently need to take over ownership, which can be challenging for users in the future. It would be helpful to have an option like workspace permission support, allowing users to edit Gen 2 without needing ownership. ... 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

In the newer PostgreSQL versions, the "ssl_renegotiation_limit" setting has been removed. The PostgreSQL connector in Power BI is still referencing this setting, so an update is needed for the connector to support encryption with the latest PostgreSQL versions. ... View more

Hello, I would like to request an enhancement to the Page Navigator visual so that it offers the same layout options available in the Button Segmentation Slicer.                                 Layout options: Orientation: horizontal / vertical / grid Style: blocks / full screen Number of columns Automatic grid Spacing (gap) between buttons Overflow style: paginated / continuous scrolling (scroll)           These same options are not available in the Page Navigator, which limits the use of this visual in reports that rely on button-based navigation. I request the evaluation of this feature, allowing the Page Navigator to offer the same layout configuration options as the Button Segmentation Slicer. This enhancement is relevant in scenarios with a large number of pages, where navigation needs to be intuitive, reducing the need for alternative solutions and manual customizations. ... View more

If we recreate an artifact in the workspace and commit both the add and delete actions at the same time, the artifact will save the logical ID. Users expect this process to delete the initial artifact and create a new one with the same name, instead of having to manually perform a delete commit first and then an add commit. ... View more

Would it be possible to include user details (such as account ID, email, or display name) in OneLake events within the Fabric Real-Time Hub so we can identify which user triggered each event? https://learn.microsoft.com/en-us/fabric/real-time-hub/explore-fabric-onelake-events   Including user information in OneLake events would be very helpful, as it would enable us to apply filters and implement custom logic further down the architecture. For example, if a specific user uploads a file, we could trigger an Activator alert, while uploads from other users might follow a different process.   Another scenario would be triggering a pipeline when a user creates a file and, if the process fails, notifying only the user who performed the action.   Thank you in advance for your consideration. ... View more

Adding Page-Level Conditional Formatting Rules in Power BI, a feature that allows users to define one rule and have it automatically applied across all visuals on the page. Ideally, it should also support applying the rule across all fields in a row for consistent, row-level highlighting. I’m suggesting this idea because I’ve personally struggled with managing conditional formatting efficiently in my reports. When I need consistent highlighting across a dashboard, for example, marking negative values or high-risk records, I have to repeat the same formatting steps visual by visual and column by column. This becomes time-consuming and hard to maintain. This feature would also help address another limitation: Power BI currently doesn’t support row-level conditional formatting. Page-level rules would be a practical solution that simplifies the process, ensures consistency, and reduces repetitive work for report developers like me. ... View more

Currently, creating and testing a Fabric Data Agent requires a paid F2 or higher Fabric capacity. Many users, including myself, would like the opportunity to evaluate and test this feature before committing to purchasing capacity. I would like to suggest allowing Fabric Data Agents to be available under: - Trial capacity environments - Limited-time evaluation access - Developer/testing sandbox mode   This would help organizations better understand the value of Data Agents, validate use cases, and make informed purchasing decisions. Providing trial access would accelerate adoption and encourage more customers to invest in Fabric capacity once they experience the feature firsthand. ... View more

Today, Power BI semantic models (datasets/DAX) work well when Power BI is the only BI tool. However, many organizations use Databricks as their lakehouse and need consistent, governed metrics across multiple BI tools, ML pipelines, and APIs. When the semantic layer lives only in Power BI: Logic is duplicated across datasets and tools Governance/security (RLS/CLS, masking) is fragmented Schema changes in Databricks break reports ML/AI pipelines cannot reuse business logic from Power BI models Proposal: Enable native Power BI integration with Databricks Metric View ... View more

Currently, when a Power BI Gateway connection is created and authenticated ( using a Microsoft account authentication method via any user id/service account), there is no way to later identify which account was originally used for authentication, once the connection is created. In many organizations, admins configure gateway connections using service accounts. However, once the connection is created, Power BI does not provide visibility into: Which account was used to authenticate the connection There is no way we can figure this out via gateway logs or any other method. Note manage access only tells us who is having access to gateway conn. not the account using which the conn is authenticated. This creates challenges in governance, auditing, troubleshooting, and account lifecycle management—especially when service accounts change, passwords expire, or ownership needs to be transferred. Atleaset the id using which the account is authenticated should be visible or some option in admin portal to get this detail for each connection. ... View more

OpenLineage lets you trace a large number of ETL jobs that mutates tables, letting you trace changes to tables significantly easier. Databricks Unity Catalog has support for Column Level Lineage and it's highly useful: View data lineage using Unity Catalog - Azure Databricks | Microsoft Learn Databricks Demo   AWS also supports OpenLineage:  Amazon DataZone introduces OpenLineage-compatible data lineage visualization in preview | AWS Big Data Blog It's actually quite easy to get OpenLineage working in Fabric Spark since you already have the JAR pre-installed: Column level lineage in Fabric Spark with OpenLineage and stashing the lineage in Delta Lake | Raki Rahman   All we need is a way to store and query historical state (e.g. in Delta Lake), and a UI component that hooks into the Lakehouse catalog and offers an API on top of OpenLineage schema. The OneLake Catalog UI could look like this:       ... View more