As the subject states, give PBI developers the ability to order drillthrough pages to their desired order. Additionally, ensure the order persists when the report is published to Fabric. ... View more

Current Behavior Value.NativeQuery() supports parameter placeholders during Power Query preview evaluation, but parameter bindings are not preserved during DirectQuery runtime execution after Close & Apply. This causes runtime SQL execution failures such as:   Must declare the scalar variable @Param -- for MS SQL Server database OR  ORA-01008: not all variables bound -- for Oracle database when the DirectQuery engine reconstructs SQL without rebinding parameters.   Why Existing Alternatives Are Insufficient 1. String Concatenation Unsafe for text parameters. Example:   Value.NativeQuery( Source, "SELECT * FROM Table WHERE Name = '" & Param & "'" ) Problems: SQL injection exposure manual escaping complexity loss of type-safe parameterization inconsistent query plans 2. Stored Procedures Not viable in many enterprise/vendor-managed environments: read-only access no schema modification permissions SaaS/vendor-controlled databases 3. Query Folding Folding applies transformations after source query generation in many cases. This does not support scenarios where parameters must: alter joins constrain CTEs influence optimizer behavior reduce scanned partitions control source-side execution logic Suggested Feature Add official runtime parameter binding support for Value.NativeQuery() in DirectQuery mode.     Value.NativeQuery( Source, " SELECT * FROM Sales WHERE SaleDate >= @StartDate AND SaleDate < @EndDate ", [ StartDate = StartDateParam, EndDate = EndDateParam ] ) with guaranteed preservation of: parameter metadata parameter values parameter types prepared statement semantics through the full DirectQuery execution pipeline.   Additional Enhancement Ideas Microsoft could strengthen the proposal further with optional features like: A. Typed Parameter Contracts [ StartDate = type date, CustomerId = Int64.Type ] to ensure providers bind correctly.   B. Safe Dynamic Lists Support:   WHERE Region IN @RegionList with structured array binding instead of string expansion.   Why This Matters This capability would: improve security reduce SQL injection risk improve DirectQuery performance support enterprise governance enable vendor-managed read-only environments align Power BI with modern parameterized query behavior available in other BI/data platforms   ... View more

(Creating an idea on behalf another user from SQL - Page 2 - Microsoft Fabric Community)   In the context of Get Data for Power Query....   Source list should be customizable for the user. Everyone has their own set of normally used sources and 90% of the time those aren't going to be the ones that are listed. ... View more

Hi, I think it could be very useful to be able to encrypt or obfuscate the code of a notebook in order to safeguard intellectual property. Thanks ... View more

Currently, Real-Time hub supports alerts only for workspace item-level events (create, update, delete). However, there is no support for workspace-level events, such as workspace deletion. This creates a gap where admins cannot: Monitor or get alerted on workspace deletions Prevent or respond quickly to accidental or unauthorized deletions Maintain proper governance and audit visibility Request support for workspace lifecycle events (especially workspace deletion) in Real-Time hub alerting and Fabric Activator. ... View more

Having an extra warning when you click the delete button in a power bi report (app). I've had multiple users deleting personal bookmarks by accident   ... View more

