The Line + Column Combo Chart has been out for a while. It is time that the Bar charts also gets the option to add a line - or change the original combo charts so that they can be used either horizontally or vertically. ... View more

It would be great if there was an option to combine the stacked AND clustered column/bar charts to use both options. This way we could stack (for example by product group) and cluster (to display budget or previous year vallues) for maximum information density. ... View more

When we use the Top N filter, it would be great if there was an option to check "Show others" which would then group all the elements that are not within the range and show them as a single item.   Example: Product A has 20M Net Revenue Product B has 10M Net Revenue Product C has 5M Net Revenue Product D has 1M Net Revenue Product E has 0.5M Net Revenue   if I do a "Top 3" filter I get: Product A - 20M Product B - 10M Product C - 5M   With the "add Others" toggled on there would be one additional row: Others 1.5M ... View more

Feature Request Allow report owners or admins to disable PDF/PowerPoint export at the individual report level, rather than only at the tenant or security group level.   Problem A customer has Power BI reports containing confidential training materials that should not be exported as PDF/PPT to prevent data leakage (especially after employee offboarding). However, their other data analytics reports still need export functionality. Today, the "Export reports as PowerPoint presentations or PDF documents" tenant setting is all-or-nothing — it applies to all reports for a given security group. There is no per-report granularity. Alternatives like Microsoft Purview sensitivity labels or Power BI Embedded are not feasible for this customer due to licensing and organizational policy constraints.   Proposed Solution Add an option under Report Settings → Export (similar to the existing "Export data" control for Excel/CSV): Allow export as PDF/PowerPoint (default) Don't allow export as PDF/PowerPoint for this report Optionally, support restricting export to specific security groups per report.   Impact This would help organizations that handle mixed-sensitivity content across reports and need granular export control without additional licensing. ... View more

Power BI has supported outlined and overlapping columns for a while now, which is great. I believe that at the last IBCS conference in 2025 there was also a teaser that IBCS (or the new ISO 24896 norm) would be fully supported by native PBI in the future. The minimum requirement for this would be hatched bars/columns to represent Forecast values.   More info on the IBCS standards: IBCS - International Business Communication Standards ... View more

We would like a feature to edit user permissions on a per-folder/item basis within a workspace. as now, we can edit user permission per a workspace, but if we could set it for each items, it would be more useful ... View more

Currently, when the Lakehouse schema is enabled, it doesn't allow to create under the workspaces with titles containing non-ASCII characters. We would like to request support for this ... View more

In some cases, we need to apply the same changes to multiple pipelines. For example, when introducing parameters to existing pipelines, a UI feature is required that enables applying the same changes across multiple pipelines simultaneously. ... View more

In working with Git/DevOps it would be a much simplified process if users could see version history for Git committed objects in the Fabric Workspace UI, and be able to revert back to a previous commit state from that version history list.   In a conversation with Copilot, such a process was very elegantly hallucinated as a solution, though it does not actually exist in functionality in the Fabric Workspace.   Here is Copilot's solution (in my conversation I was using semantic model as the example but the same steps should apply to any objects that are Git-managed):   To perform an official Fabric-supported restore, you must use the Fabric workspace Git panel. ✅ How to restore a previous version of the semantic model (Fabric UI) Go to your Fabric workspace Select the Git icon/pane on the left Choose View commit history Find the commit you want to restore Click Restore this version to workspace This will: overwrite the semantic model in the workspace update the report if needed reflect the Git state of that commit NOT affect Git history (it doesn’t rewrite anything) create a new commit after you sync back to Git ... View more

I have created an alert and was editing it in Power Activator.  I want to create an URL in the alert that the user can use to navigate to a report page filtered on a field in the alert.  The url gets created as expected, however the field reference (DEALER ID) adds spaces in front and after the reference so the url breaks.  Here is an example of what I see in the emailed alert.   ...filter=Dealer_x0020_Attributes%2FDealer_x0020_ID%20eq%20%27 HAQ %27   If I remove the spaces, the url works as expected.  Below is what the alert looks like in Activator.     Any thoughts on how to remove the spaces so the user can just click on the link in the email alert?   Thank you.   ... View more

Hi, When accessing Power BI reports via the Web on desktop, the layout does not adapt to different screen sizes. Users working on large monitors (2K, 4K, UltraWide) should be able to see more rows in tables and more content on the canvas without excessive scrolling. Currently, the report keeps the same fixed layout regardless of resolution. It would be great to have automatic responsive behavior, allowing visuals and grids to expand dynamically based on available screen space. This would significantly improve usability and productivity for users working with large datasets. ... View more

The Input Slicer (formerly Text Slicer) is now Generally Available and is explicitly positioned for Translytical / writeback / user input scenarios in Fabric. However, the Input Slicer cannot be created in the Power BI Service authoring experience. It is only usable if it was created beforehand in Power BI Desktop. This creates a hard blocker for Service‑only and Fabric‑first teams: Installing and maintaining Power BI Desktop only to add a single visual contradicts the Service‑first model Desktop usage introduces local dependencies, version drift, and governance exceptions Tenant settings do not allow enabling the Input Slicer as a built‑in visual (it is not an AppSource visual) As a result, a GA feature that is core to Translytical scenarios is not usable in a Service‑only environment. The Input Slicer should be available in the Visuals pane when authoring reports in Power BI Service ... View more

