Currently there is no way to delete multiple items simulataneously in a workspace. Also there is no way to delete an entire folder and it's contents at once.    This issue was raised previously (here) and the response was that the introduction of folders (released Q1 2024) would solve this. However this functionality is still not compatible with folders.    There is a workaround to do it programatically however I feel this should be a feature within the Fabric UI.    ... View more

In Power BI Apps, section headers are organizational only, they can’t serve as a clickable destination. To create a “hub” page and still group child items, authors must duplicate the name: once as a section and again as a page/link inside that section. This leads to redundant labels, extra maintenance, and user confusion. Current navigation lets authors add sections, links, and (optionally) one overview page, and the first navigation item becomes the app’s landing experience, but there is no way to make a section header itself open content. ... View more

When datasets are created in BigQuery using the BigQuery API without explicitly specifying a location, the API defaults to the US multi‑region. This default behavior causes issues for users need a way to change the default setting ... 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

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

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

Dear Microsoft Team, We are currently transitioning from Power BI Report Server (PBIRS) to Power BI Service to support hybrid reporting scenarios that combine on-premises and cloud data sources. While the Service offers great capabilities for composite models and cloud integration, we have encountered a major limitation regarding subscriptions for paginated reports (RDL). In PBIRS, we rely heavily on advanced SSRS-style subscription features such as: File share delivery Flexible scheduling Custom delivery extensions However, in Power BI Service, subscription options for RDL reports are restricted to basic email delivery or require Power Automate. This creates significant challenges for our end users, who are not familiar with Power Automate and expect a simple, native experience similar to PBIRS. Our Request Please consider: Adding full SSRS-style subscription capabilities for paginated reports in Power BI Service, including file share delivery and advanced scheduling. Providing a native solution that does not require Power Automate or Semantic model use (since we don't use it for RDL 80% of the time) for advanced subscriptions, to ensure ease of use for non-technical end users. In moder times analysts use combined solutions for datasorces on-prem+cloud often but with your PBIRS you are limiting there Power Bi and at the same time limiting PBI Srvice as well for RDL dynamic subccriptions.  Why This Matters We have many reports that combine on-prem and cloud data, making Power BI Service essential for hybrid scenarios. Limiting subscription options creates a major adoption barrier for enterprise customers transitioning from PBIRS. Our end users need a seamless experience without additional complexity or reliance on external tools. We believe enhancing subscription functionality in the Service will significantly improve enterprise adoption and align with the flexibility currently offered in PBIRS. Thank you for considering this request. Please let us know if there are any plans or timelines for improving subscription capabilities in Power BI Service.   Thank you!  Best, Maria Suncheleeva  ... 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

We love Polars. It is user friendly and it works great for our data volumes.   Today, V-Order can be applied to delta parquet tables using Spark notebooks, but not Python notebooks.   Please make it possible to apply V-Order to delta parquet tables using Polars in pure python notebooks.   We encourage Microsoft to cooperate closer with Polars, as most customers can save a lot of CUs (money) by switching from Spark (distributed compute) to Polars (single node). ... 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

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

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

Currently, TMDL view is only available in Power BI Desktop.   Please make TMDL view available also in Power BI Service/Fabric in the web browser. ... 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

Our team would like join to our security mapping table in the rule and call the employee that is querying's username and filter by it. It would look like: select * from my_table inner join security_table on security_table.projectID = my_table.projectID where security_table.username = username() This would allow us to dynamically set our RLS on the table. ... View more

Problem When developing or operating Warehouse‑backed models, we often need small, surgical data fixes - e.g., correcting an erroneous valid_to_dt in an SCD2 dimension or updating a junk‑dimension attribute. In SQL Server/SSMS, the “Edit Top N Rows” grid makes this fast and safe. Fabric Warehouses currently lack a GUI row editor, pushing teams to external tools (e.g., DataGrip) or ad‑hoc DML scripts. This creates friction, slows incident resolution, and fragments tooling—even though Warehouses already support full DML via T‑SQL.   Proposal Provide a first‑class “Edit Top N Rows” experience for Warehouse tables: Fabric Portal: grid editor with inline add/edit/delete, filter, and commit/rollback. SSMS / VS Code: enable the same grid or a lightweight editor with “generate DML” preview. Respect Warehouse permissions/RLS; optionally log changes via SQL Audit Logs and take a Time‑Travel snapshot for quick rollback. Why this matters Speeds data quality hotfixes, removes the need for competitors’ tools, and lets us fully standardize on VS Code + SSMS + Fabric while retaining governance and safety. ... 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

I successfully separate Selection State(Selected) from Selection State(Unselected) with transparency option. However, If the user does not make any selection(means selects all) the display of the button is same as Selection State(Unselected). It must be same as Selection State(Selected). Technically, none selected means All selected(same as any selection) ... View more