We need support for Service Principal authentication when creating Lakehouse connections.   Right now, Lakehouse connections can only be created using a user account. As a result, Dataflow Gen2, Pipeline copy activity, and Copy Job cannot use a Service Principal (SPN) when connecting to a Fabric Lakehouse as a source or destination.   This is an issue for us. We want to avoid user-based connections because: We need environment-specific identities (dev/test/prod) to prevent accidental cross-environment writes (e.g., dev pushing data to prod). Tying connections to personal user accounts creates fragility - things break when someone leaves the project or the organization. Service Principal support for Lakehouse connections is required to ensure secure, reliable, and environment-isolated authentication.   The screenshot shows that only user authentication is available, not service principal authentication. ... View more

Need Power BI rest api which list all data sources from all the sematic model at tenant level ... 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

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

Anyone who uses PowerBI long enough has had a PBIX with 50-60 measures and it has become time consuming and tedious to mantain. In Excel you can do a quick find/replace to edit several formulas - in PowerBI you need to select each one individually. An "excel-like" interface for editing measures would save a lot of time! This would take PowerBI to the next level regarding productivity. I've prepared a mockup for this as well as a DAX Editor. Let me know what you think. Mockup: https://i.imgur.com/z6TBOQb.png?1 ... View more

“Please add back the ability to align values (center/left/right) in Matrix visuals globally under Format → Values. Currently, alignment is only available under Specific column, which makes it hard to apply consistent alignment across all value columns.” ... View more

According to the documentation (https://learn.microsoft.com/en-us/power-bi/developer/visuals/enable-sync-slicers) and Microsoft's custom visuals support, syncing slicers is only supported by single-field visuals: The sync slicers feature only supports one field at a time. If your slicer has more than one field (Category or Measure), the sync slicers feature is disabled.   As a custom visuals company who, more often than not, uses filtering in our visuals, we would like them to be able to sync accross pages just like normal slicers do, but our visuals are never single-field. Moreover, we do not see why syncing by a single field could not be possible in a multi-field visual as long as that single sync field is selected; therefore, we would like to suggest voting for this idea to enable everyone make custom visuals more versatile (or rather, catch up with single-field slicers). ... 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

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

Currently, I am not able to create my multi-statement table-valued functions in Fabric Warehouse and SQL anlalytics endpoint. I would like to be able to do that w/o needing to do a code change. ... View more

Need a tool that can provide detailed information on which queries or DAX commands are being run by specific users, including the duration of each query, on their Power BI embedded capacity during times of CPU or capacity spikes. This will help us quickly identify the root cause of these spikes. ... View more

To fix inconsistencies in analytic settings, functionality needs to be enhanced to ensure they are on par with other visual component enhancements made for Cartesians, and additional settings for scatter charts is also necessary. Report creators will find it easier to format and customize settings to align with the overall look and feel of their reports. ... View more

We're using Power BI Embedded in the App Owns Data scenario in our web application. In the Embedded Analytics Playground we can see Export Visual Data Summarized Export Visual Data Underlying What we *need* is to be able to call "Export Visual Data with Current Layout" as is provided by the built-in Export Data options menu item, but without making the user of the embedded application go through the UI (and also be able to style the dialog we present, add logging of who exported what etc. etc.) Is this API available, but no documented? Is there some trick that we can use to invoke whatever the built-in export does?   ... View more

Hi,   The new Office 365 Email Fabric Connection that is required to run a new Office 365 Email in an activity using Service Principal authentication cannot be shared. I get that should be the case for OAuth authentication connections with individual user accountsfor security reasons.   New Office 365 Email Activity         This causes us issues becasue we are using git and branched workspaces. If a connection is not shared with other workspace users then when people branch out to their workspace, artifacts with unshared connections cannot load. Hence, why we are still using the old Email activities. I've just noticed today that the old Email activity is no longer available in pipeline activitiy options. When will the legacy version be going completely, please? And before it goes, will there be any updates to the new Email connection to make it sharable? In the mean time, are there any other options?   Thanks. ... 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

Dark Mode for Power BI Service and Fabric. ... View more

Introduce an “Export Visual Data as Rendered” option that guarantees the exported dataset matches the visual exactly, including all applied filters, measures, and formatting. ... View more

When adding columns to a Matrix I always want the headings to align above the numbers ( i.e. to the right ).    This should be the default in my view Per bottom visual of screenshot   ... 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