In Power BI, we can publish PowerBI files into a Workspace & configure Audiences through a Power BI App.   Each Audience can be granted access to specific Power BI files within the App, by clicking the eye icon to show/hide the Power BI file for that Audience.   However, there is currently a limitation: Access can only be controlled at the Power BI file level, not at the report view-page level within a power BI file. For example, an Audience can be granted access to a Power BI file within the App, but once access is provided, the user is able to view all report view-pages within that Power BI file. There is currently no capability to restrict visibility so that an Audience can only view specific report view-pages while other report view-pages remain hidden.   The functionality that we are requesting would allow the ability to configure report view-page level visibility within a Power BI file within the PowerBI App. This enables different Audiences to see only the report view-pages relevant to them. This  solution would mean: There is only 1 Power BI file to maintain/refresh/publish/governance/etc. We have the ability to easily click the eye-icon next to each report view-page in the App, to show/hide it from each Audience. This reduces the risk of breaching privacy laws/people seeing data they aren't meant to. Reduces risk of version inconsistencies and reporting errors accross all versions.   Currently, the only practical workaround is to create multiple (ie x10: to have 1 per audience, as I have 10 audiences) duplicated Power BI files, each containing only the report view-pages relevant to a specific Audience. This approach introduces several significant challenges, including: Increased maintenance effort, as report changes must be replicated across multiple reports. Additional administrative overhead for maintenance, refresh, publishing and governance. Higher risk of version inconsistencies and reporting errors accross each duplicated version.   Please confirm if Page-Level Audience Visibility in Power BI Apps can be enabled?   ... View more

Power BI needs a way to move gateway connections between gateway servers without having to recreate on the new server each time. As a large enterprise running Power BI, we have many gateway clusters that are now being capped at the 1,000 connection limit, forcing our users to constantly shuffle connections around to other gateways. We need the ability to change the drop down for gateway cluster in the connection settings and relocate it easily without having users recreate the connection and delete the old one. ... 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

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

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

Feature Request: Include all data from scrollable visuals in PDF export Currently, Export to PDF in Power BI only captures the visible portion of tables and matrices. Scrollable data beyond what fits on the page is not included. Official documentation confirms this: “Visuals with scrollbars are exported in their default state… only as space allows on the page.” Export reports from Power BI to PDF  Request: Add an option “Include all data for scrollable visuals” to PDF export. Benefits: Export complete tables/matrices without creating paginated reports Save time and simplify report sharing This addresses a documented limitation and would improve native export functionality. ... 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

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

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

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

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 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

One of our customer is using standalone copilot and their requirement is when ever a user uses the standalone copilot it should be billed under certain workspace which customer can be able to select inorder to avoid confusion on the usage of standalone copilot getting billed to random workspace. ... View more

In the newer PostgreSQL versions, the "ssl_renegotiation_limit" setting has been removed. The PostgreSQL connector in Power BI is still referencing this setting, so an update is needed for the connector to support encryption with the latest PostgreSQL versions. ... 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

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

  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