As per the Microsoft Learn documentation “Troubleshooting dataflow issues – connection to the data source”, dataflow connections are not automatically removed when they are no longer used by a dataflow. Instead, they must be manually deleted or trimmed, otherwise they continue to appear under Dataflow connections. Troubleshooting dataflow issues - connection to the data source - Power Query | Microsoft Learn Observed Behavior When a connection is removed/unlinked from a specific dataflow, it still appears in the dataflow connections list. This behavior is expected according to the documentation, as dataflows maintain associations with previously created data source connections unless a manual trim is performed. The issue becomes more noticeable when: The same connection is reused across multiple dataflows The connection is no longer required for the current dataflow, but is still needed elsewhere [Troublesho...soft Learn | Learn.Microsoft.com] Challenges / Impact There is no direct way to remove or hide unused connections only for a specific dataflow. Manual cleanup (gateway switching / connection trimming) must be performed per dataflow. In environments with hundreds of dataflows, this process becomes: Time‑consuming Operationally expensive Difficult to manage at scale This increases the risk of: Confusion around which connections are actively used Accidental deletion of shared connections used by other dataflows Reference Microsoft Learn documentation confirms that: Old or deleted data source connections can continue to appear Cleanup requires a manual user‑initiated trim process There is currently no automated or bulk cleanup option [Troublesho...soft Learn | Learn.Microsoft.com] Ask / Feedback for Fabric Team The dataflow connections should be updated automatically when they are unlinked or removed from the dataflow, as it is inconvenient to manually remove the connections from Manage Connections and then click Save and Close in the dataflow. We kindly request the Fabric team to implement this update as soon as possible. ... View more

To address the challenges of organizing and presenting data due to the limitations of column and row headers, a potential solution would be to implement a new matrix visual with customizable controls, allowing report creators to adjust the dimensions of columns and rows, group them hierarchically, apply diverse styles, and use conditional formatting. ... View more

Currently, the preview feature supports creating, running, and scheduling dbt jobs. However, for end-to-end orchestration, we also need a way to invoke these jobs from within a pipeline. Providing either a native pipeline activity for dbt job execution or an API for triggering them would significantly improve the usability of this feature in production workflows. ... View more

If multiple users want to work with the same Dataflow Gen 2, they currently need to take over ownership, which can be challenging for users in the future. It would be helpful to have an option like workspace permission support, allowing users to edit Gen 2 without needing ownership. ... View more

Enterprise customers adopting Microsoft Fabric want to standardize on OneLake as the unified storage layer for both structured data (Lakehouse tables, Warehouse data) and unstructured data (files stored in OneLake). This data may originate from external systems (ADLS, S3, databases, SaaS) or be created natively within Fabric workloads. A growing number of regulated customers have Infosec and compliance requirements to enforce retention policies consistently across all data in OneLake, regardless of source or workload. Today, customers are explicitly asking for a OneLake‑scoped retention capability that they can reason about as a storage‑level control, similar in intent to ADLS lifecycle policies.   A native, Purview‑governed OneLake retention model would materially reduce this adoption barrier and strengthen the OneLake governance story. ... View more

Hello, I would like to request an enhancement to the Page Navigator visual so that it offers the same layout options available in the Button Segmentation Slicer.                                 Layout options: Orientation: horizontal / vertical / grid Style: blocks / full screen Number of columns Automatic grid Spacing (gap) between buttons Overflow style: paginated / continuous scrolling (scroll)           These same options are not available in the Page Navigator, which limits the use of this visual in reports that rely on button-based navigation. I request the evaluation of this feature, allowing the Page Navigator to offer the same layout configuration options as the Button Segmentation Slicer. This enhancement is relevant in scenarios with a large number of pages, where navigation needs to be intuitive, reducing the need for alternative solutions and manual customizations. ... View more

Context & Observation In building pixel-perfect Power BI reports, we frequently use Shapes (rectangles, lines, rounded containers, icons) to create headers, separators, buttons, and layout scaffolding. When the shape count is high, we see noticeably slower page rendering and interactions (e.g., slicer response, bookmarks, hover, selection). Conversely, DAX measures—even in large numbers—do not show the same penalty because they don’t create additional draw calls or DOM-like visual nodes; they are calculated at query time and reused by visuals. Repro (high level) Create a report page with 100–300 Shapes (lines, rectangles with gradient/fill, shadows/rounding). Keep data volume minimal and visuals simple (e.g., a few cards/labels). Compare page navigation and selection interactions versus the same page with consolidated or fewer Shapes. Performance Analyzer shows more time spent in visual rendering rather than data query. Business Impact Authors avoid clean visual scaffolding and branding due to performance costs. Navigation/landing pages with many decorative elements feel sluggish, which reduces perceived quality. This disproportionately affects enterprise reports that require pixel-perfect layout and design consistency. Request: Could Power BI optimize the rendering pipeline for Shapes so that using many Shapes does not impact performance? Possible approaches might include: Treating Shapes as lightweight vector primitives with batching, caching, or GPU acceleration. Offering a Combine/Flatten Shapes option to reduce the number of render objects. Attachments (available on request) Sample PBIX files with high shape counts Screen recordings comparing interaction latency Performance Analyzer screenshotsProviding a Low-Overhead Shape type for decorative elements (no interactivity) Why this matters Other design tools (e.g., traditional drawing apps) handle numerous vector shapes efficiently through batching and caching. Bringing a similar approach to Power BI would allow rich layouts without compromising performance, aligning with enterprise design standards. Exposing a Shape Count / Visual Complexity metric in Performance Analyzer to help authors identify bottlenecks. Impact: This would enable authors to build richer layouts (headers, separators, callouts) without compromising responsiveness, particularly on navigation-heavy pages. ... View more

