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

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

Power BI reports currently do not fully meet WCAG 2.2 AA requirements for Use of Colour (1.4.1). Data visualizations rely on colour alone to convey meaning (ie. identify categories or data types). While data labels can be applied to address this, the labels are presented via tooltips, which are not fully accessible due to other issues (keyboard navigation and hover behavior). Impact: This creates a significant barrier for users who cannot perceive colour and rely on keyboard navigation and/or hoverable behavior in tooltips, preventing them from accessing all report content. It also means reports cannot achieve WCAG 2.2 AA compliance. Request: Please provide built-in options to include accessible alternatives to colour coding, such as patterns, shapes, or persistent text labels within visuals. This change would help ensure Power BI content meets WCAG 2.2 AA standards and supports accessible digital services. ... View more

Power BI reports currently do not fully meet WCAG 2.2 AA requirements for Content on Hover or Focus (1.4.13). When additional information appears on hover (e.g. tooltips), users cannot move the pointer over this content without it disappearing. If a user is zoomed in (particularly when using smaller screens), they may need to scroll or pan to view the entire content, which can be impossible unless the user can move their pointer off the trigger without the content disappearing. Users utilizing particularly large pointers may also need to be able to hover over the content without it disappearing if, when positioned on the trigger, the pointer partially obscures the content. Impact: This creates a significant barrier for users who need to zoom in and/or use large pointers due to vision impairments, preventing them from accessing all report content. It also means reports cannot achieve WCAG 2.2 AA compliance. Request: Please enhance Power BI so that hover-triggered content can be hovered over without disappearing. This change would help ensure Power BI content meets WCAG 2.2 AA standards and supports accessible digital services. ... View more

Power BI reports currently do not meet WCAG 2.2 AA requirements for Reflow (1.4.10). At screen resolution 1280 x 1024, when users zoom in up to 400%, the content does not adapt to a single-column layout. Instead, users must scroll both horizontally and vertically to access information. Impact: This creates a significant barrier for users who need to zoom in due to vision impairments - they can lose their place and must expend more physical and cognitive effort accessing the content. It also means reports cannot achieve WCAG 2.2 AA compliance. Request: Please enhance Power BI so that published reports can reflow responsively without loss of information or functionality when zoomed. This change would help ensure Power BI content meets WCAG 2.2 AA standards and supports accessible digital services. ... View more

Preview feature options are showing in local language set in laptop instead of showing the options in the language set in application level in Power BI desktop. This needs to be changed the preview features must be shown in language which is set by customer in Power BI desktop instead of considering the languag used in local machine. ... View more

It would be really helpful if we have an option to recover the deleted artoifcats like data model in power bi service. ... View more

For the reports using Visualize your data quickly from Power Apps/ Dynamics 365 apps feature should be able change the visual type. ... View more

I would like to have auto detect of relationship in the semantic model that is created within the Microsoft Fabric.  This feature should be on par with that we have in Microsoft Power BI to enable end users or data users to be able to create model in the Microsoft Fabric workspace.  Right now there is no option to enable it online when connecting several tables in a lakehouse.   Functionality across Microsoft Power BI & Fabric should be same or similar, if end user plan to migrate from Power BI Capacity to Fabric Capacity. ... View more

Please add the ability to rename the display label for measures used in the "Reference labels" and "Detail" sections of a Card visual. This small change would significantly improve report clarity and user experience. It allows developers to present cleaner, more user-friendly labels. ... View more

Power BI reports currently do not fully meet WCAG 2.2 AA requirements for Info and Relationships (1.3.1). While it is possible to add visible headings, there is no way to apply a proper heading hierarchy programmatically. For example: There is no option to apply heading 1 formatting to the main text heading (ie. nest it within an h1 HTML element). Heading tags (h1-h6 HTML elements) can only be applied to entire text boxes, not specific text within them. A 'Power BI Report' visually hidden heading 2 (h2 HTML element) is automatically inserted and cannot be edited or removed. Impact: This creates a significant barrier for screen reader users, preventing them from reliably identifying and navigating using headings. It also means reports cannot achieve WCAG 2.2 AA compliance. Request: Please provide full support for semantic heading structures in Power BI reports, including the ability to apply heading levels (H1–H6) to individual text elements. This change would help ensure Power BI content meets WCAG 2.2 AA standards and supports accessible digital services. ... View more

At present, Power BI sets “Grow to fit” as the default setting for tables, which often proves impractical because columns take more room than needed. This can be adjusted case-by-case by selecting “Fit to content” (Format → Column headers → Options).   I would love to see this introduced as a higher-level setting at the global, report, or theme level. It would eliminate the need to adjust every table individually and allow users to decide which default column-width behavior should be applied to their tables and matrices.   Current Default setting - Grow to Fit Lots of white space unless adjusted manually After a manual adjustment - Fit to Content Less white space, neather table     ... View more

Secondary axes are automatically managed by the system in some cases, making it problematic for report creators with no control over intervals, ticks, and other crucial components, limiting effectiveness of various types of analysis. It would be great if the secondary axis included comprehensive format settings so that greater control over displayed data is provided. ... View more

Currently the ability to use time travel in directlake models is not available. I need to be able to connect to the Base deltalake table folders and access cdc functionality to use version as of functionality to return time travel data as fast as possible on the fly. This is currently not supported.  ... 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

Please make it possible to run a notebook as the Workspace Identity, instead of running as a user identity.   This means the notebook (and the notebook's security context, i.e. the notebook's authentication to data connections) will not depend on any single user but use the Workspace Identity instead. ... View more

Create user permissions options on workspace folders to avoid creating multiple workspaces or granting access on a report-by-report basis. ... View more

As a large enterprise managing thousands of Power BI gateway connections across multiple clusters, we frequently encounter a significant operational challenge due to the current 1,000 connection limit per cluster. This limitation necessitates the manual recreation of data sources and rebinding of datasets when exceeding capacity, leading to a time-consuming and error-prone administrative process. We request a feature that enables Power BI administrators to seamlessly reassign existing data sources between gateway clusters. This functionality should be accessible via a user-friendly dropdown or bulk operation within the Power BI Service or Admin Center, eliminating the need to recreate connections from scratch on a new cluster. ... View more

Implement a Git difference view to show the changes made against the commited. Currenly it shows what modified and new but noway to know what changes we made. ... View more