The primary axis are outdated and require significant improvement when compared to Excel. This makes it difficult for report creators and often leads to problems when trying to manage and style them effectively. By offering more format settings, greater control over displayed data can be provided, especially if axis ticks, new gridlines, and separators are also included. ... View more

If we recreate an artifact in the workspace and commit both the add and delete actions at the same time, the artifact will save the logical ID. Users expect this process to delete the initial artifact and create a new one with the same name, instead of having to manually perform a delete commit first and then an add commit. ... View more

One of the most annoying behavior of report designers is to rename fields in visuals in cryptic way without standards and you won't understand at a first sight which field from which table had been used.     AFAIK (without using any external tool or power bi project - just staying in PBI Desktop), the only thing you can do is to hover fields with the mouse and look at the tooltip that shows you the original field/measure home table and name. for further anlaysis you need to move to the data pane and search it manually. Wouldn't it be nice to have a "Go to definition" that points the referenced field/measure in the data pane that you can activate directly in the context-menu right-clicking the field?     ... View more

I know Explore and Org Apps are still in preview, but if Org Apps do not have explore immediately on the selected report, they lose a lot of their usefulness.   Please make sure that Explore feature is also included in Org Apps UI the same way as it is currently in ordinary Workspace Apps. ... View more

We need to subscribe base on the report type. For example, subcribe for paginated reports and normal reports.  ... View more

OpenLineage lets you trace a large number of ETL jobs that mutates tables, letting you trace changes to tables significantly easier. Databricks Unity Catalog has support for Column Level Lineage and it's highly useful: View data lineage using Unity Catalog - Azure Databricks | Microsoft Learn Databricks Demo   AWS also supports OpenLineage:  Amazon DataZone introduces OpenLineage-compatible data lineage visualization in preview | AWS Big Data Blog It's actually quite easy to get OpenLineage working in Fabric Spark since you already have the JAR pre-installed: Column level lineage in Fabric Spark with OpenLineage and stashing the lineage in Delta Lake | Raki Rahman   All we need is a way to store and query historical state (e.g. in Delta Lake), and a UI component that hooks into the Lakehouse catalog and offers an API on top of OpenLineage schema. The OneLake Catalog UI could look like this:       ... View more

Currently, when creating connections for Trusted Workspace Access via Manage connections and gateways, the only supported authentication method is Workspace Identity. Attempts to use Organizational Account or Service Principal authentication result in failed test connections it will be usefull if Organizational Account and Service Principal Authentication are supported for Trusted Workspace Connections ... View more

Hi We have F256 capacity and we have recently purchased 64 SKUs. Unfortunately, there is no way for us to upgrade the capacity by 64 SKUs, but rather can only jump to the next available one, in your case is F512. This is not feasible option. Provide an option to upgrade the capacity with multiples of 64 SKUs. ... View more

Now that Fabric Warehouses support the MERGE T-SQL consturct, it's high time to get Pipeline Copy Data activity to support the UPSERT option for the Destination settings when writing to a Warehouse table.   This has been available for Lakehouse destinations for a while, albeit still in preview.    Please make this available for Warehouse tables as well.   And while you're at it, make it availalbe for Dataflow Gen2 Data Destinations.   This is CORE Functionality that should have been part of the product 18 months ago! ... View more

It’s challenging and time-consuming for both new and experienced report creators to organize data when trying to split cards into categories. By introducing small multiples, it could be a familiar and easy way for report creators to intuitively categorize data, especially if they had more control over layout and formatting. ... View more

When Power BI reports are embedded in SharePoint Online using the Embed web part (iframe), URL filter parameters work correctly. However, users are frequently prompted to sign in again, or are redirected to a new tab or window for authentication.   This occurs even when: Users are already signed in to SharePoint Online Users have valid Power BI licenses The report is hosted within the same Microsoft 365 tenant   As a result: Users experience repeated authentication prompts Login opens in a separate tab/window The embedded analytics experience feels broken and disruptive Business users find this confusing and frustrating   In contrast, the native Power BI web part provides smoother authentication and SSO behavior — but does not reliably support URL filters. This forces customers to choose between: Correct filtering behavior (Embed web part) Seamless SSO experience (Power BI web part)   This trade-off should not be necessary.   Requested enhancement: Please enable seamless single sign-on behavior for Power BI reports embedded via the SharePoint Embed web part, without repeated login prompts or new-tab authentication flows.   This would make iframe-based embedding a viable and user-friendly option for enterprise deployments that rely on URL-based filtering and dynamic report context. ... View more

