Fabric Ideas

It would bereally helpful if we had an option to add notes or comments beside each individual visuals in Power BI. This notes could be dynamic based on filters/slicers and even included in reports. Right now, smart narratives or textboxes doesn't serve this purpose well, when we want to explain visuals seperately.A small notes sections per visual would improve make reports meaningful. For example: We might want to add a short explanation of the numbers or highlight a trend that users should notice-especially when sharing reports with clients or leadership who may not know the background. ... 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

The customer requires key pair authentication for Snowflake as their organization no longer allows the use of usernames and passwords. Since Power BI does not support key pair authentication, this feature is needed in upcoming updates. ... 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

One of the use case of Kusto functions is to abtract underlying table schema/data changes etc. But with the permissions at database level, there is no way to hide/restrict direct usage of tables. Users are able to view all entities (tables, functions etc) within database and able to explore and access. When we change table schema, it may break if they are directly accessing table. It would be good to have security role which restricts at entity level (e.g provide access to function but not tables).    Also in the ADX ideas  ... 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

With the debut of DAX Query View and TMDL Script View, there should be an API to retrieve these files.   This capability would enable organizations to automate testing and deployments by programmatically accessing DAX Queries and TMDL scripts.   For example, a Notebook could iterate over semantic models in a workspace, retrieve DAX Queries for testing, and execute those tests using semantic-link. If tests fail, teams could take corrective actions based on the results. ... View more

OPENROWSET function can read the files from Azure Data Lake storage or Azure Blob storage.  It would be useful to enable OPENROWSET to also read files form Fabric One Lake and access the files in Lakehouse /Files area. ... View more

I currently trigger my dataset refreshes using the Power BI REST API. However, to avoid overwhelming the system, I can't refresh all reports at the same time. This means I have to constantly poll the API to check the refresh status of each dataset before triggering more. This approach isn't efficient and puts unnecessary load on both the client and the Power BI service. It would be much better if we had the option to configure a webhook that notifies us when a dataset refresh is completed. That way, we could trigger subsequent refreshes or downstream processes only when needed—without continuous API calls. Please consider adding webhook support for dataset refresh completion events! ... View more

It’s challenging and time-consuming for both new and experienced report creators to organize data when trying to split cards into categories. By introducing small multiples, it could be a familiar and easy way for report creators to intuitively categorize data, especially if they had more control over layout and formatting. ... View more

The Date filter is not working with the March 2025 Update of Power BI. See attached images.     Works in January 2025 Update.   ... View more

It would be really useful to have security settings to show or hide individual report pages. Currently, audiences control access only at the report level, not per page. ... View more

Can this feature be applied to Excel files like Csv files?? ... View more

Problem: Currently, when a dataset is connected to a Lakehouse as a datasource in Power BI Fabric, it defaults to a cloud connection mapped to SSO. In embedded mode, reports built on these datasets fail due to a lack of identity, as they do not inherit authentication from the service principal. To resolve this, users must manually adjust the datasource settings via the Power BI service https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-fixed-identity   Proposed Solution: Introduce a new REST API or extend the current API functionality to allow programmatic setting (or re-setting) of the connection to the service principal, including updating datasources. Benefits: Automates the process, reducing manual intervention Minimizes downtime for embedded reports Enhances developer experience and deployment efficiency Ensures consistency in authentication settings across different environments Impact: This feature will significantly improve the workflow for organizations embedding Power BI reports using service principals, ensuring seamless and automated datasource authentication. ... View more

In our setup, we work with multiple environments (Dev, Test, and Prod), each represented by its own workspace. To streamline deployment via pipelines, we keep Lakehouses and Notebooks named identical across workspaces.   Previously, when opening a Notebook, we could clearly see which Lakehouse it was connected to, including the workspace name it belonged to.  This made it easy to identify if a Notebook was referencing, for example the Dev Lakehousem while working in the Prod workspace. We could then simply disconnect and re-add the correct reference.   However, with recent UI changes, only the Lakehouse name is visible, not the workspace it is contained in. This creates confusion when multiple Lakehouses share the same name across different workspaces. Even when adding a new source, the explorer does not clearly show which reference is from which workspace. This makes it far too easy to mistakenly remove or connect the wrong Lakehouse especially in production environments.   This seemingly small UI regression significantly affects productivity and introduces potential risks during deployment or debugging. Please consider restoring the visibility of workspace names to Lakehouse references in Notebooks.   Before: Screenshot from google E.g: Workspace Dev -LakehouseA -LakehouseB .... Workspace Prod -LakehouseA -LakehouseB ....   After:   Only lakehouse name   We use same lakehouse name in each workspace   ... View more

I wanted to share some feedback and a suggestion regarding the Purview glossary implementation, based on our experience at our organization. While we appreciate the capabilities that Purview offers for data governance, we've encountered significant challenges with setting up and maintaining the business glossary. Despite the ability to import terms rapidly, there is no automated way to link these terms to the items they represent. Each definition must be manually linked to a data item one at a time, across three screens with multiple user interactions per screen. Given that we have over 28,000 data items in our data warehouse alone, not to mention the additional measures and tables in our Power BI data sets, this manual approach is not feasible for us. The current process significantly hinders our ability to efficiently manage and utilize the business glossary. We believe that an automated feature to link Power BI descriptions to the Purview glossary would greatly enhance our ability to manage data governance and provide a more seamless experience for our users. If this feature is included in the new Purview integrated within Fabric, it would be a significant factor in hastening our move to an F64 capacity. We hope that Microsoft considers this suggestion, as it would be invaluable in addressing the challenges we face and improving the overall user experience. ... View more