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

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

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

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

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

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

Hi Team, We are facing limitations when trying to deeply analyze how users and workloads consume Fabric/Power BI capacity. Currently, the Capacity Metrics App provides a high‑level overview, but it does not offer sufficient granularity to fully understand how specific APIs, operations, or workloads impact capacity behavior. From a governance and operational standpoint, we need more detailed insights to accurately assess performance, identify inefficiencies, and build internal monitoring or optimization solutions. Suggested Improvement Introduce enhanced telemetry and reporting capabilities that include: Breakdown of capacity consumption by API / operation level Visibility into workload-level consumption patterns User-level consumption mapping tied to actions Exportable detailed logs/metrics for custom internal analysis ... 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

Problem Fabric ontology can be generated from a semantic model with one click — but customers still have to build the semantic model manually. For a lakehouse with 100–200 Gold tables, that's days of click-by-click work to select tables, define relationships, mark date tables, and create measures. Customers with 5,000+ tables and 300–800 ontology candidates often estimate 3–4 weeks of manual effort before they can even start with ontology. This is a major adoption blocker for Fabric IQ. What would help Any form of automation or AI-assisted bulk creation of semantic models directly from lakehouse metadata — using schema, profiling, lineage, or Copilot — would dramatically shorten the path to ontology. Even partial automation (e.g., relationship detection on user-selected tables) would be a meaningful first step. Anyway to automate the creation ? not fully but a base atleast ? Why it matters Snowflake (Semantic Views Autopilot), Databricks (Genie), dbt, and AtScale already automate this. Fabric is behind on this specific capability, despite having stronger downstream features (ontology graph, Activator, agents). Closing this gap would accelerate Fabric IQ adoption for the enterprise segment with the largest data estates. ... View more

Summary As of Power BI Desktop March 2026 (v2.152.x), dropdown slicers visually accept keyboard input but no longer perform any filtering. Typing is silently ignored with no error, toggle, or UI indication. This behavior previously worked and appears to have been removed without notice. Description Dropdown slicers still present a visual affordance that suggests typing will filter values (cursor focus, keystroke acceptance), but no filtering occurs. This creates a false affordance: the control appears interactive, but user input has no effect. The only way to enable search is to change the slicer style to List and enable Header → Search. There is no in‑product guidance indicating that search is now List‑only, and no indication in the dropdown slicer UI that typing is unsupported. This behavior disproportionately impacts enterprise datasets with high‑cardinality fields such as Work Item IDs, Ticket Numbers, or Account IDs, where dropdown slicers were historically usable via typing. Steps to Reproduce Open Power BI Desktop March 2026 (v2.152.x) Add a slicer visual Set Style = Dropdown Bind the slicer to a text field (e.g., formatted Work Item ID) Click the dropdown and type any characters Result: No filtering occurs. Typed input is ignored. Expected Behavior One of the following: Typing filters dropdown slicer values (previous behavior), or Dropdown slicer disables text input entirely, or UI guidance indicates that search is supported only in List slicers Actual Behavior Keystrokes are accepted visually No filtering occurs No warning, tooltip, or setting explains the behavior Impact Significant analyst time wasted troubleshooting data types, sorting, and slicer configuration Erosion of trust in Power BI UI consistency Repeated rediscovery of the same regression across teams Increased support burden in large enterprise environments Suggested Fix Restore typing‑to‑filter behavior for dropdown slicers, or Remove the typing affordance from dropdown slicers, or Add explicit UI messaging (e.g., “Search available only in List slicers”) Classification UX regression / breaking change without discoverability Final Thoughts If this behavior is intentional, could the dropdown slicer disable keyboard input or surface guidance that search is List‑only? ... 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

Currently, when Disaster Recovery is enabled at the capacity level in Power BI, the platform automatically performs near real-time geo-replication of data to a secondary (paired) region. However, from a user and administrator perspective, there is no visibility into the replication status or health of this process. Users are requesting the ability to confirm and monitor that DR is functioning as expected. ... View more

When a report page contains multiple sections such as Sales, Finance, etc., providing expand and collapse functionality would help users easily view or hide all visuals within each section.     ... 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