Problem Statement: Currently, Power BI only offers Row-Level Security (RLS) to control data access, but there's no native way to control which report pages users can see in the navigation pane. All users with report access can view all pages, even if those pages aren't relevant to their role. Requested Feature: Implement Page-Level Security (PLS) that allows report developers to: Define which user roles can access specific report pages Automatically hide pages from the navigation pane for users without access Prevent unauthorized users from manually navigating to restricted pages Business Use Case: Many organizations have reports with different sections for different audiences: Executive dashboards for leadership Detailed financial analysis for finance teams Operational metrics for operations staff HR metrics for HR department Currently, we must create separate reports or apps for each user group, leading to: Content duplication and maintenance overhead Multiple versions of similar reports to manage Increased workspace clutter Higher administrative burden Proposed Solution: Add a "Page Security" setting similar to RLS in Power BI Desktop Allow assignment of security roles to individual pages In Power BI Service/Apps, only display pages the user has permission to view Integrate with existing RLS roles for unified security management Benefits: Simplified report management (one report instead of many) Better user experience (users only see relevant content) Reduced administrative overhead Consistent with existing RLS security model More scalable enterprise deployment Alternative Considered: Creating multiple reports/apps works but creates significant maintenance challenges and doesn't scale well for large organizations with many user roles. ... View more

Although we all agree that Polars/Pandas/DuckDB is faster on single node, the Spark Engine has a strong, nearly bug free API that has many efficient implementations (e.g. one of the best Delta/Iceberg/Hudi Writers). It also offers Stream Processing across many matured data sources.   There's nearly 15 years worth of rich tutorials on Spark patterns. Copilot/AI is extremely proficient at producing high-quality Spark code. Data Engineers can be highly productive in Spark in a very short period of ramp up. It is also a great API to learn, since all hyperscalers offer a managed Spark runtime, so it's easy to find a Data Engineering role (job security etc.)   Spark Declarative Pipelines will also significantly reduce the barrier to entry to writing ETL code: Spark Declarative Pipelines Programming Guide - Spark 4.1.0-preview1 Documentation   But - due to the lack of a cheap/fast/single-node runtime, instead of taking advantage of these awesome API investments in Spark Engine, many Data Engineers who have smaller volume of data end up writing entire heterogenous API centric codebases, when they could just use the Spark API and it's innovations, so the code can scale out when the job needs to with simple config changes, or run in local mode when it doesn't need to.   Ideally, one day Fabric could offer a serverless Spark runtime, but until then, it might be fairly easy to tune up a single-node Spark runtime that is opinionated with spark configs that do not force shuffles. Perhaps NEE could back this runtime to reduce the memory footprint as well.   OSS Apache Spark can run pretty fast(er) on a single node if you tweak a few settings. The problem is, you need to be a Spark Expert to read these things and tweak it. It'd be good if Fabric could do this for laymans.   How to Speed Up Spark Jobs on Small Test Datasets How to cut the run time of a Spark SBT test suite by 40% | by Matthew Powers | Medium Setting Shuffle Partitions in order to limit the number of Tasks by qnob · Pull Request #291 · holdenk/spark-testing-base Spark Standalone Mode - Spark 4.0.1 Documentation   For non-distributed datasets on a single VM, Fabric could go ahead and provision a Spark runtime that is Executor heavy, say, on a 6 core VM, do this:   Here's an example of an opinionated spark config ```yaml spark:   local: true                           # Fire spark in local[*] mode   ui: false                               # Turn off Spark UI to save resources   offHeapEnabled: false        # Disable offheap   driverCore: 1                       # Driver doesn't do much, reduce it more if needed   driverMemory: "512mb"    # "   executorCore: 5                 # Executor does the most work, I'm not sure if odd numbers are allowed 🙂   executorMemory: "11.5g"  # "   shufflePartitions: 1             # Don't need shuffles on small data sizes ``` ... View more

We have issues where Power Quary requires realoding the dataset every time we need to work on it. Ideally, once the data is loaded, we should be abel to work on it without having to reaload it repeatedly. Please investigate this behaviour, as it impact workflow efficiency and incraeses processing time. ... View more

We have complex RLS and audiences in our PBI/Fabric Apps.  We need to be able to login as a user to view their experience.  There is no worse-way to get user adoption then to send a user to a dashboard just to find out there is something missing with their permissioning and they get an error or a blank screen.   Executive adoption of PBI will never get off the ground if we can't ensure a seamless experience. I am sure this is the case for most organizations.   Even better, I would be able to login as them to view their "home page" experience to pin favorites and ensure they are easily routed to the right reports.   ... View more

