Similar to the Monitor page, where we can see what has run and what is currently running, it would be useful to see what's scheduled to run in the future. This to check that all schedules are set up as expected.   Reason: Easy and conveniently verify that all schedules are configured as expected. ... View more

GitHub commits from Fabric Workspaces are unsigned, which causes an error for repos with signed commits enforced. Please add support for signed commits. Thank you.   ... View more

Currently, the Explore setting in Power BI (preview) can only be enabled or disabled at the tenant level, meaning it applies to the entire organization. Customers are requesting the ability to enable this feature for specific groups or subsets of users rather than globally. This would allow organizations to test and adopt the feature gradually without impacting all users, providing better governance and controlled rollout during the preview stage. ... View more

Please change the priority of BCDR workloads to run at a lower priority so they do not contribute to overloading a Fabric Capacity. If you have high capacity usage from normal workloads, its unacceptable for BCDR acitivities to continue using so many CUs that your Capacity begins throttling. ... View more

By design, Power BI disables scheduled refresh for a semantic model in the following cases: After four consecutive failures or when the service detects an unrecoverable error that requires a configuration update. After two months of inactivity, scheduled refresh for the semantic model is automatically disabled. Power BI also sends notifications to the semantic model owner and recipients. However, there is currently no way to view all semantic models with disabled scheduled refresh in a single list. Admins or users must open the settings of each semantic model individually or check notification emails one by one, which is time-consuming when managing a large number of models. Although it is possible to retrieve this list using the Power BI Rest API, this method requires specific API knowledge and PowerShell scripting skills. The most user-friendly approach would be to make this information easily accessible in the Power BI Service interface. For example, semantic models with disabled refresh could be highlighted in a specific color.     ... View more

To address the limitations of our current slicers, which are less advanced and potentially confusing compared to our competitors, a new and enhanced list and dropdown slicer should be designed with a wider range of customization options, incorporating industry best practices, and include innovative features like the ability to copy and paste lists. ... View more

The Refresh Attempts feature automatically pushes 3 consecutive refreshes on a dataset if it fails a single time, in hopes that it will succeed. This is helpful, but incredibly wasteful when considering the cost of each refresh due to cloud infrastructure costs.   This feature has quadrupled our cost of refresh failures, because typically when a refresh fails, it is for a valid reason, so the subsequent refreshes fail. This is especially problematic when cloud issues cause refreshes to fail for our entire tenant, effectively causing us to reach our cloud infrastructure cost quotas.   I propose that the refresh attempts feature should be able to be toggled on or off by Tenant, Workspace, or Dataset. ... View more

Currently, Microsoft Fabric lacks native dark mode support. Adding a built-in Dark Mode/Theme that allows UI components to seamlessly adapt to dark backgrounds and colors would enhance accessibility, reduce eye strain, and align with modern UI trends. ... View more

Power BI should consider adding the Trend Line (linear regression trendline) feature to a small multiples line chart.  Currently it is available for line charts but not when using small multiples. An option to generate simple linear regression trendlines- straight lines that show the overall direction of data points would improve clarity and analytical accuracy, especially for business analysts and decision-makers who rely on visual cues to interpret performance metrics. ... 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

Description: Currently, only the connection owner can delete a Cloud Connection in Fabric / Power BI. Even tenant admins or Fabric capacity admins do not have permission to remove, reassign, or take ownership of connections they didn’t create. This limitation causes several operational and governance challenges: When a user leaves the organization, their personal cloud connections become orphaned and cannot be deleted. Admins cannot clean up unused or stale connections, leading to clutter and confusion. Governance policies cannot be fully enforced, as there’s no way to centrally manage ownership or lifecycle of connections. It increases dependency on individual users rather than service principals or admin accounts. Proposed Enhancement: Enable Fabric Admins / Power BI Tenant Admins to: View all cloud connections across the tenant, regardless of ownership. Delete or transfer ownership of connections to another user, group, or service principal. (Optional) Bulk manage connections via Admin APIs or the Fabric Admin Portal, including audit and export capabilities. These capabilities should align with existing admin rights for datasets, workspaces, and gateways, ensuring consistent governance control. Benefits: Prevent orphaned or stale connections. Simplify tenant clean-up and governance. Enhance compliance and lifecycle management. Reduce dependency on individual user accounts. Align Cloud Connections with the existing Power BI admin model (datasets, gateways, capacities). Category: Admin & Governance / Data Connectivity ... View more

New Desktop app update installed an almost white user interface. There is zero contrast which is not good for the eyes. I see where some people have requested a light interface so incorporate an option to select either light or dark theme like in the Office apps. ... View more

It would be very useful to have a centralized view for managing page properties, particularly filters. Instead of opening each page individually to configure or modify filters, users could manage all page filters and related settings in one place. This would save time, ensure consistency, and make report maintenance much more efficient. ... View more

Matrix visuals could significantly enhance the user experience by emulating Excel's intuitive sorting, searching, and filtering capabilities, even for hierarchical columns. This idea would the current limitation in Power BI's matrix visuals, which lack a comparable experience to Excel's established standard for data manipulation. ... View more

Smart Narrative provides dynamic summaries of data, which would greatly enhance contextual storytelling in tooltips. Currently, it’s not supported in tooltip pages. Enabling this would allow users to deliver richer insights on hover-over interactions.   #SmartNarrativeTooltip ... View more

Secondary axes are automatically managed by the system in some cases, making it problematic for report creators with no control over intervals, ticks, and other crucial components, limiting effectiveness of various types of analysis. It would be great if the secondary axis included comprehensive format settings so that greater control over displayed data is provided. ... View more

Re: API Call for Workspace Contacts in Workspace S... - Microsoft Fabric Community   Retrieve workspace contacts from workspace settings via REST API Call   I need to Track Capacity backed workspace contacts across the organization in a Workspace catalog So that i can ensure each workspace is properly administered and managed       ... View more

Would be helpful if we could use bookmarks to adjust column header widths in a visual. Currently, that information does not seem to be captured, even when using "Personalize Visuals" with the "Auto-size width" option turned off. ... View more

Experimenting with Copy Job. Yeah, OK, but not great. Some suggestions: 1) Make the option for OVERWRITE available for Warehouse destinations. Currently available for Lakehouses only. This article (What is Copy job in Data Factory - Microsoft Fabric | Microsoft Learn) does not differentiate that option. Honestly, how hard it is to program in a DROP TABLE IF EXISTS statement in the back end code? Warehouses support such actions.   2) Give the user the abiltiy to DISABLE a table in the list. If I have a list of 50 tables in my job, but during development only want to refresh 2 of them, I have to run the whole job. Waste of time and resources. ... View more