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

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

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

users are working with Microsoft Fabric deployment pipelines in  environments where Dev → Test → Prod promotion is required. Limitations  Lakehouse deployment fails when shortcuts exist Pipelines do not support deployment of Lakehouses with active shortcuts Requires manual removal and recreation Connections are not environment-aware After deployment, connections still point to source (Dev) No native parameterisation support Cross-workspace data sharing limitations Unable to directly create shortcuts on Warehouse tables across workspaces impact with workarounds : Manual effort increases significantly post-deployment Time-consuming and error-prone for large-scale deployments High risk of configuration drift across environments   It would be highly beneficial if these limitations could be addressed in the product, or if a more robust and scalable alternative approach could be provided to support enterprise deployments. ... 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

There needs to be a way to view user names stored with connections under Manage Connections and Gateways or through some other means.  As an enterprise with lots of connections using various service accounts, in which we need to do password re-sets on a regular basis, we need a way to know which connections are using which accounts.  The On-Prem Power BI Report Server provides this level of granularity, there is no reason Power BI Service can't provide the same.  Without this, managing these connections is almost impossible. See below comparison. ... View more

Currently, Activator rules only sends email notifications to individual internal email addresses. It would be very beneficial to allow Activator rules to send emails directly to Microsoft Exchange Distribution List as well.   This will make notification management easy for developers. Instead of updating recipients individually within each Activator rule whenever team members join or leave, administrators could manage membership directly through the Exchange Distribution List.   This will reduce effort require for maintenace and help ensure notifications always reach the correct audience.   This enhancement will be useful for teams, support groups, and large organizations where notification recipients change frequently.  ... View more

Hi Team, Hope you are doing well!   Now: Testing Row-Level Security today requires publishing to production first. There is no safe way to validate who sees what before going live. Misconfigured roles are only discovered after the fact, a direct governance and compliance risk.   GOAL : A native testing pane inside the Power BI Service where developers can simulate any role, impersonate a specific user by email, and immediately see which rows and tables are accessible, without touching the live environment. Three capabilities: role simulation without publishing, per-table access visibility, and an automated assertion suite that flags regressions whenever the data model changes.   Why ? Security incidents caused by misconfigured RLS are entirely preventable. This feature makes them so. It also reduces the time developers spend on manual validation cycles from hours to minutes, and provides compliance teams with a formal, exportable audit record of every validation session.   Thank you for considering this, I believe it would be a great addition to the Fabric and power bi experience ... View more

Currently, we understand that users can reference shared cloud connections within the Variable Library . However, connections created through On-Premises Data Gateway (OPDG) and VNet gateways are not supported in this experience.   We would like to request support for OPDG gateway connections to be available as selectable connection references in the Variable Library. This enhancement would significantly improve the overall user experience and align the Variable Library feature with broader connectivity scenarios commonly used by customers. ... View more

The ability to hide specific pages for a report based on the audience they belong too in a power bi app. ... View more

Customer wanted to know how they can get a notifications for upcoming Power BI preview features before they are pushed and enabled in the tenant settings. Not using the below options: Preview features are announced externally first (blogs, newsletters, events) Check Power BI updates blog (monthly drop) The most reliable proactive model is: Blog + Newsletter + Enablement sessions + RSS tracking     ... View more

Power BI Pipelines have been very helpful in CI/CD process between dev/test/prod workspaces - WHEN artifacts are created in Power BI Desktop and published to the service.   Now, we are hoping to move more towards in-service development and cut out the Power BI Desktop. However, the deployment piplinee does not detect/recognize changes to a reported that are done in the service.  For example, a business edits a report in the production workspace - adding a new page and chart visual.  The pipleine does not recognize that edit, so it can easily be overwritten by a future update from the dev/test workspace.   Reasons for adopting in-service development: Microsoft continues to improve the in-service development capabilities.  Recent releases allow createion and editing of semantic models and reports in the service. Some artifacts can only be created in service, such as dataflows.  Org apps is another artifact type that may qualify. We want to expand Power BI adoption outside of IT department into the hands of business users.  Our goal for IT to create robust semantic model and then for business users to create their own reports using the avilable in service tools.  For business users, creating a report or chnaging an existing report in service may be the easiest, least technical way.   ... 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

I would suggest to introduce "folders" to have new connections organized in a easier and segregated way. In a Enterprise environment, wheer all teh connecitons to resources are managed ina  centralized way, having the possibility of creating folders, as in the Workspaces, would allow better organized resources (e.g. Like in the Deployment pipelines). Thank you for the opportunity, Alfredo Lourido Santos ... View more

Having the ability to run python code outside of the notebook environment (like we can for pyspark jobs) could be a real win for efficiency and modularity. It would allow users to package robust, unit-tested code and deploy it to the fabric environment where it could run as a cost-effective single-node job. Databricks has an implementation for this, and it would be really nice to see something similar come to Fabric. Notebooks are great for ad-hoc or exploratory stuff, but building something robust in them feels like shoving a peg into a wrong-shaped hole. They are (nearly) impossible to unit test, so you often end up creating libraries which allow you to package transformations in a way that can be tested, then your notebooks end up being essentially thin wrappers around a bunch of external code. I think the most obvious example for this is the number of Fabric DBT implementations that essentially involve installing DBT core into a notebook and running it there (I know there is DBT jobs coming, but this is beside the point). This is a symptom of a larger need for this type of hosting/execution of code within the environment. Yes, you could host the code on a vm external to Fabric but that goes against the ethos of a unified data platform. Offering something like this would be a great way to increase the flexibility and extensibility of the platform. The implementation can be fairly barebones and developer forward, aiming to provide maximum flexibility and extensibility. Basically a way to run python scripts/CLI tools on the Fabric capacity.    ... View more

We would like to request support for a direct private connectivity path between Power BI Service and Azure Databricks, such as Azure Private Link (or an equivalent service-managed private endpoint), that bypasses the need for a VNet Data Gateway seralize/deserialize stage. Currently, when connecting Power BI Service to a Databricks workspace configured with private networking (no public endpoint), the only supported approach is through a VNet Data Gateway or On-premises Data Gateway. While this enables secure connectivity, it introduces additional overhead due to the serialization and deserialization of data through the gateway layer. ... View more