If you create a process that loads data in parallel to the Data Warehouse using the Spark Connector you may receive 429 Errors. It would be great if there was an option to retry with delay for specific error codes, like dataframe.write.options('retryIfError',429, 'retryWait',30)   ... View more

Problem Statement: In Microsoft Power BI Desktop, report development often requires working with multiple panes simultaneously (Fields, Visualizations, Filters, Bookmarks, Selection, etc.). When several panes are kept open on the right-hand side, the available space for the report canvas is significantly reduced. This creates challenges such as: Limited visibility of the report layout Frequent resizing of panes and canvas Reduced efficiency when designing complex dashboards Poor experience for users working on smaller screens Business Impact: This limitation directly affects developer productivity and report quality: Reduced design precision because of constrained canvas space Inefficient utilization of multi-monitor setups (which I believe are common in enterprise environments) Friction for power users handling complex reports with multiple visuals Proposed Solution: Introduce a pop-out / detachable report canvas feature in Power BI Desktop. Key capabilities could include: Ability to detach the report canvas into a separate window Support for drag-and-drop across multiple monitors Independent resizing of panes and canvas Option to dock/undock panes dynamically Example Use Case: A report developer using dual monitors could: Keep all configuration panes (Fields, Filters, Visualizations) on the primary screen Move the report canvas to a secondary screen in full view Design and interact with visuals without space constraints This would significantly improve usability, especially for complex dashboards. Expected Benefits: Enhanced developer productivity Better utilization of multi-screen setups Improved dashboard design experience Reduced dependency on constant UI resizing This feature would align Power BI Desktop with modern development tools that support multi-window workflows and significantly enhance the user experience for professional report developers.   Sample Image ... View more

Anyone who uses PowerBI long enough has had a PBIX with 50-60 measures and it has become time consuming and tedious to mantain. In Excel you can do a quick find/replace to edit several formulas - in PowerBI you need to select each one individually. An "excel-like" interface for editing measures would save a lot of time! This would take PowerBI to the next level regarding productivity. I've prepared a mockup for this as well as a DAX Editor. Let me know what you think. Mockup: https://i.imgur.com/z6TBOQb.png?1 ... View more

Summary Add an advanced context-menu option on standard visuals that allows users to view and edit the visual’s JSON directly from the Power BI canvas. Problem Statement Today, advanced users increasingly rely on editing visual JSON to apply formatting or behavior changes that are not currently exposed through the Power BI Desktop UI. The only way to do this is by saving the report as a .pbip project and manually editing the visual JSON files. While powerful, this workflow: Is unintuitive and error-prone for many users Requires leaving the Power BI canvas and working directly with project files Discourages experimentation due to the risk of breaking the report Creates a barrier for users who are comfortable with JSON but not with the .pbip file structure or source control workflows As a result, many users are editing .pbip files simply to unlock visual customizations that feel like they should be available in-context. Proposed Feature Introduce an Advanced option in the visual right‑click context menu (or Format pane) such as: Right‑click visual → Advanced → Edit Visual JSON This would: Open a modal or side-pane JSON editor scoped only to the selected visual Display the current visual definition JSON (read/write) Validate changes before applying them Allow users to revert to the previous state if the JSON is invalid Optionally, this could be gated behind: A preview feature flag A warning or “advanced users only” acknowledgment Read-only mode with an explicit “Enable Editing” toggle Benefits Improves productivity by keeping advanced customization in the canvas where users are already working Reduces friction compared to editing .pbip files directly Encourages experimentation with faster feedback and safer iteration Aligns with real-world usage—many users are already editing visual JSON today, just through unsupported workflows Future-proofs the product by allowing advanced users to access new or undocumented properties without waiting for full UI support Why This Matters Power BI already exposes the full visual definition internally; this feature simply makes it accessible in a safer, more discoverable, and more user-friendly way. Similar to how Tabular Editor exposes advanced model metadata, this would serve power users without impacting the default experience for most users.   This capability would significantly reduce reliance on .pbip file manipulation while empowering advanced users to push Power BI visuals further. ... View more

The new "view usage metrics report" does no longer support dashboards - it only works for Power BI reports.   And the "old" usage metrics report does no longer give back any values for dashboard usage.   It would be great to have this standard feature back, The old usage metrics would again give back usage values for Dashboards, or The new usage metrics would work for Dashboards, too Thanks a lot, in advance! ... View more

If multiple users want to work with the same Dataflow Gen 2, they currently need to take over ownership, which can be challenging for users in the future. It would be helpful to have an option like workspace permission support, allowing users to edit Gen 2 without needing ownership. ... View more

Hi Community, As someone who has taken advantage of the .pbip folder structure and git integration with PBI I am very pleased with the functionality but I have noticed a few items that would be an improvement over the current setup. For reference, I am utilizing a general workflow of staging branch linked to dev workspace, main linked to prod workspace, devs create feature branches from staging and then PRs are opened into staging from feature and then PRs off of release branch from staging is opened with main. On each successful commit to staging or main a github action runs that syncs the branches contents with the online workspace. Now this brings me to my point, there are times when devs would like to make a minor change directly within the workspace. I want to get this changes tracked and incorporated in git; however, there is currently only the option for commitng directly to the linked branch or creating and commiting to new branch (and then you could follow the stated dev cycle I outlined above assuming you create a new branch) BUT it would be greatly appreciated if you could open a PR from what is in the online workspace with the linked branch because my staging and main branches are protected and no commits can be made directly to then without review. I am curious if anyone else has a similair experience or if this would be helpful for them? Please a few screenshots below for reference.    Any interaction on this post is greatly appreciated.   ... View more

