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

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

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

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

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

We would like information on which characters are supported or valid for workspace names, in the documentation. There should also be a description that gives an overview of the valid characters for workspace names in the Power BI service when creating a workspace. ... 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

Dark Mode for Power BI Service and Fabric. ... 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

When I create a hierarchy in a table in a semantic model (Fabric), I can't see the hierarchy in a pivot table in Excel. I used this feature frequently with semantic models in PowerBI, and really liked it. ... View more

When I look at the Version History, I see only who made changes to the previous versions, but not who changed the current version: It would be very helpful to see, who was the author of the last changes. ... 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

Summary Add a simple UI to edit small Lakehouse (Delta) tables used for metadata, configuration, and reference/lookup data. Today, even trivial edits require Spark or SQL, which makes managing these simple tables more cumbersome.  Problem Many Fabric Lakehouse tables are: metadata (jobs, tasks, entities, config) small reference or lookup tables These tables are small, hand-maintained, and operational, not analytical. They often need minor row-level edits, but Fabric has no UI for this. Proposed Provide a grid-style editor UI: Read-only by default, explicit edit mode Edit / add / remove rows (with limits) Validation, confirmation, and audit logging Role-based access Edits commit as Delta ACID transactions. Why This improves operability and governance while avoiding ad-hoc notebooks and SQL ... View more

Considering the most powerful and versatile machines are being built on ARM processors and many developers preferring these machines due to the extended battery life, or performance per watt, I think it would be critical for Microsoft to start developing Power BI Desktop to be fully compatible with ARM64 processors. Windows ARM with a snapdragon processor is a great machine. It is where all machines are going. It's time for Power BI Desktop to get up to speed with everything else. ... 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

It would be really useful to have security settings to show or hide individual report pages. Currently, audiences control access only at the report level, not per page. ... View more

Request: The “Export Data” to excel option is currently hidden under the small three-dot menu on visuals, which is not intuitive and easy to miss for many users.   Suggestion: - Add a visible “Export Data” button on the visual or in the ribbon - Or provide a quick-access option for exporting data. ... View more

Want a metrics to show the consumption of artifacts when refreshed using Gateway. It should be shown in terms of how much of memroy is artifacts consuming for gateway not in cloud. ... View more

As a Fabric Admin, we noticed there are restrictions when it comes to accessing cloud connections throughout our Microsoft Fabric environment. Access is controlled by ownership and specific permissions, which means even Fabric Admins can’t view or manage these connections unless they’re given explicit access. This can make it challenging to troubleshoot, audit, or assist users in different departments efficiently. ... View more