Hi Community and Dev Team,   Currently, values in Power BI’s Table and Matrix visuals are always aligned to the top of the cell, this can make reports look unbalanced, especially when row heights are increased or when using visuals that combine text and icons.   I suggest adding a formatting option that allows vertical alignment (Top, Middle, Bottom) for cell values, similar to how horizontal alignment is already supported, this would give report designers more control over layout and improve readability.   Thank you in advance. ... View more

Currently, the Test as role feature in Power BI Service does not work for semantic models that use DirectQuery with SSO enabled. When attempting to validate Row-Level Security (RLS), the message “Test as role does not work with Single Sign-On (SSO)” appears. This limitation makes it difficult for developers and administrators to verify RLS behavior without involving end-users. ... View more

Summary: Power BI currently supports drilldowns (e.g., hierarchy-based navigation like Year → Quarter → Month) and drill-through pages based on filter context. However, there's no native support for "Drill Across" — a powerful feature in one of the well know BI enterprise tool that allows users to drill between unrelated attributes or columns, even if they aren’t part of the same hierarchy or table. Problem Statement: In many enterprise use cases, business users need to explore data laterally across unrelated dimensions. For example, from a "Product" summary, a user may want to drill into "Customer Region" or "Order Status" — attributes from entirely different domains or tables. This kind of exploration is not possible today in Power BI unless we create multiple drill-through pages with predefined relationships or use complex workarounds. Feature Request: Introduce native "Drill Across" capability that allows users to define custom drill maps or navigation paths between unrelated fields/tables — without relying on traditional hierarchy or model relationships. Similar to how MSTR allows: i)   Drill Up / Down (within a hierarchy) ii)  Drill Across (across unrelated columns/attributes) Benefits: 1. More flexible data exploration 2. Better user-driven analysis 3. Reduces the need for multiple drill-through pages 4. Aligns Power BI closer with enterprise-level BI features. Example Use Case: From a "Sales by Product" visual, a user could drill into "Customer Demographics" or "Shipping Status" — without needing to predefine all relationships or drill-through pages. Current Workarounds (Not Ideal): i) Creating multiple drill-through pages ii) Using bookmarks with filters iii) Modeling artificial relationships Conclusion: "Drill Across" would significantly enhance Power BI’s self-service capabilities and bring it closer to feature parity with other enterprise BI tools. Please consider adding this to the roadmap. ... View more

We would like to enable or disable the “A colleague shared a report with you one week ago” notification on a per-report basis. Currently, we have confirmed that this can only be managed at the individual user level or at the tenant level. ... View more

  The current inability to parameterize connections in pipeline activities means we need to use the same identity to run the pipeline activities across dev/test/prod environments.   This means the same identity needs to have write access to all environments dev/test/prod.   This creates a risk that code executed in dev writes data to prod, because the identity has write access to all environments.   Please make it possible to parameterize the connection of all pipeline activity types, so we can isolate the identities for dev/test/prod and make it physically impossible for a dev pipeline activity to write data to prod environment.   Here's an overview based on my trials and errors:   Activities that do have "Use dynamic content" option in connection:   - Copy activity  - Stored procedure  - Lookup - Get metadata - Script - Delete data  - KQL   Activities that do not have "Use dynamic content" option in connection:   - Semantic model refresh activity  - Copy job - Invoke pipeline - Web - Azure Databricks  - WebHook - Functions - Azure HDInsight  - Azure Batch  - Azure Machine Learning ... View more

Currently, Power BI does not provide a way to change the owner of a Dataflow via the REST API. This limitation creates challenges in scenarios where ownership needs to be transferred due to organizational changes, role transitions, or automation requirements. Having the ability to programmatically change the owner of a Dataflow would improve governance, reduce manual intervention, and support enterprise-level management of Power BI assets.   Use Cases: Automating ownership transfer when users leave the organization or change roles. Assigning ownership to service accounts for better control and monitoring. Enabling centralized management of Dataflows in large environments.   Impact: This feature would enhance administrative flexibility and support better lifecycle management of Dataflows, especially in enterprise scenarios where automation and governance are critical. ... View more

