Currently, colors are automatically assigned randomly.  It would be nice if your dev workspace was always blue, and your prod was always pink for example.  Then you'd have a good visual as to where you're working in. ... View more

Hello Team, We have noticed that in our Power BI Service, the Viewer role on a workspace no longer provides Build permissions for datasets as it did previously. Even when Build permissions are manually granted, users with Viewer access still cannot see the datasets in the workspace—they can only view reports. We would like viewers to have the same access as before, so they can see and connect to datasets in workspaces where they have Viewer access. Please look into this issue so that viewers can rebuild reports as needed, which helps keep production environments secure without requiring everyone to have Contributor roles. ... View more

We need the ability to send email only when data exists to be sent. ... View more

The usefulness of tags would be greatly increased if Tags was a column in the Workspace view and the OneLake Catalog view. Perhaps it could be a configurable preference setting.  The current filtering functionality is great, but having better visibility in a list view would increase productivity since the user would not have to hover or click through to get each individual items tag(s). ... 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

Identify users with Power BI Pro licenses that come with the E5 subscription. We need a way, either through a REST API or a UI, to display all users utilizing the Pro license features assigned via E5. ... View more

To address the challenges of organizing and presenting data due to the limitations of column and row headers, a potential solution would be to implement a new matrix visual with customizable controls, allowing report creators to adjust the dimensions of columns and rows, group them hierarchically, apply diverse styles, and use conditional formatting. ... View more

I would like to request the addition of a Kintone connector for Power BI. Kintone Official Website (US) Kintone Official Website (Japan)   By enabling seamless integration, we expect to unlock greator value from both platforms - leveraging Kintone's data capabilities and Power BI's powerful analytics and visualization features. In response to customer requests, we developed and provided a custom connector for Kintone. https://cybozu.dev/ja/id/90125c111898e77ad9a26618/ (Japanese only) ... 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

When I look at the Version History, I see only who made changes to the previous versions, but not who changed the current version: It would be very helpful to see, who was the author of the last changes. ... 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

We're using Power BI Embedded in the App Owns Data scenario in our web application. In the Embedded Analytics Playground we can see Export Visual Data Summarized Export Visual Data Underlying What we *need* is to be able to call "Export Visual Data with Current Layout" as is provided by the built-in Export Data options menu item, but without making the user of the embedded application go through the UI (and also be able to style the dialog we present, add logging of who exported what etc. etc.) Is this API available, but no documented? Is there some trick that we can use to invoke whatever the built-in export does?   ... View more

Request: The “Export Data” to excel option is currently hidden under the small three-dot menu on visuals, which is not intuitive and easy to miss for many users.   Suggestion: - Add a visible “Export Data” button on the visual or in the ribbon - Or provide a quick-access option for exporting data. ... View more

Data segmentation visual, configured as a dropdown, is overlapping the main panel, as shown in the image above. ... View more

Sinto falta de um recurso que destaque as colunas e medidas que estão sendo utilizadas no relatório. Por exemplo, às vezes quero excluir uma medida, mas não sei se ela está sendo usada em algum visual do dashboard. Seria muito útil ter um indicador mostrando se e onde cada medida ou coluna está sendo utilizada.   ... View more

Ter mais opções de ícones nas formatações condicionais, as vezes sinto falta de alguns ícones específicos, como seta para baixo verde. Seria legal se pudessemos personalizar/escolher nossos próprios ícones também!  ... View more

As of today, Semester isn't available as a Category when creating Calendars. Why is it not available, as this is a standard period in calendars?   Please add it as a new Category. Even though there is no Time Intelligence function for the Semester, several of my clients use it for reporting. ... View more

Hello Everyone, I'm working with a customer using a Fabric PAYG capacity. They typically run their capacity for only a few hours per day, yet experience unexpected spikes in CU consumption at pause/resume time.   The Problem: Background operations are smoothed over a fixed 24-hour window. This works well for Reserved Capacities that run continuously, but creates an unfair billing situation for PAYG customers who pause their capacity.​   Example: Customer runs an F32 capacity for 1 hour A background job consumes 11,500 CUs (10% of the hourly F32 budget) With 24h smoothing, only 11,500 ÷ 24 = ~480 CUs are "repaid" during that 1 hour of uptime When the capacity is paused, the remaining ~11,020 CUs become billable overages, even though the F32 had enough capacity to fully absorb the job within that hour   Proposed Enhancement: Allow PAYG customers to configure the smoothing window (e.g., 1–24 hours) or provide an option to disable smoothing entirely. This would let customers who run short capacity windows properly utilize their provisioned CUs without losing capacity to the 24-hour smoothing assumption.  Reserved capacity customers benefit from 24h smoothing because their capacity runs continuously. PAYG customers, by design, start and stop their capacity—yet the current smoothing mechanism penalizes this usage pattern. ... View more

We need support for Service Principal authentication when creating Lakehouse connections.   Right now, Lakehouse connections can only be created using a user account. As a result, Dataflow Gen2, Pipeline copy activity, and Copy Job cannot use a Service Principal (SPN) when connecting to a Fabric Lakehouse as a source or destination.   This is an issue for us. We want to avoid user-based connections because: We need environment-specific identities (dev/test/prod) to prevent accidental cross-environment writes (e.g., dev pushing data to prod). Tying connections to personal user accounts creates fragility - things break when someone leaves the project or the organization. Service Principal support for Lakehouse connections is required to ensure secure, reliable, and environment-isolated authentication.   The screenshot shows that only user authentication is available, not service principal authentication. ... View more