Problem Description In OneLake security, when a user is a member of multiple security groups or roles that apply different access rules to the same object, table, column, or row, conflicting permissions can result in overly restrictive behavior—often blocking access entirely. This is challenging in enterprise environments where users frequently belong to multiple roles across domains, projects, or departments. Instead of enabling fine-grained access, the current behavior can unintentionally deny access completely, even when there is a valid overlap in permissions. Expected Behavior When multiple roles apply to the same object: The system should support resolving permissions using the intersection of all roles Users should retain access to: Rows allowed across all roles (AND logic) Columns allowed across all roles Objects permitted across all roles Instead of blocking access completely, the system should enforce the most restrictive valid access. Actual Behavior Conflicting roles may result in: Full denial of access Unexpected permission failures Overlapping permissions are not leveraged Difficult to understand and troubleshoot effective access Proposed Solution Introduce a configurable feature (toggle or policy setting) for handling role conflicts: 1. Configurable Conflict Resolution Mode Allow administrators to choose between: Strict Mode (current behavior) Conflicts result in blocking access Intersection Mode (new option) Effective permissions are calculated as the intersection of all roles: Row-level: AND filters applied Column-level: only shared allowed columns Object-level: access only if permitted across roles 2. Scope of Configuration The setting could be applied at different levels: Workspace level Domain level Individual dataset / item level 3. Transparency & Debugging Provide tooling to: Show effective permissions after role intersection Highlight which roles contributed to restrictions Help admins understand why access is granted or limited 4. Backward Compatibility Default behavior remains unchanged (strict mode) Organizations can opt in where needed Enables gradual adoption based on security strategy Impact Reduces unnecessary access failures Enables scalable multi-role security design Simplifies administration in complex environments Improves user experience and trust in security model Business Value Supports real-world enterprise security patterns Encourages adoption of fine-grained access controls (RLS/CLS) Reduces support overhead and troubleshooting time Provides flexibility to meet different compliance and governance needs Additional Context This is especially valuable in organizations where: Users belong to multiple teams/projects Security is managed centrally via groups Both row-level and column-level security are extensively used A configurable model ensures Fabric can support both: Highly secure “fail-closed” environments Flexible, data-sharing-friendly environments ... View more

In Microsoft Fabric, copy activities are currently blocked if there is a reference to a linked dataset from Google Cloud Platform (GCP) that has been removed or unlinked from the project. Even if the dataset is no longer actively used in the pipeline logic, the presence of this stale or broken reference causes the entire copy job to fail or be blocked during validation or execution. This creates unnecessary operational friction and prevents pipelines from running successfully.   Fabric should: Allow pipeline execution even if unused or stale linked datasets exist Provide clear warnings instead of blocking execution Automatically ignore or gracefully handle broken/unlinked external dataset references that are not actively used in the current run ... View more

Great, I would like to have possibility to set simple slicer (for example date slicer) to the last year, last month, ... So at landing page people will not have to click for last year, month ,...etc Of course in the slicer should be also visible other options (choices)         ... View more

It would be great if we could navigate to the desired measure/column with one click of the left mouse button in the Data panel (as shown in the screenshot). At the moment, we have to manually repeat the name in the search panel in Data, which is annoying and feels like a redundant action.   ... View more

"Reset button" on the server currently act as global level reset the dashboard. We are requesting feature that allows this reset behavior to the individual user level. ... View more

Imagine if I could make a Power BI report available in light mode, dark mode, and a custom high contrast mode, using a custom theme for each.   Instead of users seeing the "High-constrast colors" menu in the UI, they would see "Change theme".  Then the list would start with the themes provided by the report developer, then list the high contrast modes. ... View more

Please fix this: The owner of the lakehouse cannot be a service principal for security sync to work.   https://learn.microsoft.com/en-us/fabric/onelake/security/sql-analytics-endpoint-onelake-security#limitations   We want to use Service Principal (not personal user) to be the owner of the Lakehouse. ... View more

It would be very helpful if Power BI supported a feature to constrain movement when dragging visuals: Hold Shift while dragging a visual Movement locks to horizontal or vertical (keeping X or Y position fixed) Currently, maintaining alignment while dragging requires using gridlines, guides, or re-aligning afterwards, which can slow down layout work. This behavior is available in tools like Canva and Adobe Illustrator and would make report layout much faster and more intuitive in Power BI! Power BI Desktop, Usability, User Experience, Design, Report Layouts ... View more

