Hi   Please change the translation of the panel name Format Image from Formatbild to Bildformat or Formatera bild in Swedish.               Thanks, Anna-Karin   ... View more

Summary Improve the readability and editability of Spark Notebooks by introducing named cells, an outline view based on those names, and drag-and-drop cell reordering. Detailed Description 1. Cell Naming Allow users to assign a name to each notebook cell. This name should be independent from comments and code content, and treated as metadata. Benefits Improves readability of large notebooks Makes the role and intent of each cell explicit Helps collaborators quickly understand notebook structure 2. Cell Outline View (Based on Cell Names) Provide an outline / navigator panel that lists cells using their assigned names. Benefits Enables quick navigation in long notebooks Provides a structural overview similar to sections in documents Reduces cognitive load when reviewing or debugging 3. Drag-and-Drop Cell Reordering Enable reordering of cells via drag & drop, ideally within the outline view as well as directly in the notebook. Benefits Makes refactoring and restructuring notebooks much easier Encourages incremental cleanup and better organization Aligns with how users naturally think about notebook structure Why This Matters As Spark Notebooks grow larger and more production-oriented, readability and structural clarity become as important as execution correctness. These features would: Improve developer productivity Reduce maintenance cost Make Fabric notebooks more suitable for long-lived, team-managed workloads ... View more

Requested Features:   (Gateway connection status)   1. Gateway Connection Health API - Endpoint: GET /gateways/{gatewayId}/{connection}/health - Returns: Overall gateway connection health status (online/offline/degraded) - Includes: Last heartbeat timestamp, connectivity status   2. Datasource Connection Test API - Endpoint: POST /gateways/{gatewayId}/datasources/{datasourceId}/test - Returns: Connection test result without triggering actual data operations - Includes: Response time, connection success/failure, error details   3. Gateway Metrics API - Endpoint: GET /gateways/{gatewayId}/metrics - Returns: Performance metrics (CPU, memory, active connections, query queue) - Supports: Time-range queries for historical data   Use Case: Organizations need to proactively monitor gateway infrastructure for: - Alerting when gateway connection go offline - Detecting SQL Server connection failures before users report issues - Integrating with external monitoring tools (Datadog, Azure Monitor, etc.) - Meeting SLA requirements for data availability   Current Limitations: - Existing APIs only show gateway registration status, not real-time connectivity - No way to test datasource connections without triggering data refreshes - No programmatic access to gateway performance metrics   Expected Benefit: This would enable enterprise customers to build robust monitoring solutions and ensure high availability of their data infrastructure. --- Please vote if you'd find this valuable for your organization! ... View more

When I create a table or matrix, the column widths are defined by the length of the column name. I should be able to choose in the settings, a specific width for all columns (eg, 20px), or choose automatic adjustment to fit all columns within the visual's window size. I have to manually adjust every single column width, because the default is to fit the column header/measure name on one line. Often id prefer it be across 2 or 3 lines, if it means I can see my whole table without scrolling. This ius a massive omission in the function of Power BI, and severely impacts the visual impacts of my dashboards. Tableau has this as a simple setting that is accessible from screen, and Microsoft cant even allow this in the advanced settings?  ... View more

When a Report Builder file is based on a PowerBI dataset, the functionality to connect is very easy. Where the workflow falls apart is when complex parameters are required inside the Report Builder file. We usually want Report Builder to act as a 'detail' table for some metric on a PBIX.  That means if I click a button, or a graph or whatever in PowerBI I can launch a Report Builder file.  This works great when we create dynamic URL's.   However, when adding parameters to Report Builder, we are forced to deal with legacy workflows from SSRS to get the parameters to work.  Dates, datetimes, IN functions, etc are outright nasty to figure out.  We need a more efficient way to handle complex Report Builder files in our products. ... View more

Request to add an end-user option in Power BI to expand the Copilot side pane to full screen. Not all users have access to the standalone Copilot experience, so providing a full-screen option would allow users to preview and evaluate Copilot-generated content without switching to another window. The current side pane is relatively narrow; visuals and tables produced by Copilot can be difficult to read due to the limited pane size. Adding a full-screen expansion option would improve accessibility, readability, and overall usability of Copilot features within Power BI. ... View more