when a Power BI embed report remains idle overnight or for several hours,it takes some time to load the data which impacts user experience—especially for reports that need to stay open for monitoring purposes. ... 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

Currently, when using the semantic model UI at 100% zoom on smaller screens or lower resolutions, table fields are not visible, making table selection impossible. Reducing zoom (e.g., to 80%) or using a higher-resolution display resolves the issue, which indicates a UI scaling and responsiveness limitation. ... View more

Currently, parameters defined in a Fabric Notebook’s “Parameter Cell” need to be manually re-entered when creating or editing a Fabric Data Pipeline. This manual process increases the risk of typos and inconsistencies, especially in larger projects with multiple notebooks and environments.   Idea: Enable Fabric Pipelines to automatically detect and import parameters directly from the “Parameter Cell” of a referenced notebook. This would: Eliminate manual parameter duplication Reduce the risk of errors Improve development efficiency and maintainability   Suggested Solution: 1) Define parameters in parameter cell   2) In Pipeline while configuring the Notebook activity, let it import the parameters by click:   3) Set type and default value based on the entries in the notebook:       ... View more

Description Currently, Dataflow Gen2 in Power BI does not allow refresh operations on flows targeting a Warehouse unless the user performing the refresh is the owner of the dataflow. Even users with full workspace permissions (Admin/Member) and Fabric capacity rights cannot refresh unless ownership is transferred. This limitation creates operational challenges, especially in enterprise environments where multiple users manage refresh schedules. In contrast, when the destination is a Lakehouse, refresh works without requiring ownership transfer, which is the expected behavior. Proposed Enhancement Allow any user with sufficient workspace and Fabric permissions to refresh Dataflow Gen2, regardless of ownership. Ensure consistent behavior between Lakehouse and Warehouse destinations. Optionally, introduce a service principal or delegated refresh capability for automation and enterprise scenarios. ... View more

Currently, Microsoft Fabric provides the ability to manage access to Copilot and Azure OpenAI-powered features at the Tenant and Capacity levels using the following setting: “Users can use Copilot and other features powered by Azure OpenAI” As a Fabric Administrator, I’m requesting an enhancement to allow Copilot access control at the Domain level. This additional layer of granularity would empower organizations to roll out Copilot features in a more secure, targeted, and manageable way—especially in environments with multiple business units or domains that have varying readiness levels or compliance requirements. Implementing domain-level controls would help accelerate adoption while maintaining governance and minimizing risk. ... View more

While Copilot has a lot of potential, developers recognize that there is a significant amount of work that needs to be done to make a report "Copilot friendly".  In organizations with a large Power BI footprint with hundreds or thousands of reports and models, this could result in significant work.  If this work is not done and Copilot is turned on, results that appear accurate are not and could lead to wrong decisions being made.  This leads to a lack of trust in the feature and worse, lack of trust in the report developers.     By allowing for more granular control of where Copilot is deployed, developers can choose what reports are Copilot ready and do the work (model optimization, prompt engineering) to ensure high quality responses.  ... View more

When deploying from Dev/Non-Prod to Prod, the target’s pipeline schedule is overwritten. Please add deployment rules (or an opt-out) so schedules can be environment-specific without showing as drift in comparisons. This avoids Prod cadence being reset and reduces capacity burn in Non-Prod. ... View more

New Desktop app update installed an almost white user interface. There is zero contrast which is not good for the eyes. I see where some people have requested a light interface so incorporate an option to select either light or dark theme like in the Office apps. ... View more

Similar to the Monitor page, where we can see what has run and what is currently running, it would be useful to see what's scheduled to run in the future. This to check that all schedules are set up as expected.   Reason: Easy and conveniently verify that all schedules are configured as expected. ... View more

Matrix visuals could significantly enhance the user experience by emulating Excel's intuitive sorting, searching, and filtering capabilities, even for hierarchical columns. This idea would the current limitation in Power BI's matrix visuals, which lack a comparable experience to Excel's established standard for data manipulation. ... View more

Multiple users are looking for a ways to connect an MS Project desktop file (MPP) to Power BI without using Export to Excel or PWA so if we have any connecter for this it would be helpful   ... View more