Hi Team, Good day. I would like to propose an idea for consideration regarding report security and user experience in Power BI. Currently, we are implementing Row-Level Security (RLS) and Object-Level Security (OLS) based on defined rules to control data access. As an enhancement, it would be highly beneficial if we could extend this capability to also control page-level visibility based on user access. Example scenario: User 1: Access to Page 1 and Page 2 User 2: Access only to Page 2 In this case, it would be valuable if Page 1 could be completely hidden from User 2, rather than just restricting the data within the page. This would improve report usability, maintain cleaner navigation, and enhance overall user experience. Thank you for considering this suggestion. Please let me know if any additional details are required. Thanks, Srikanth Talluri ... View more

Hi Team, Good day. I am in the process of logging an idea and would like to share a suggestion for consideration. In my report, I am currently utilizing multiple bookmarks, with each page containing its own set of bookmarks. At present, we have the ability to set a landing page as the default. Extending this functionality to allow a specific bookmark to be set as the default within individual pages would be highly beneficial. This enhancement would improve usability and provide greater control over the initial view for each page. Thank you for considering this suggestion. Please let me know if any additional details are required. Thanks, Srikanth Talluri   ... View more

Detailed Description Today, Power BI Service executes dataset refresh operations independently and often in parallel within the same workspace. There is no native mechanism to define execution order, priority, or dependencies between datasets. This creates operational challenges in environments with multiple datasets competing for shared resources such as on-premises data gateways, capacity (Premium or Fabric), and source systems. In scenarios with large and small datasets scheduled for refresh at similar times, the lack of orchestration can lead to: Resource contention on gateways (CPU, memory, connection limits) Increased refresh failures due to overload or timeouts Unpredictable refresh completion times Difficulty meeting SLA requirements for critical datasets Inefficient use of capacity when heavy datasets start after lighter ones Real-world scenario An environment with 30 to 50 datasets: 5 large datasets (each taking 30 to 60 minutes) 25+ smaller datasets (5 to 10 minutes each) When all refresh jobs trigger at the same time: Smaller datasets start first and consume gateway slots Larger datasets are queued or throttled Overall refresh window increases Failures occur due to long wait times or source system limits Current workarounds To control execution order, teams must implement external orchestration: Fabric Pipelines or Data Factory pipelines Power Automate flows Custom scripts using Power BI REST API Dataflows as intermediate dependency layers These approaches add complexity, require additional infrastructure, and increase maintenance overhead.   Proposed Enhancement Introduce native refresh orchestration capabilities in Power BI Service: 1. Dataset Priority Allow assigning priority levels: High Medium Low Scheduler executes higher priority datasets first. 2. Refresh Order Control Allow defining explicit execution order within a workspace or schedule group: Example: Dataset A (large) Dataset B Dataset C 3. Dependency Management Allow datasets to depend on others: Dataset B starts only after Dataset A completes successfully Support simple dependency chains and DAG structures Expected Benefits Predictable refresh execution Better SLA compliance for critical datasets Reduced refresh failures Improved gateway and capacity utilization Elimination of external orchestration dependencies Simpler operational management Business Impact Organizations with enterprise-scale deployments face real constraints in managing refresh workloads. Native orchestration would reduce operational complexity and increase reliability, especially in regulated environments where data freshness and availability are critical. Summary Power BI needs built-in control over dataset refresh order, priority, and dependencies to support enterprise-scale workloads efficiently and reduce reliance on external orchestration tools. ... View more

Enable Native Fault Row Logging for Lakehouse/Warehouse in Copy Activity.   Currently, while using Copy Activity in Microsoft Fabric pipelines, handling faulty or incompatible rows requires custom implementation. Although fault tolerance options exist (such as skipping incompatible rows), there is no native way to persist these rejected records directly into a Lakehouse or Warehouse for analysis. ... View more

Currently, On-Object Interaction is only available in Power BI Desktop and is not supported in the Fabric web report editor. This forces users who work primarily in Fabric to fall back to the old Visualizations pane, which is less intuitive and slows down the report authoring workflow. Please bring On-Object Interaction to the Fabric web editor so that users can enjoy the same modern authoring experience regardless of whether they are working in Desktop or in the browser. This would significantly improve productivity for teams that use Fabric as their primary authoring environment. ... View more