If it was possible to offer a robust and customizable style management system for the matrix, it could be the key to enhancing the professional appearance of tables and matrices. Further, giving report creators the ability to adjust gridlines, color, style, and the addition of custom icons, bars, sparklines, and other elements, along with a variety of pre-designed styles, would significantly improve style management options for tabular elements. ... View more

The Dynamics 365 Business Central connector in Power Query only supports authentication using a user account.   Please add support for Service Principal authentication using Azure AD App Registration with Client ID and Secret.   This would allow automated refresh processes and remove the dependency on personal user accounts.   Business Central APIs already support Service Principal authentication so enabling it in the Power BI connector would greatly improve enterprise scenarios and Microsoft Fabric integrations. ... View more

Power BI currently does not provide any native method for administrators to track where organisational visuals are being used across the tenant. The following limitations create significant governance and compliance challenges: Activity Logs / Audit Logs record high‑level actions (e.g., ViewReport, ExportData) but do not log which organisational visuals appear in a report.  The only current method to identify uncertified visuals is to manually or programmatically inspect report definitions / PBIX files, which is impractical for large organizations.  When an uncertified visual is added to Organizational Visuals, it becomes available to the entire tenant, with no ability to restrict usage at a granular (e.g., to security groups) level, complicating governance. This gap makes it difficult for administrators to ensure compliance, manage third‑party risks, and perform internal audits. Enhancement:  Ability to track organisational visuals in Activity Logs / Audit Logs. Ability to restrict the usage of organisational visuals through security groups. ... View more

When editing an Import mode semantic model in the Power BI service, the Refresh operation always runs an "Autodetect relationships" step at the end — even when the source .pbix has both "Autodetect new relationships after data is loaded" and "Update or delete relationships when refreshing data" disabled under Current File > Data Load options.   These per-file settings are intentionally turned off for models with complex or carefully managed relationship structures, but the web editor appears to ignore them entirely.   Expected behavior: The web editor should respect the Data Load settings already defined in the semantic model metadata. Ideally, these settings would also be exposed in the web editing experience so they can be viewed and modified without needing to download to Desktop.   Current behavior: Autodetect relationships runs on every refresh in the web editor regardless of the existing setting. This adds unnecessary processing time (especially on capacity-constrained Fabric workspaces with large models) and risks creating unintended relationships.   Workaround: None in the web editor. The only option is to monitor for unwanted relationships after each refresh. This is documented as a known gap — the Microsoft docs state that "Data Load settings defined in the Options dialog in Power BI Desktop aren't available for viewing or modification in the web experience" — but the expectation is that existing settings should still be honored even if they aren't yet editable in the browser. ... View more

User was granted Viewer access to a Power BI Workspace App only, without any permissions at the workspace level. Despite this limited access, when the user selected “View semantic model”, the full semantic model details including schema, tables, and measures were visible. To verify this behavior, we performed multiple tests: Created a Power BI App and assigned Viewer access to a test user. The user could view the report. The user could also see the semantic model contents when clicking View semantic model. Assigned Viewer role at the workspace level. The behavior remained the same the semantic model’s tables and measures were still visible. Removed all workspace roles and shared the report directly with the user. The user was still able to view the semantic model schema via the App. User want to hide the view semantic model option, tables and measures to other users.  ... View more

Hello, I would like to request an enhancement to the Page Navigator visual so that it offers the same layout options available in the Button Segmentation Slicer.                                 Layout options: Orientation: horizontal / vertical / grid Style: blocks / full screen Number of columns Automatic grid Spacing (gap) between buttons Overflow style: paginated / continuous scrolling (scroll)           These same options are not available in the Page Navigator, which limits the use of this visual in reports that rely on button-based navigation. I request the evaluation of this feature, allowing the Page Navigator to offer the same layout configuration options as the Button Segmentation Slicer. This enhancement is relevant in scenarios with a large number of pages, where navigation needs to be intuitive, reducing the need for alternative solutions and manual customizations. ... View more

Today, semantic model version history helps restore snapshots for a single semantic model, but it doesn’t provide an environment‑to‑environment diff or reconciliation report. Customers need an automated compare/diff view (tables/measures/relationships/RLS) across environments to safely replicate PROD changes into UAT and audit “who changed what”. Request: extend/version history & deployment experience to include cross‑environment change tracking and comparisons (not just per‑model snapshots). ... View more

I have a potential client for streaming data and real time dashboards. I'm setting up a mock up, pushing data every few seconds. Everything is connected, but the Real Time Dashboard is 15 MINUTES behind, and losing ground. I understand that Microsoft took away the ability to set a dashboard to refresh automatically and refresh is now controlled by MS/Fabric.  Please bring back the ability to have a real time dashboard configure for automatic refreshes. If you are worried about capacity or for whatever reason it was disabled, start broad, like every minute instead of every few seconds. Honestly, what good is 'real time' data of I cannot actually see it in real time? ... View more

  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

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

Currently high concurrency session is available only under strict rules.  as of now: Session sharing conditions include: Sessions should be within a single user boundary. Sessions should have the same default lakehouse configuration. Sessions should have the same Spark compute properties. If we could reuse high concurrency session between multiple users, that would improve usability in big teams where a lot of people run may small task at the same time. All other conditions can be met. ... View more

Enable users to configure the refresh frequency of shortcut transformations so they can balance data freshness and cost. This would allow users to choose between near real-time usage when up-to-date data is required and lower-frequency refreshes when they want to reduce cost and ingest data more easily. ... View more