Currentluy On-premises data gateways aren't supported and fail to register when Private Link is enabled. kindly Support On‑premises Data Gateway when Private Link is enabled ... View more

In the newer PostgreSQL versions, the "ssl_renegotiation_limit" setting has been removed. The PostgreSQL connector in Power BI is still referencing this setting, so an update is needed for the connector to support encryption with the latest PostgreSQL versions. ... View more

The user wants to customize default questions on Copilot. We believe that Copilot would be more effective if report viewers could select from prompts that the report developer has predefined, rather than having to type their own prompts. ... View more

New Desktop app update installed an almost white user interface. There is zero contrast which is not good for the eyes. I see where some people have requested a light interface so incorporate an option to select either light or dark theme like in the Office apps. ... View more

Hi,   I created a shortcut table in the Lakehouse where one of the columns has a length greater than 8,000 characters. However, when I reference this shortcut table in Data Warehouse views, the data in that column gets truncated. How can this issue be resolved?   Thanks, Venkat ... 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

Currently, Microsoft Fabric supports notifications only at the overall capacity level, which makes it difficult to proactively identify individual artifacts driving high CU consumption. This idea proposes enabling per‑artifact capacity usage alerts for semantic models, reports, and other items. Admins could define CU thresholds at the artifact level and receive notifications when those limits are exceeded. This would help quickly isolate high-impact artifacts, reduce capacity contention, and improve governance and operational efficiency. ... View more

When multiple slicers are based on the same date dimension (e.g., a Month slicer and a Date slicer in “Between” mode), the Date slicer does not visually update when filtered by the Month slicer, even though the model is correctly filtered. It would significantly improve UX if the “Between/Before/After” date slicers could optionally auto-sync their visible range with the current filter context. A toggle such as “Synchronize with filter context” would make date filtering behavior more intuitive and consistent across slicer types. ... View more

Currently, you can hit weird errors or slow performance when trying to open items in a workspace that is linked to a paused capacity.   It would be a real quality-of-life improvement if there would be a small message or popup showing when a workspace is linked to a paused capacit.   ... View more

We request the addition of Service Principal authentication support for the SharePoint Folder connector in Power BI, including the ability to scope access to specific folders within a SharePoint site for the refresh scenarios. This enhancement would enable app‑only, non‑delegated authentication for SharePoint document libraries, supporting unattended refreshes and eliminating dependency on user‑based OAuth tokens.   Business Impact: Without Service Principal support, SharePoint Folder refreshes depend on user credentials, creating security, governance, and reliability challenges. App‑only authentication would improve refresh stability, security isolation, and enterprise automation, particularly in environments with strict identity lifecycle and compliance requirements. ... View more

Description Power BI Desktop loads PBIP report artifacts only at open time. When PBIP files are modified externally (Git pulls, merge conflict resolutions, scripted refactors), those changes are not reflected in an already opened Desktop session, requiring manual close and reopen. This limits the effectiveness of PBIP in Fabric‑first, Git‑based, collaborative development scenarios.   Why This Matters (Fabric & Git) PBIP is foundational for Fabric CI/CD and Git integration. In real-world team workflows: Developers pull changes from Git while Desktop is open Merge resolutions and scripted updates modify PBIP files on disk Desktop cannot reload or apply those changes without restarting This breaks collaborative development, slows iteration, and makes applying Git merges to active reports error‑prone.   Proposed Solution Add an explicit “Reload from Disk” command for PBIP projects in Power BI Desktop. Discards in‑memory state Reloads PBIP artifacts from disk Equivalent to close & reopen, but controlled and safe (Optional future enhancement: detect external changes and prompt the user.)   Impact Enables Git‑collaborative PBIP workflows Allows applying merges and scripted refactors without restarting Desktop Improves Fabric CI/CD and developer productivity Increases PBIP adoption for enterprise teams ... View more

Im using a design for my power bi reports, in which i allow the user to select what measure they want to look at, from a dropdown, instead of having a new sheet for each measure.  This can lead to some filters becoming redunant for certain measures. As to not confuse the user, I am removing the filter options dynamically, depending on the selected measure, using the "filter on this visual".  If the user already has checked some values and left some unchecked not all values are removed. It would be nice to have the option of removing all filters.  Se this thread for a discussion: https://community.fabric.microsoft.com/t5/Desktop/Dynamically-remove-options-on-slicer-regardless-on-checked-state/m-p/5124123#M1460507 ... View more