Currently, Power BI allows the option to “Show items with no data” for certain visuals, but this functionality is limited when using Line Charts with a Continuous axis type.  Allow line charts to display items with no data while keeping the axis type as Continuous. This would help maintain smooth scaling and date hierarchy formatting without forcing users to switch to categorical mode (which changes labels to raw date values). This enhancement would improve parity between visuals and provide better support for scenarios where users want continuous scaling and visibility of empty periods. ... View more

When I create a hierarchy in a table in a semantic model (Fabric), I can't see the hierarchy in a pivot table in Excel. I used this feature frequently with semantic models in PowerBI, and really liked it. ... View more

Description: Currently, when replicating tables from a SQL database to the SQL Analytics endpoint in Microsoft Fabric, all tables are included by default. However, not all tables are needed in the analytics endpoint. This creates unnecessary overhead and, in some cases, leads to lock situations in the SQL database during replication for certain tables. Problem: Some tables are not required in the analytics endpoint. Replication of these tables can cause locking issues in the source SQL database. There is no built-in mechanism to exclude specific tables from replication. Proposed Solution: Introduce functionality to exclude specific tables from replication. This should include: Explicit Table Exclusion: Ability to define a list of tables to exclude. Pattern-Based Exclusion: Support for regex-based patterns to exclude tables dynamically. Example: Exclude all tables ending with __b. Regex equivalent: .*__b$ Benefits: Reduces unnecessary replication overhead. Prevents lock situations on source tables. Provides flexibility for administrators to manage replication scope efficiently. ... View more

Fabric’s SQL endpoint currently fails when the feature.v2Checkpoint flag is present in Delta log history. This flag is automatically set when tables are written with v2 checkpoints, which is the default when adopting Databricks‑recommended practices like liquid clustering. This creates a critical gap: Databricks promotes v2 checkpoints and liquid clustering as best practices, yet Fabric’s SQL endpoint does not support them. The result is brittle workarounds that block enterprise‑scale adoption. Ask: Enable support for v2 checkpoint policy in Delta table shortcuts so Fabric can align with Databricks standards, eliminate fragile workarounds, and unlock enterprise readiness. ... 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

We would like information on which characters are supported or valid for workspace names, in the documentation. There should also be a description that gives an overview of the valid characters for workspace names in the Power BI service when creating a workspace. ... 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

Need to restore the feature that send refresh failure notifications to contacts for Dataflow Gen1. Currently, the notification is only sent to the Dataflow owner, and the option to add contacts in the refresh settings is missing. Previously, this feature allowed adding specific users to receive notifications when a dataflow refresh failed, which was very useful ... View more

Paginated reports to automatically pick up the refreshed semantic model data without manual intervention. This feature would ensure consistency between semantic model refresh and paginated report output, improving user experience and reducing operational overhead. ... View more

Need to implement a  feature when slicer is bound to a parameter,it's selection logic should be same like regular column slicer.when using a multi-select slicer with the “Select All” option enabled, selecting “Select All” correctly checks all values. However, when a user deselects any single value, the slicer automatically clears all other selections, leaving only the clicked selected value which leads to difficulty to users to deslect the required value ... View more

I need to conditional format the row header, not just the values section.   Also I would like to be able to format the font in bold/italic and be able to define complete rows (values including row headers) to be underline/overline. ... View more

When connecting to a semantic model currently, we have to use the workspace/lakehouse/warehouse unique id and semantic model unique id in order to analyze that semantic model.  Instead of using those unique ids attached to a very specific semantic model we should be able to have the ability to customize those unique ids to a static customizable user friendly names for ease of use and the best customer experience.  Currently if I want to analyze a semantic model in Microsoft Excel or another methodology, if I have to connect to that model with the unique workspace/warehouse/lakehouse id and unique semantic model id, why can't I use the user facing workspace name, lakehouse name and semantic model name?  Why are we using GUIDs in 2025?   Additionally, if I have a new model that needs to replace an existing model, I should be able to replace or rename that model to the existing model name and it should inherit the current model's lineage vs recreating and redeploying all the associated lineage items to the new model.  This would save so much development time it's ridiculous that there is no solution for this currently. ... View more

We would like to be able to modify a Power BI Connection authentication config via API.   For example, for BigQuery connections, we would like to update their Service Accout key-based authentication config programatically: this would eliminate toil for people with several connections and periodic mandatory key rotations.   References: Power BI REST APIs for embedded analytics and automation - Power BI REST API | Microsoft Learn Google BigQuery connector - Power Query | Microsoft Learn ... View more