Hi team,   I would be really helpful if we could have the explore mode in the Power BI desktop when connected to a semantic model in edit mode or even in connected mode   That would make the exploration of the data very accessible - the share and open in new tab buttons should of course not be there 🙂         ... View more

At the moment in a large query with many interdependencies it can be really hard to navigate and find the right info. It's a great feature to have but could  use improvements like for example:   Visually differentiate upstream vs. downstream queries relative to the selected query, eg color coding Make it easier to choose the starting query for the view (e.g., quick search or dropdown), eg Search bar or dropdown to pick the query to focus on Option to “Center on selected query” for clarity Maybe also add filters to show only upstream, only downstream, or both. ... View more

Add two complementary capabilities for DAX development in Power BI: Collapse multiple dependent measures/variables into a single final measure for use in reports. Explode a complex measure into its constituent parts (e.g., VAR expressions and referenced measures) as separate measures for investigation, performance tuning, and debugging. Currently, you can do all this quite painfully with a high click-and-wait tax, would be wonderful to have it as an integrated feature. ... View more

I went into my Pipeline and Notebook and a Connection has shown up whereas before I just had Workspace ID and Pipeline ID.  I think this is a change to Fabric that has happened December 25?)   Thank fully I got admin to sort out a service principle in Azure but I have some issues.   1. best practice is to parameterise everything. i cant parameterise this connection ID. I can my workspace ID and Notebook ID. But not this. (This needs to be able to be parameterised) 2. Once set It says Notebook and my name so even thorugh a service princaple has been used it seems to be a personal connection.  (This also needs reolving. it shouldnt be a personal connection when i used a Service principal   this is very confusing and needs looking at. this is specifically for collaborating with other developers. Promoting through dev test prod etc. We want to be able to do this properly   This is useless when you want to push your code base back into main dev workspace. or for example if another developer pulls the codebase into their dev workspace to work on it. I have been using library variables for the workspace Id and Notebook ID, Everyone and every environment has there own. But this has really thrown it.  ... View more

Pouvoir dupliquer les mesures afin de ne pas les refaires à chaque fois serait très utile ... View more

Need Power BI rest api which list all data sources from all the sematic model at tenant level ... View more

Hi, the deployment pipelines are represented a convenient and useful feature than using DevOps or Git and I hope that they can be improved as soon as possible. I think in order to deploy a warehouse it it very important that a deployment pipeline is able to follow the order of dependencies between warehouse objects without generating any errors. F.e. a deployment pipeline should first deploy the schemas, then deploy the tables and next the views and so on. A view could depend on another view. Thanks ... View more

Please add a built-in way to test OneLake Security data access roles, similar to how Power BI lets you test role definitions (“View as”). We need to easily verify which data is visible for a given role, security group, or user before releasing to production. Requested capabilities Allow EXECUTE AS (security group name or user name) so we can preview data and verify the effective RLS and CLS behavior. Support testing RLS/CLS even when the target group or user belongs to multiple roles. Allow us to define test expressions against the result set returned under EXECUTE AS. Make these configured test expressions callable via API, so automated tests of RLS/CLS behavior can be integrated into CI/CD pipelines. ... View more

Power BI currently applies only one RLS role per user per dataset, evaluated before the report loads. Because of this, slicers or disconnected tables cannot be used to let users pick which role they want to view the report as (e.g., SuperUser vs CompanyHR vs Self). This creates a major limitation for users who legitimately have multiple roles. In real scenarios, a user may need to switch between their restricted view (HR) and full view (SuperUser), but Power BI always forces the most permissive role and offers no way to choose. The only supported workaround today is creating multiple datasets and duplicated reports, which becomes unmanageable and not scalable as the number of roles grows. Requested Feature: Allow users to choose their active RLS role dynamically inside the report—using a slicer, parameter, or a built-in role selector. RLS should respect the user’s choice among the roles assigned to them. This would avoid dataset duplication, reduce maintenance, and support common enterprise use cases where users hold multiple roles. Why This Is Important Many enterprise scenarios involve users who hold multiple business roles, such as: SuperUser + Company HR Manager + Auditor Global Admin + Regional Admin Internal + External View Multiple market/country responsibilities These users need the ability to explicitly pick which role they want to use for a report, not always default to the most permissive one. Proposed Enhancement Introduce a new RLS feature such as: Dynamic RLS mode Allow RLS expressions to reference a special runtime value (e.g., RLSSELECTEDROLE()) set by a slicer or parameter. Session-based role override After login, users can pick one of their assigned roles for that session. UI-based role selector A Power BI native visual that lists roles the user has access to, enabling runtime switching. Dataset-level “multiple active roles” mode Allow RLS to author rules based on a user’s chosen role rather than forcing one default. These changes would keep security intact while allowing more flexible, real-world role behavior.   Thanks for considering this. Let me know if further clarification is needed. ... View more

Summary Microsoft Fabric currently alerts administrators only when overall capacity hits 100 percent. However, this alert is typically triggered by short-lived interactive operation spikes, which resolve quickly and rarely pose long-term risk. The real operational threat comes from high background operations utilization, which runs continuously and can quietly consume capacity over a 24-hour rolling window. Fabric should introduce a separate, configurable alert for background operations thresholds to support proactive capacity management. Problem Interactive workload spikes—such as report queries or user-driven actions—may momentarily push capacity to 100 percent, but they are brief and predictable. Capacity typically stabilizes once user activity subsides. Background operations behave differently: They run on a continuous 24-hour rolling cycle They accumulate load instead of dropping off quickly They can slowly consume large portions of available capacity They can create sustained, system-wide throttling long before admins realize there is a problem By the time the current 100 percent alert fires, background utilization has often been building for hours, and remediation options are limited. Proposed Solution Introduce a dedicated admin alert that triggers when background operations utilization exceeds a configurable percentage threshold (e.g., 40%, 60%, 80%). Key characteristics: Separates background consumption from interactive spikes Provides early warning before a choke point occurs Supports proactive workload scheduling and capacity planning Reduces the likelihood of long-lasting throttling scenarios Why This Matters High background utilization is a slow-burn risk that impacts the environment across the entire day. Without visibility into rising background load, admins cannot intervene early enough to prevent throttling or degraded user experience. In short: Interactive spikes = noise Background operations = signal Fabric’s alerting model should reflect this difference to ensure stable and predictable capacity performance. Requested Outcome Add a configurable background operations utilization alert to Microsoft Fabric Capacity to enable proactive governance and avoid sustained system throttling. ... View more

Problem: Currently, downstream consumers who need to query Eventhouse data via Lakehouse shortcuts must have read access to the primary Eventhouse tables. This creates two main challenges: Security / Governance: Users can access the primary Eventhouse, which may not be desirable. Operational Overhead: Teams must schedule incremental .export commands for each table to provide Lakehouse access, which is cumbersome and difficult to manage at scale.   Proposed Solution: Introduce a feature that allows Eventhouse to automatically export data to Lakehouse shortcuts without requiring users to have read access to the primary tables. Benefits: Downstream consumers can query Lakehouse shortcuts without impacting Eventhouse compute or hitting query limits. Eliminates the need to schedule per-table exports manually. Maintains strict security and governance by preventing direct access to the primary Eventhouse tables. Supports both full and incremental exports, keeping Lakehouse data fresh and up-to-date. ... View more

I am trying to authenticate to AML workspace from Fabric Notebook using DefaultAzureCredentials. While running the command, it si failing to retrieve token. I see that the only auth mechanism is through SPN/Secret route. Do you have timelines on when this will be available for GA as using SPN/Secret is not secure/compliant    ... View more

Hello Team, We have noticed that in our Power BI Service, the Viewer role on a workspace no longer provides Build permissions for datasets as it did previously. Even when Build permissions are manually granted, users with Viewer access still cannot see the datasets in the workspace—they can only view reports. We would like viewers to have the same access as before, so they can see and connect to datasets in workspaces where they have Viewer access. Please look into this issue so that viewers can rebuild reports as needed, which helps keep production environments secure without requiring everyone to have Contributor roles. ... View more

Restricting Fabric Mirror Databases to read-only is a huge limitation that limits users abilities to manage the database in certain ETL operations to it.  Stored Procedures are very limited if you can't write to the database.  Allowing write operations would expand the use cases for a Mirrored Database immensely. ... View more

It would be helpful to add dynamic context to visuals using a measure within this field:     ... View more

Customizable input/checkbox fields in Power BI that support lightweight write-back to the semantic model would allow users to mark records (for example, “Reviewed,” “Needs Follow-Up,” or “Exclude”) directly in table and matrix visuals. The checked state would be stored as a field in the model and could then be used like any other column for filtering, grouping, or driving measures across pages and sessions. This would provide an intuitive, low-overhead way for business users to track record status and create ad-hoc subsets of data, without needing complex bookmarks, personal filters, or external write-back solutions. ... View more

We would like to have a tenant setting that allows us to completely disable report sharing with other users. Currently, to block report sharing, we can disable the tenant setting for people within our organization. Similarly, we need a tenant setting that either blocks sharing with specific people or disables sharing entirely. ... View more

We need the ability to send email only when data exists to be sent. ... View more

Power BI app should be automatically update when reupload the dashboard ... View more