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

Currently, scalar UDF containing non-deterministic functions (such as GETDATE) can't be used in combination in a query with a user table.   e.g. create dbo.udf () returns datetime2 as begin return getdate() end this query would fail: select col1, dbo.udf() as udf_output from usertable1 ... 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

Power BI report subscriptions currently send only images in the email body and need to have SSRS reports like subscription results where the complete report is available in the email body   ... View more

In the Power BI Matrix visual, when multiple fields are placed in the Columns well, the hierarchy order is fixed. The first field always becomes the outer grouping, and there is no way to swap or control who groups who. This makes it impossible to reproduce common Excel PivotTable layouts, such as:   Metric → Date / YoY / YTD   Instead of being forced into:   Date / YoY / YTD → Metrics   Add the ability to swap or control column hierarchy order in the Matrix visual, similar to Excel, allowing users to choose which field acts as the parent grouping.   Why This Matters Matches Excel behavior users already understand Improves readability of multi-metric reports Reduces workarounds and duplicated measures Enables cleaner and more flexible analytical layouts ... 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

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

As a Fabric admin, I'd like to ensure that the admin monitoring workspace can be configured with a non-human user. https://learn.microsoft.com/en-us/fabric/admin/monitoring-workspace#refreshes . The reason for that is that, we use privileged identity management, and Fabric admins are just-in-time-elevated to be that. The alternative of ensuring the role is active at the time of the refresh is just lame. Humans take days off and have weekends. Therefore, the data will always be outdated.   If the workspace can be configured with a service principal or managed identity, that would work perfectly. ... 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

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

The docs say:   "There's a semantic model-level setting to automatically update Direct Lake tables. It's enabled by default. It ensures that data changes in OneLake are automatically reflected in the Direct Lake semantic model. You should disable automatic updates when you want to control data changes by framing (...)"   https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-overview#automatic-updates   Currently, this disabling needs to be done manually on each semantic model in each workspace.   However, best practice is to not do manual adjustments in Test and Prod workspaces.   Please make it possible to control this behavior via Git instead. This setting could be a part of the definition of the semantic model item.   Please also make it possible to use Deployment Rules or Variable Library to control this behavior in Test and Prod when we're using Fabric Deployment Pipelines. ... View more

In power query when you connect to a table in a dataflow there are no options to create or use a parameter for that dataflow. When connecting to SQL there is an option when setting up the connection to create a parameter but that doesn't exist for a dataflow. This means that it is a bit fidly requiring creation of a parameter seperately then amending the advanced editor M code.  Could we get an options cog on the navigation step that allows the easy creation of or reference to parameters for dataflows and workspaces.  These are essential as we are working with dataflows and deployment pipelines and often switch between dataflows for testing but setting them up n power query is arduous. ... View more

Feature request: OneLake shortcuts to support connections to ADLS Gen2 storage accounts using managed private endpoints   Currently OneLake shortcuts only support connections to storage accounts that are publicly accessible or accessible with storage networking rules in place. Shortcuts via Managed Private endpoints are not supported yet. Our organization requires all connections to go via Private Endpoints. Furthermore, networking rules are not possible in our situation, since our Fabric instance is deployed in a different Azure Tenant.   OneLake shortcuts are a great way to save compute, as we would be able to query directly on our Delta and Parquet tables in our Storage Accounts, instead of requiring compute to serve this data. Once OneLake Shortcuts via Private Endpoints are supported, I am also hoping that Databricks mirrored catalog would be working via the Managed Private Endpoint connections.   Therefore my feature request is OneLake shortcuts to support connections to ADLS Gen2 storage accounts using managed private endpoints. ... 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

Problem Statement Currently in Power BI, when a Dataflow or other artifacts (e.g., datasets, reports) are deleted, they cannot be restored. This can cause significant issues for customers if the deletion was accidental or triggered during operational activities.   Customers want an option to restore deleted Dataflows or artifacts, with a retention period would help customers quickly recover deleted content, reduce operational impact, and align Power BI with common data‑platform usability standards. ... View more

Today, Power BI semantic models (datasets/DAX) work well when Power BI is the only BI tool. However, many organizations use Databricks as their lakehouse and need consistent, governed metrics across multiple BI tools, ML pipelines, and APIs. When the semantic layer lives only in Power BI: Logic is duplicated across datasets and tools Governance/security (RLS/CLS, masking) is fragmented Schema changes in Databricks break reports ML/AI pipelines cannot reuse business logic from Power BI models Proposal: Enable native Power BI integration with Databricks Metric View ... View more