Currently, Power BI does not provide a simple way for workspace admins or Power BI service administrators to disable scheduled refresh for all datasets (semantic models) in a workspace with a single action. This creates significant challenges in scenarios such as: Emergency Maintenance: When immediate suspension of refresh is required to prevent failures or data inconsistencies. Cost Control: Avoiding unnecessary refreshes during downtime or when source systems are unavailable. Governance: Enforcing organizational policies without relying on individual dataset owners. At present, the only options are: Manually disabling refresh for each dataset individually. Using REST APIs or PowerShell scripts, which require technical expertise and permissions. Proposed Solution: Introduce a one-click option in the Power BI Service (workspace settings or Admin Portal) that allows authorized admins to: Pause all scheduled refreshes for every dataset in a workspace. Optionally resume them later with a single action. This feature would greatly improve administrative efficiency, reduce risk, and enhance governance for organizations managing multiple datasets. ... View more

Can you please enable the ability to provide confounding variables in quick insights so it doesn't rely on random correlations across data tables? It seems all but useless in the large part when assessing meaningful relationships with data. ... View more

As a suggested improvement, it would be very useful to allow increasing or configuring the text input character limit in Power BI Service. Many real-world scenarios require users to enter longer text, such as comments, observations, incident descriptions, approvals, or operational notes. A fixed 100-character limit makes these scenarios difficult or impossible to implement directly from reports. Since Power BI Desktop does not enforce this limitation, having the same behavior in Power BI Service or at least a configurable limit at the visual or report level would greatly improve consistency and usability. Even a higher default limit (for example 500 or 1000 characters), or an optional setting to control the maximum length, would enable many valid business use cases without needing external tools like Power Apps. ... View more

Right now, the Viewer role in the Power BI service can create subscriptions for him/herself but cannot add other users to a subscription. Only higher level roles (i.e., Admin, Member, Contributor) may add other users to subscriptions. BUT these roles have access to the model(s) and at least some report edit capabilities.   Our Viewers have the need to setup subscriptions, mostly paginated reports, to send to their direct reports as most recipients of reports in our org are used to the "push" approach every morning. They're general low-tech individuals with the need for key data to perform their jobs well, and SSRS was a good solution for this, but we're preparing now for the de-support of SSRS in 2028. In the meantime, we are publishing our paginated reports to both PBIS and SSRS to allow managers to setup subscriptions to deliver to all their direct reports whilst the managers are using PBIS (a PBI app to be exact). ... View more

With the 'Replace Values' function, there should be a way to change the values if they are not a specified value. Right now, you can only do it if it is a specified value, but it would help if I could change the values if they are not equal to something. For instance, I have a number column and I want to make it a binary field. If the value is zero, it should stay zero. If it is not zero, I want to change it to 1. It appears that this can only be done if a new column is added, which I would like to avoid to keep the file size smaller. Instead I would like to change the value in that column to 1 if the current is not zero ... View more

It would be beneficial if we could connect to the data sources directly from Excel Web. Although this might require the implementation of an on-premises data gateway. By enabling this connection, we can streamline the data work flows and ensure more efficient access to the necessary information. This change could enhance the productivity and allow users to leverage real-time data insights seamlessly. ... View more

While setting up the one drive connection, is there a way to set it up using SPN instead of a user identity?  ... View more

Is there a way to subscribe to only recent changes? I keep getting quarterly reports on things that happened 2 years ago, but I only want to see if anything has changed in the most recent quarter. ... View more

