We would like the option fo Autoscale for Power BI using Fabric. We have been using Fabric for approximately 1 year and just hit our first outage. It is quite frustrating that we have no alternatives but to wait for it to come back (so that we can then begin our troubleshooting). The metrics app does not work. We keep getting emails to enable autoscale, but it does not appear to be an option for Fabric. We would really like to take advantage of Autoscale if we could. Thanks! ... View more

Users working with reports occasionally encounter the error “Query exceeded memory limit.” However, report creators have no way to determine which specific query caused the memory limit to be exceeded. It would be helpful to have a feature, such as in Fabric Capacity Metrics, to identify which queries caused the memory limit to be exceeded. ... View more

Currently, OneLake Security Roles must be configured individually within each Lakehouse. For organizations managing multiple Lakehouses based on data domains, this results in significant manual effort and duplication. Additionally, maintaining both Active Directory (AD) groups and separate OneLake Security Roles adds complexity and increases the risk of misalignment. ... View more

Currently, the Power BI Service does not include the prophet package in its supported Python environment. This limitation prevents users from running advanced time-series forecasting workflows in published reports using Python visuals. Adding prophet and its required dependencies would enable seamless forecasting directly in the Power BI Service, ensuring consistency between Desktop and Service and reducing reliance on external workarounds. ... View more

I need to conditional format the row header, not just the values section.   Also I would like to be able to format the font in bold/italic and be able to define complete rows (values including row headers) to be underline/overline. ... View more

Today, only Oauth 2.0 (user account) is supported as authentication option when setting up an Azure Key Vault reference.   Please add support for Workspace Identity  Service principal User assigned managed identity ... 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

As part of enabling Change Data Feed (CDF) on Fabric mirror databases, please consider exposing the Delta Lake table_changes table-valued function so that it can be invoked directly through the Lakehouse T-SQL endpoint. This functionality would allow users to query incremental changes using familiar T-SQL syntax, improving integration with downstream systems and simplifying change tracking workflows.   Example Usage: -- Retrieve changes since version 2 SELECT * FROM table_changes('myschema.mytable', 2); -- Retrieve changes since a specific timestamp SELECT * FROM table_changes('myschema.mytable', '2025-11-14T12:00:00.000+0000') ORDER BY _commit_version;   Why this would be helpful: Enables consistent access to CDF data without requiring Spark or Python. Supports real-time analytics and ETL scenarios using standard SQL tools. Aligns with Fabric’s goal of providing unified query experiences across engines. -> Fabric-Ideas/Enable-Change-Data-Feed-CDF-on-a-Mirror-Database/idi-p/4500759 ... 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

Power BI needs a way to move gateway connections between gateway servers without having to recreate on the new server each time. As a large enterprise running Power BI, we have many gateway clusters that are now being capped at the 1,000 connection limit, forcing our users to constantly shuffle connections around to other gateways. We need the ability to change the drop down for gateway cluster in the connection settings and relocate it easily without having users recreate the connection and delete the old one. ... 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

The amount of compute which is charged for writebacks via Power Apps / UDF is not equal to the amount seen in the performance summary of the Fabric database and in general way to high. It becomes hard to understand what is causing CU spikes. We were told that because of the serverless architecture initial writes / reads take a couple of seconds (apx. 30s) to turn on the backend. After 15 min without interaction it scales down again. There is no way to see nor configure the compute usage of this. We would like to have more control in the process so simple write backs do not consume a ton of compute just for spinning up the server every time. Another big downside is that the end user need to wait a significant amount of time. Every UDF also needs to spin up if it was not used for 15 min.  We have an F4 Fabric Capacity in which we have created SQL DB workload. We also have a Power BI report in which a Power App is embedded. Power App reads data from SQL DB.   Every time end user interacts with the Power App, we see a spike in Capacity Metrics App.     It consumes almost half of the F4 capacity when Power App starts to read data from SQL DB.   This number is not aligning with the performance summary of the Fabric database. The memory tab only shows mb not compute usage.  ... 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

Problem Today, in Fabric Deployment Pipelines, a user must have Contributor access in all stage workspaces (Dev, Test, and Prod) to perform deployments.   This design means the same user identity has read and write permissions across every environment, which creates unnecessary risk. A user could accidentally read data from Dev and write it to Prod, or the other way around.     Proposed Solution Allow deployments between stages to use isolated identity connections, such as:   Service Principal Workspace Identity Managed Identity   This would let a user act as an orchestrator of deployments, rather than the identity that actually performs the writes. The user would no longer need Contributor access in all workspaces - only User access to the defined identity connections that handle deployments on their behalf.   Suggested Implementation When configuring a deployment pipeline, users could select an identity connection (Service Principal, Managed Identity, or Workspace Identity) in the user interface.   The selected identity must have at least Contributor access in the target (destination) workspace.   Users could select a different identity connection for the source workspace, allowing for complete isolation between Dev, Test, and Prod.   Each environment could therefore have its own dedicated identity, ensuring watertight separation between stages.   The user account itself would typically still be Contributor in Dev (for development work) but only User on the Test and Prod deployment connections. This maintains convenience for deployments while preventing direct modification of production resources.   Example: SPN_dev (Contributor in Dev) SPN_test (Contributor in Test) SPN_prod (Contributor in Prod) The user (me) doesn't have Contributor access in the workspaces. I only have User access on each SPN's Deployment Pipeline connection. This means, I can trigger deployments without having Contributor permission in the workspaces myself.   Of course, if I don't have User access on each SPN's Deployment Pipeline connection, I will not be able to deploy content to the workspaces. This is how we will ensure that no unauthorized users can use the deployment pipeline.   What are the actual changes? At it's core, this proposal introduces two changes (new features): The concept of shareable Deployment Pipeline connections. (Inspired by data source connections). The ability to use separate identities (separate deployment pipeline connections) for the source and target stage, in order to orchestrate the deployment across stages - without a single identity having Contributor permission in both workspaces. ... 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

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, colors are automatically assigned randomly.  It would be nice if your dev workspace was always blue, and your prod was always pink for example.  Then you'd have a good visual as to where you're working in. ... 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