Please add an endpoint to the Job Scheduler API where we can get a list of all failed runs.   The response from this endpoint should, by default, include all failed runs across all workspaces that the caller has access to, and include all item types.   The caller must specify a startTime and an endTime in the request, to only search for failed runs within that time interval.   Optionally, to narrow down the search further, the caller can specify: workspace IDs (list of IDs) item types (list of item types) item IDs (list of item IDs) The default should be to include all. ... View more

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

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

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

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

A Lakehouse Collation setting showing case sensitive vs non-case sensitive should be added to the exisitng lakehouse settings in Microsoft Fabric.  For years i've been able to change collations on a database on on-prem SQL and am able to re-populate those data tables to reflect the new collation moving forward.  This should be an option in Microsoft Fabric in the lakehouse settings which should allow me to change a collation on an existing Lakehouse without having to create a brand new Lakehouse and have to completely recreate anything in it's lineage such as semantic models, reports, etc.  Seems like we could do this for the last 20+ years in SQL and should be able to do this using a Lakehouse easily as well. ... View more

Currently I need to use Tabular Editor to make modifications to the collation assigned with any semantic models I create in Microsoft Fabric.  These collations appear to be a random bug and do not always inherit my lakehouse collation.  This causes issues when my users/customers try to analyze a semantic model inside of Microsoft Excel and try to filter data for a specific data value in the model that is case sensitive.  A button should be added to the semantic models settings that turns case sensitivity on or off.  As a work around, I am currently using Tabular editor to modify a semantic model and deploy a copy to Fabric.  This does not allow me to modify the existing semantic model, but create a new semantic model with the collation I want.  This should be an easy add/fix that should already be in Microsoft Fabric since it's kind of already in a 3rd party tool. ... View more

I would like if the Power BI Monitor Tab allowed users to create multiple custom filtered views and save them so that we can toggle back and forth or clear the filters without having to recreate them the next time. I am an admin for 18 workspaces (not all production), and need to check different combinations, and statuses (sometimes I want to see only the failures, other times I want to see what is in progres, etc), or I might want different combinations of columns visible/hidden. This tab is severerely under-utilized by me because of this.  ... View more

Similar to the Monitor page, where we can see what has run and what is currently running, it would be useful to see what's scheduled to run in the future. This to check that all schedules are set up as expected.   Reason: Easy and conveniently verify that all schedules are configured as expected. ... View more

Dark Mode for Power BI Service and Fabric. ... View more

Enable individual users / freelancers to study and practice fabric with a per-user license similar to Premium Per User in Power BI. F2 is a price point that is too high for them. Strong limitations in time and resources available would make sense, but there should be a clear monthly cap that cannot be like the current F2. ... View more

Hi there,   as a developer I want to have the option in the GraphQL item to choose if changes in the underlying tables are populated automatically or need manual update.  Automatic helps to bring more reliablility and automation in the whole lifecycle.  Manual options lets the user only populate validated changes to the API.  Currently as of 24.11.2025 the GraphQL API item does NOT automatically populate schema changes of underlying tables to the item. The tables needs to be reloaded either by "reload schema" or even deletion and new selection of tables.  Thanks and best regards! ... View more

I’m building a logic in my application that depends on the size of my Power BI or Fabric datasets. Currently, there’s no available API or endpoint to get this information. It would be really helpful if Microsoft provided a way (through the Power BI REST API or Fabric API) to retrieve the dataset size — similar to what is shown in Workspace Settings → System Storage (API) inside the Power BI service.   Having access to this value programmatically would help developers: Monitor dataset growth automatically Implement custom alerts and optimizations Manage workspace storage usage efficiently ... View more

Currently the only option for connecting to a lakehouse using a cloud connection is an organisational account. Adding in Service Principal as an option would avoid the reliance on single user accounts and would bring the lakehouse connector into parity with the warehouse connector. ... View more

This is purely for aesthetic and usability reasons.   Now that a default semantic model is no longer generated when creating a new Lakehouse, could we consider streamlining the user experience by merging the Lakehouse and its SQL analytics endpoint into a single item? At the moment, having them listed separately feels a bit redundant and visually inconsistent. Consolidating them would make the interface cleaner and more intuitive.       ... View more

Currently, with the new multiple scheduler feature, we can define multiple run schedules for a Fabric item. However, when using deployment pipelines, there’s no way to control which schedules are active in Dev, Test, or Prod. This means schedules intended only for Prod must also run in Dev, consuming unnecessary compute.   It would be very useful to allow using the Variable Library or deployment rules to set the active/inactive state of each schedule per environment, making deployments more efficient and flexible. ... View more

Please make it possible to use Managed Identity with Fabric items like Notebooks and Data Pipeline.   Benefits: No need to handle credentials. The item won't be related to a physical person. Then, we can give the Managed Identity access to read (and write to) data storage items in other Fabric workspaces, Azure SQL, ADLS, Dataverse, etc.   So that we don't need to rely on human users, and also don't need to handle credentials. ... View more

Currently, the Explore setting in Power BI (preview) can only be enabled or disabled at the tenant level, meaning it applies to the entire organization. Customers are requesting the ability to enable this feature for specific groups or subsets of users rather than globally. This would allow organizations to test and adopt the feature gradually without impacting all users, providing better governance and controlled rollout during the preview stage. ... View more

To make it easy to filter workspaces, and also enable cost chargeback scenarios, it should be possible to apply Tags to workspaces. ... View more