Power BI Service dynamically resizes visuals to adapt to different browsers, zoom levels, DPI scaling, and device sizes for accessibility/responsiveness. This adaptive model is valuable, but it can cause unstable rendering (“jitter”) for visuals with small multiples and dense labels (e.g., stacked bar/column charts). The result is visible reflow and re-rendering after page load or on interaction in Service, even when the layout is stable in Desktop. Microsoft’s own guidance and docs emphasize responsive behaviors for visuals (e.g., slicers and other core visuals) in both Desktop and Service, which explains why Service keeps recalculating layout for different viewports. [reddit.com], [learn.microsoft.com] Problem & impact: Unpredictable resizing in Service for stacked bar/column charts with small multiples and multiple labels/legends. Misalignment & jitter degrade trust for executive dashboards and compliance reports. Developers spend time on workarounds (fixed paddings, minimum category widths, non-auto fonts) that don’t fully prevent Service-side reflow. (These axis/padding controls exist, but they don’t stop the dynamic recalculation in Service.)  Enterprise stakeholders expect Desktop = Service consistency for sign-off; current behavior undermines that. Proposed solution: Introduce an opt-in “Lock Layout” / Pixel-Perfect Mode at the visual and/or report level that: Disables dynamic reflow in Service, preserving exact Desktop layout (fonts, paddings, grid, axis density). Caches layout once per visual load (and invalidates only on explicit user resize), rather than re-measuring labels and legends multiple times. Offers two modes for authors: Responsive Mode (current behavior; best for mobile/adaptive scenarios) Fixed Layout Mode (desktop-quality, pixel-consistent rendering for executive dashboards)   ... View more

  Problem The recent addition of Excel Drill‑Through support for Direct Lake models is a welcome improvement. However, this change introduces a significant governance and usability challenge for large enterprise models. In the current implementation: Drill‑through is enabled by default for every measure The default behavior exposes all columns from the underlying fact table The only way to control this is to manually add a detailRowsDefinition to each measure For large Direct Lake models with hundreds or thousands of measures, this is not scalable. We would prefer a governance model where drill‑through is disabled by default, and only specific, approved measures opt in. Current Pain Points To achieve controlled drill‑through today, we must: Edit every measure Add a “blocked” detailRowsDefinition for measures that should not allow drill‑through Add a custom detailRowsDefinition for measures that should allow it This is extremely time‑consuming and error‑prone at scale. Additionally, the default Excel drill‑through behavior (showing all fact table columns) is rarely appropriate for governed semantic models and cannot currently be changed. The only workaround is to: Export the model as TMDL Bulk‑edit all measures using scripts or AI Re‑import the updated TMDL This is not a sustainable long‑term approach. Requested Enhancements 1. Model‑level setting: “Disable drill‑through by default” A simple toggle in Power BI Desktop or the model properties pane that allows developers to invert the default behavior: Off by default → Measures must explicitly opt in On by default → Current behavior This would immediately solve the governance issue for large models. 2. Ability to define a default detailRowsDefinition Allow model authors to specify a default drill‑through template or suppression rule, rather than relying on the fact‑table dump. 3. Optional: UI support in Power BI Desktop For example: A model‑level drill‑through policy setting A bulk‑apply option for detailRowsDefinition A “block drill‑through” checkbox in the measure properties pane These additions would make drill‑through governance far more manageable. Why This Matters Direct Lake is designed for very large, enterprise‑scale models. These models often require strict governance, and the current drill‑through defaults create: Data exposure risks Inconsistent user experiences Significant manual overhead Providing model‑level control would align drill‑through behavior with enterprise needs and reduce unnecessary TMDL manipulation.   For reference, here’s the update announcement: Drillthrough in Excel now supported for Direct Lake and DirectQuery Models | Microsoft Power BI Blog... ... View more

Currently, we can only view email subscriptions for reports within a specific workspace. We would like an option for tenant admins to see all subscriptions across the tenant, so the admin can add or remove users and take ownership of any subscription. ... View more

Currently, when configuring Edit Interactions in Power BI reports, users must manually adjust filters and highlights for each individual visual. This process is time-consuming and prone to inconsistencies, especially in reports with multiple visuals. Proposed Enhancement: Introduce a global option that allows users to apply the same Edit Interaction settings (filter or highlight) across all visuals in a report or within a selected page ... View more

Currently, user-defined functions are defined at the model level. It would be nice to be able to define functions that are local to a DAX expression (e.g. the DAX expression of a measure, calculated column, or even a variable) so that the model-level scope does not get cluttered with functions that are needed in only a few places. This might require treating functions as first-class citizens, similar to what was done in Excel with LAMBDA, so that functions can be assigned to variables. ... View more