When you click a visual in Power BI Desktop, it would be really useful to have an option to show only the fields/measures used by that visual in the Fields pane.   At the moment, even with a visual selected, the Fields pane still shows the entire semantic model. In larger models (or when working with shared datasets), it’s hard to quickly see: which tables are involved which columns or measures the visual is actually using   I’d love a simple toggle in the Fields pane, something like: Show all fields Show fields used by selected visual     This would make it much easier to: understand existing reports work with inherited/shared models debug or refactor visuals onboard onto someone else’s report   Feels like a small UX change that would save a lot of time day to day. ... View more

[ Behavior ] Depending on the order of the transformation steps, this can result in a subquery that requires a full scan.   // Narrow down the columns at the end M Query : #"Filtered Rows" = Table.SelectRows(SalesLT_Product, each ([Color] = "Black")), #"Removed Other Columns" = Table.SelectColumns(#"Filtered Rows",{"ProductID", "Name", "Color"})   Native Query : select [_].[ProductID],     [_].[Name],     [_].[Color] from [SalesLT].[Product] as [_] where [_].[Color] = 'Black' and [_].[Color] is not null   // Narrow down the columns at the first M Query : #"Removed Other Columns" = Table.SelectColumns(SalesLT_Product,{"ProductID", "Name", "Color"}), #"Filtered Rows" = Table.SelectRows(#"Removed Other Columns", each ([Color] = "Black"))   Native Query : select [_].[ProductID],     [_].[Name],     [_].[Color] from (     select [ProductID],         [Name],         [Color]     from [SalesLT].[Product] as [$Table] ) as [_] where [_].[Color] = 'Black' and [_].[Color] is not null   [ Request ] This is due to the folding feature. While the goal of the folding feature has been achieved, there seems to be room for improvement in the process by which optimal queries are generated. We would appreciate it if you could improve the optimization behavior to prevent bottlenecks on the data source side as much as possible, especially for data sources within Microsoft.   Understanding query evaluation and query folding in Power Query - Power Query | Microsoft Learn The goal of query folding is to offload or push as much of the evaluation of a query to a data source that can compute the transformations of your query. ... View more

Problem: Developers and reviewers with edit permissions frequently open notebooks for reading. Notebooks currently open in edit mode with autosave, which causes accidental changes and noisy version history. Request: Open notebooks in View‑only mode by default, or at least add an option (user preference or workspace/tenant policy) to open notebooks in view-only mode.  Edit mode should require intentional button click. Benefits: prevents accidental edits, reduces accidental autosaves, safer review workflows, aligns Fabric with other notebook UX patterns (view-first), prevents false "notebook has been updated" triggers in IDE. ... View more

Currently, there is only REST APIs to add users to the dataset(semantic model)'s direct access.   To add users, please refer to the API: Datasets - Post Dataset User - REST API (Power BI Power BI REST APIs) | Microsoft Learn To add user in groups, please refer to the API: Datasets - Post Dataset User In Group - REST API (Power BI Power BI REST APIs) | Microsoft Learn   User needs REST API to add users to the report's direct access. This function is needed for automation of adding users to report's direct access.     ... View more

Hello Team, We are requesting you to consider the feature were delays of refreshes in power bi service can avoided as we see that it is a by design behavior in service. As of now customers are trigerring refreshes with ADF. Thank you. ... View more

Power BI currently clears selections in one table visual when a selection is made in another, preventing independent multi-visual filtering. Requesting a feature that allows table (and matrix) visuals to retain their own persistent selections so users can click a row in multiple visuals and have all selections remain active simultaneously. This would enable combined filter context across visuals without requiring Ctrl‑click or merging data into a single table. ... View more

We are attempting to deploy the semantic model from the Dev stage to the Test stage, but we are encountering an error stating that the dependent artifacts must be deployed first to the target stage. In our case, some of these dependent artifacts are in different workspaces and have different owners, which makes this requirement impractical in many scenarios. If this restriction could be removed, it would make working with the deployment pipeline much easier. ... View more

The only way to update a group name is to double mouse click the name.  Would be good to have the normal other ways to perform this action available too :} So option in the Groups popup and right mouse menu functionality needs to be added. Suggested improvements Add Rename to right‑click menu OR allow F2 to rename OR show an inline edit icon (✏️) Tooltip hint on hover (“Double‑click to rename”) Links Table view tab > Data pane > Edit Groups | needing option and/or right mouse menu for name change   (my forum post) Naming groups   (past forum post with same issue)   ... View more