Often when I am writing queries I end up having multiple queries within the same script in Fabric Warehouses/ Lakehouse SQL endpoints. This results in this nice dropdown for navigating between each of those queries but as more queries are included in the script, it gets to be a lot. Currently I leave comments in my code like "Result 1: Query Subject" but that means I need to track down which query is which still and if I reorder the queries then I need to update the query numbers. What if there was a command or a wrapper that could be a flag to name these something set by the user (or dynamically) so that it would be easier to click through results?   ... View more

As part of the new Recent data module, I would also like to see Recent Connections so that I can connect to another table from the connection I just used. ... View more

Problem Description When using Microsoft Fabric Data Factory’s Copy Activity with an OData v4 source, any column defined as an enum type in the OData service is silently dropped during schema inference and data ingestion. This occurs because Fabric Copy Activity performs strict metadata‑based type validation and only materializes properties that map directly to supported primitive types. Since OData enums are logical types rather than primitive scalars, they are excluded from the inferred schema. This behavior results in incomplete datasets, unexpected data loss, and inconsistent ingestion outcomes—especially for systems that rely heavily on OData metadata and enum‑based domain modeling. Expected Behavior Power BI, which uses the same OData v4 metadata document for schema discovery, successfully handles enum types by gracefully coercing them into strings when no native type mapping exists. This demonstrates that a metadata‑driven fallback is technically feasible and consistent with Microsoft’s broader OData tooling ecosystem. The expected behavior for Fabric Copy Activity is to follow the same principle: If an OData enum type cannot be mapped to a native Fabric type, Automatically fall back to string, Instead of dropping the column entirely. Why This Matters Many enterprise OData services rely on enums to model business concepts such as status, category, priority, workflow state, and other domain‑specific classifications. Losing these fields during ingestion creates several issues: Data loss: Critical columns disappear without warning. Broken lineage: Downstream transformations and semantic models cannot rely on stable schemas. Inconsistent behavior: Power BI and Fabric interpret the same OData metadata differently, causing confusion for users who expect parity. Workarounds are impractical: Switching to Web API is not viable because it lacks metadata, type information, and relational structure required for OData‑based ingestion. Requested Enhancement Implement a fallback mechanism in Fabric Copy Activity so that: OData enum types are automatically materialized as string columns. Schema inference remains metadata‑driven and predictable. No columns are silently dropped due to unsupported logical types. Benefits to Microsoft Fabric Users Consistent behavior across Microsoft products (Power BI and Fabric). Improved reliability of OData ingestion pipelines. No unexpected schema loss, reducing operational risk. Better support for enterprise OData services, which frequently use enums. Reduced need for custom workarounds, manual schema overrides, or alternative APIs.   Thank you for reading 😉 ... View more

Feature Request: Allow Users to Permanently Set the “Simplified” Layout as the Default Title: Add an option to permanently set the “Simplified” layout as the default view on the Power BI Home page Description: Currently, the Power BI Home page displays the new Copilot layout by default. While users can manually switch back to the “Simplified” layout via the selector at the top of the Home page, this preference is not saved permanently and must be reapplied frequently. Recommended apps are not immediately visible to new users. The official documentation only confirms the manual toggle but does not provide a way to persist this setting.  This creates friction for users who prefer the classic, cleaner layout for daily work. Requested Enhancement Introduce a persistent user setting that allows individuals to set the “Simplified” layout as their default Home page view. Optionally, add a tenant‑level or admin‑level setting for organizations that want to define a default layout for all users.  Benefits Improved usability and reduced manual steps A more consistent and predictable user experience Better alignment with user or organizational preferences Enhanced onboarding and orientation for non‑technical users  Background Recommended apps are not immediately visible to new users At the moment, no option exists to make the simplified layout the default. Microsoft documentation mentions only how to switch manually, with no support for saving the preference long‑term ... View more

Description Currently in Power BI, when a visual contains multiple columns or measures, filtering values within that visual often requires writing complex DAX expressions or creating additional measures and calculation logic. I would like to suggest a feature where users can filter values directly within a visual column, similar to the filter/drop-down functionality available in Excel tables, without relying on DAX. Proposed Feature Once a visual is prepared with multiple columns: Each column should have an Excel-like filter option Users should be able to: Include / exclude specific values Apply simple conditions (equals, greater than, less than, blank, non-blank) Filter at the visual level only, without affecting other visuals Example Scenario A table visual contains: Area Town village Activation Count Qualification Status Instead of writing DAX to: Remove blanks Exclude zero values Show only qualified Towns The user can simply apply filters directly on the relevant column inside the visual—just like Excel. Business Impact 🚀 Reduces dependency on complex DAX 🧠 Improves flexibility for business users ⏱ Saves development and maintenance time 📊 Makes Power BI behave more intuitively for Excel users 🔧 Enables faster ad-hoc analysis without model changes Current Limitation / Workaround Requires additional DAX measures Calculation groups or field parameters add complexity Not user-friendly for non-technical report consumers Expected Outcome Power BI visuals become more interactive and flexible, enabling self-service filtering while keeping the data model clean and simple. ... View more

When the user clicks on show as table on a visual in report, and the user does not want to see the total option. Can this be made as customisable? ... View more