Fabric Ideas

Currently, when sharing a report from a workspace in Power BI, the default option shown is: "People in your organization with the link can view and share." Even if I change this to "Specific people", enter the intended recipients, and apply the changes, the next time I click the Share button, it reverts back to the default "People in your organization" option. This can be misleading and may result in unintentionally broader access if the user forgets to reselect "Specific people."   Please consider enhancing the Share dialog to: Remember the last selected sharing option (e.g., "Specific people") for that report or user session. Or allow users to set a default sharing preference at the report or workspace level. Provide a clearer indication of the current sharing scope to avoid accidental oversharing. This would improve usability and help maintain tighter control over report access, especially in environments where data sensitivity is a concern.   Thanks for considering this improvement! ... View more

In the current Org Apps experience, filters reset when navigating away from the app, causing users to lose their context and requiring them to reapply filters each time they return. This disrupts workflow efficiency and user satisfaction. Proposed Solution: Introduce persistent filter states in Org Apps, similar to the behavior in the regular Org app. When a user sets filters (e.g., department, location, role), those selections should be retained across sessions and page navigations until explicitly cleared or changed by the user. ... View more

Please make it possible to run a notebook as the Workspace Identity, instead of running as a user identity.   This means the notebook (and the notebook's security context, i.e. the notebook's authentication to data connections) will not depend on any single user but use the Workspace Identity instead. ... View more

Currently, Power BI does not allow local calculated columns (created in the report layer) to be used as category axes in Small Multiples visuals. This limitation causes an error even when the same logic works perfectly in other visuals or when the column is part of the original dataset. The behavior is undocumented and leads to confusion for users working with composite models or temporary logic in local models. It would be highly beneficial if Power BI could support local calculated columns in Small Multiples, or at least document this limitation clearly. This enhancement would improve flexibility in report development and reduce the need for workarounds like disconnected tables or Power Query transformations. Suggested Improvement: Allow Small Multiples visuals to recognize and use local calculated columns as valid category axis fields. Alternatively, clearly document this limitation in the official Power BI documentation so users can plan accordingly. Thank you for considering this enhancement to improve the Power BI user experience. ... View more

Please make it possible to use variable library in Notebooks which are being run by a Service Principal. Currently it doesn't work.   Ref.: https://www.reddit.com/r/MicrosoftFabric/s/2CcC01o04E ... View more

This Learn page https://learn.microsoft.com/en-us/power-bi/connect-data/refresh-scheduled-refresh#schedule-refresh states "After two months of inactivity, scheduled refresh on your semantic model is paused. A semantic model is considered inactive when no user has visited any dashboard or report built on the semantic model. When scheduled refresh is paused, the semantic model owner is sent an email. The refresh schedule for the semantic model is then displayed as disabled. To resume scheduled refresh, revisit any dashboard or report built on the semantic model." The definition of inactivity on a report should not depend on manual/human interaction via the user interface, considering that Microsoft offers standard API's and even low/no code integration options from the Power Platform to retrieve & consume reports. As the subject says, API report interaction should álso prevent the scheduled refresh on semantic model to be paused due to inactivity.   The well-known workaround to add a subscription on each report to prevent the refresh to be disabled is not a suitable fix as it does not tackle the root of the problem - in other words, this message does not quite qualify as an "idea" since the current conditions to define inactivity are at least a gap, if not a bug.   That being said, please vote for the "idea" if you face the same problem 🙂 ... View more

Because of the Proxy authenication issue (currently Onelake explorer does NOT support proxy autheniciation via Kerberos/ NTLM), it is not possible to use Onelake within company network environment, in where the Proxy is used for accessing Internet.   And i believe many many Corp.s have this setup, So if this idea could be realized, it will be benefit lots of Fabric users.   ... View more

The current card visual forces users to overlap elements or waste copious amounts of time creating custom visuals. The new card feature should give users the ability to create multiple cards in a single container and provide a greater level of customization. ... View more

It would be beneficial to incorporate features from Pivot tables that allow for the expansion and collapse of columns and hierarchical column groups within tabular visuals. This would not only solve the current limitations of matrices but also provide report creators with the flexibility to hide and show rows and columns, saving these settings for future use, thus eliminating the need to scroll through irrelevant data. ... View more

Enabling customized calculations at the query level for subtotals and grand totals would offer greater flexibility in reporting and preserve performance. Efficient organization of control settings to modify the style of these totals separately will empower report creators to achieve their desired appearance, while addressing their need for more control and customization in reporting. ... View more

Imagine a world where report creators can automatically apply slicer and filter selections based on specific logic, revolutionizing data analysis and user experience. This innovative approach eliminates any need for complex workarounds, optimizes slicer functionality, and paves the way for more efficient and effective data reporting. ... View more

Instead of me having to go to external tools, add functionality that can examine columns and measures that are unused ... View more

Interpreting visuals without a clear legend to indicate logic behind specific styles can lead to confusion and decision-making errors. An idea to enhance clarity and transparency by ensuring legends and tooltips accurately display colors, patterns, and other visual components influenced by logics, would enable report consumers to easily understand the applied logic and make more effective decisions. ... View more

As Power BI Embedded becomes central to delivering analytics within custom applications, there's a growing need for Copilot support especially in App-Owns-Data scenarios where the app manages authentication and data access.   we need Copilot enabled in User/ App owns data scenarios.   Additionaly, we need a REST API for copoilot, A secure API to invoke Copilot features within embedded apps. so that we can use this Copilot API in embedded codes and App owns data scenarios. ... View more

Please add a workspace-level toggle that allows the workspace admin to make all items read-only in the Fabric user interface.   With this setting enabled, items (such as notebooks, semantic models, dataflows, etc.) cannot be edited, created, or deleted manually via the UI. Instead, all changes must go through:   Deployment Pipelines Git API Ideal implementation: A toggle in the workspace settings (e.g. “Make items read-only in UI”).   Only workspace admins can enable/disable this setting. ... View more

When trying to export the Matrix visual we are getting sub totals after exporting the data, even though the row/coulmn subtotal is disbaled in visual format. Also when we click on show as table from matrix visual we see subtotals, In the both scenario sub totals should not be visible. ... View more

Ensure that item names can be consistently retrieved in Microsoft Purview audit logs and related logs such as Power BI Activity, regardless of whether they pertain to Power BI items or Fabric items. Additionally, due to inconsistencies in which fields are populated depending on the item, please provide a clearer and more comprehensive explanation of the meaning of each field. For example, "ArtifactName" is not covered in the current documentation below, making it difficult to interpret the logs accurately:   https://learn.microsoft.com/en-us/purview/audit-log-activities https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/powerbiactivity ... View more

The primary axis are outdated and require significant improvement when compared to Excel. This makes it difficult for report creators and often leads to problems when trying to manage and style them effectively. By offering more format settings, greater control over displayed data can be provided, especially if axis ticks, new gridlines, and separators are also included. ... View more

Table tooltips are currently a bit messy. They work great for providing visibility into supporting data, calculations, etc. that don't fit in the table columns, but it's annoying for the user to always have a popup when they're hovering anywhere over the table, which they must be when scrolling. Additionally, sometimes only certain rows have supporting information (such as notes), so that it doesn't make sense to show the tooltip for all rows.   This idea doesn't solve all of these problems, but it does at least address a common scenario with the overlap of them.   Conditional formatting icons are great for informing the users that "something is different about this row." This prompts them to hover to view the tooltip. Making the icon have a click action that displays the tooltip would be intuitive for the user, avoids the problem of showing tooltips for rows that have no additional information, and keeps the user from getting frustrated at the pop-up. ... View more