Ability to click a value in a table that filters a different chart on the same page, drill into one of the columns on the chart that has been filtered by previous selection, then click back button, I would like the ability for the previous selection to remain selected such that my chart is still filtered.  ... View more

When I want to format multiple/all the columns in a table based off a condition in one of the columns, I have to add the conditional format to each column in my table individually. I think it'd be really cool if there was a feature where I can either copy/paste the conditional formatting to selected columns or if there was a way to format all the columns at once. ... View more

We have encountered a bug regarding the scheduled refresh behavior for Materialized Lake Views (MLVs). When a custom refresh schedule is configured for a specific subset of MLVs, and one or more of those MLVs is subsequently deleted, the entire scheduled refresh job fails. It appears that deleting an MLV does not automatically remove it from the underlying scheduler. Furthermore, when these specific scheduled runs fail due to the deleted MLV, the run history and failed results do not load in the UI, making it difficult to access the logs. Steps to Reproduce: Create multiple Materialized Lake Views (MLVs) in Microsoft Fabric. Navigate to the schedule settings and configure a separate refresh schedule for a subset of these MLVs (do not select all). Delete one or more of the MLVs that are actively included in that refresh schedule. Allow the next scheduled refresh to trigger. Observe that the refresh job fails. Attempt to view the failed run results/details in the refresh history. Expected Behavior: When an MLV is deleted, it should be gracefully removed or deregistered from any active refresh schedules. The scheduled refresh should successfully execute for the remaining existing MLVs on the schedule. The refresh history and execution logs should always load in the UI, even if a run fails. Actual Behavior: The scheduled refresh fails completely because the system attempts to refresh an MLV that no longer exists. The UI fails to load the run details/results for these specific failed executions, preventing us from viewing the underlying error logs. ... View more

Add an AI-enabled visual builder that can generate Deneb visuals directly from natural-language intent plus existing semantic model objects. Users should be able to specify starting measures, ending measures, variance measures, grouping dimensions, and ordering rules. Power BI should then generate the required visual spec without forcing users to create disconnected tables or consolidated presentation-only measures. ... View more

Don't think this is currently available: Have default visual format settings:  eg: corner radius 6, border blue, font X, font colour Y etc etc so that everytime you add a visual, it has the same characteristics. We can create a template, but you still have to copy paste from one pbix to another or copy an exising visual and change it. It would be nice to have a place to set defaults so that all new visuals are created the same. ... View more

Ref this youtube-video: (350) How to Turn SQL Database changes into Real-Time Intelligence with Fabric Eventstreams | Data … I want to use Fabric SQL Server as a (CDC) source to Fabric Eventstream in the same manner as using Azure SQL Server (CDC) is outlined in the youtube-video. We have service principal based connection to our Fabric SQL Server and it would be a killer use case to be able to use this as source (CDC) in the setup of the Eventstream.   ... View more

Currently, notifications are triggered only when the overall capacity utilization exceeds the specified limit. However, we would like to have notifications configured based on specific scenarios such as interactive throttling, request rejections, and background rejections when they reach a defined threshold.   In addition, we require certain modifications to the surge protection settings.     Currently, it is not explicitly mentioned that the policy is implemented based on a 24-hour smoothed window, as described in the documentation. https://learn.microsoft.com/en-us/fabric/enterprise/surge-protection#set-the-background-operation-rejection-and-recovery-thresholds  ... View more

Make it possible to add a description to folders in workspaces.   This would be useful for humans and AI in knowing which content goes into which folder.   Suggested change: In addition to folder name (already possible), make it possible to add a folder description.   The description should be visible when opening the folder, or there could be a small icon we can hover over to see the folder description.   The description should also be a part of Git so that AI can use this information when developing the project. ... View more

The banner is always shown (by design) and reappears on every reload, impacting UI/UX in embedded apps and portals. Need a setting to hide or remove the sensitivity label banner in embedded Power BI reports. Related Idea: Option to hide the information protection banner (sensitivity label) ... View more

Currently you can only filter the last 100 items when using filters which in a large environment makes the monitoring hub nearly useless as you cannot actually find some runs even from the past 24 hours when you have enough objects and the filtering is unreliable, sometimes load more returns 2 objects, sometimes 0 with the same exact conditions. This is a basic capability on other platforms, it should work in Fabric too already. ... View more

Curerntly there is no aggregate to give me first/last value in a group. The solution is to use a CTE/derived table with row_number That then prevents use of scalar function inlining and adds complexity when all I want to do is. We have ANY but I'd like to be able to get FIRST and LAST without resorting to CTEs/Derived tables.  select somekey, FIRST(SomeColumn) over (order by <some othere column) from myTable group by somekey Probably needs an IGNORE_NULLS option ... View more

Hi Microsoft Team, Customers would like to suggest a feature to allow users to restore deleted artifacts in Power BI / Fabric (like reports, dashboards, datasets, etc.). Currently, if something is deleted by mistake, it is hard to recover and may require recreating it again. It would be helpful to have a Recycle Bin or restore option, where deleted items can be recovered within a certain time. This will help prevent data loss and save time for users. ... View more

When we add two different columns to a single axis, such as X or Y, in a visual, we see drill up and drill down options. Is it possible to remove these options after applying this setup? ... View more

Currently, dbt docs are generated as a static site (dbt docs generate) and must be hosted or accessed locally, which is not ideal in a Fabric environment. Idea: Allow dbt jobs in Fabric to automatically generate and display dbt docs directly within the workspace. Value: No need for local hosting (dbt docs serve) Centralized documentation for all users Built-in lineage and metadata exploration Better alignment with Fabric’s unified experience This would simplify documentation access and improve data discovery across teams. ... View more

Idea Description: Currently, when formatting Table and Matrix visuals in Power BI, users must apply certain formatting settings (such as text alignment, font size, font color, and other column-level properties) individually for each column. For example, if a report developer wants to center-align all column headers and values, they must manually configure each column one by one. This becomes time-consuming and inefficient, especially for tables containing a large number of columns. I would like to propose a **"Select All"** option within the formatting pane that allows users to apply formatting settings across all columns simultaneously. Similar functionality already exists in many Microsoft products and would significantly improve the report development experience. Advantages: Reduces repetitive manual effort. Improves developer productivity. Ensures consistent formatting across all columns. Simplifies maintenance when new formatting standards need to be applied. Enhances usability for reports with many columns. Suggested Options: Add a **"Select All Columns"** option in the field formatting section of Table and Matrix visuals. When selected, any formatting changes (alignment, font settings, colors, text wrapping, etc.) would be applied to all columns at once, while still allowing individual column overrides when needed. This enhancement would save considerable development time and improve the overall user experience for Power BI report authors.   If this helps, ✓ Mark as Kudos & Submit Vote | Help Others ... View more

Lorsqu'un usager s'abonne à recevoir des avis de la plateform Power BI, la programmation d'émission de courriel devrait valider la préférence de langagues avant de publier un courriel.    Ainsi vous éviteriez de vous exposer à des plaintes qui seraient faites à des organismes de protection de la langue comme au Québec ou il y a des lois qui régissent des situations.   Merci ... View more

In our current architecture, we have several workspaces with specific workloads. One of the workloads is central management of functions, variables, an orchestration database, etc.    When we run notebooks, we import them using %run "NB WhateverTheNameIs". This works excellent, as long as the notebook is in the same workspace. Things change when the notebook is in a different workspace. Using the notebookutils.notebook.run library seemed like a great idea, until I found out that this only works for returning values, not when I need to import functions.   So, here's the idea, upgrade %run to %run ("NB WhateverTheNameIS", "Workspace ID"). This works similar to what the notebookutils library does, only more fitting to my, and probably other people's as well, use cases. ... View more

At the moment when editing a pipeline the default activities shown in the ribbon are a mix of Icon + text (e.g. Icon "Copy data") and just the icon where a tool tip shows just the activity name (e.g. Teams Icon only) . Removing the duplication of icon plus text and just having the icons with the tool tips would allow far more icons to be shown in the ribbon and be quicker to access.  i.e. work the same way as other Office applications. Also can the ribbon be customizable so we can set our most used activities in the ribbon. ... View more

The Problem Scenario Currently, Microsoft Fabric evaluates capacity utilization based strictly on a 24-hour moving average for background operations and a 5-minute window for interactive operations. While this smoothing mechanism manages minor daily spikes, it completely ignores long-term underutilization history. Consider this realistic enterprise scenario: An organization purchases a premium F64 capacity. For 29 days of the month, the capacity runs at a quiet 3% to 5% utilization. The customer is consistently paying for premium hardware performance that sits completely idle, yielding massive resource margins back to the cloud infrastructure. On day 30, the team needs to execute a massive, critical end-of-month data processing job or a full historical reload. The workload causes an instant utilization spike of 10,000%. Even when smoothed over a 24-hour window, this massive burst triggers aggressive throttling, freezing new requests and grinding business operations to a halt. Fabric's architecture treats this customer exactly the same as a user who has been redlining their capacity to the absolute limit for the past week. The system has zero memory of the 29 days of idle capacity that the customer fully paid for. Why the Current Model Feels Broken for Businesses From a budgetary and finance perspective, cloud capacities are viewed as an allocated pool of paid resources. When an enterprise pays for continuous premium capacity but faces severe performance penalties the moment they actually need to harness that power, it creates a "use-it-or-lose-it" paradox. It penalizes customers for having irregular or batch-heavy data lifecycles despite their significant financial commitment. Proposed Solutions / Feature Requests I request that Microsoft introduce a more flexible, financially empathetic mechanism to handle historical underutilization for dedicated F-Capacities: Historical "Capacity Banking" (Rollover CUs): Allow capacities that consistently run below a specific threshold (e.g., under 15% utilization for more than 7 consecutive days) to accumulate a "Burst Credit Buffer." If a sudden massive job is triggered, let the system draw down from this historical bank to offset the 24-hour smoothing debt before triggering harsh throttling. Idle-Time Autoscale Credits: Instead of requiring customers to pay additional out-of-pocket costs for Azure Autoscaling during a critical spike, allow historical idle time to act as a credit pool to fund temporary, automatic scale-ups (e.g., automatically bumping from F64 to F128 using accumulated credits). Configurable Smoothing Windows for Premium Tiers: Give Fabric Administrators the option to extend the background job smoothing window from 24 hours to 7 days for higher capacity tiers, allowing large monthly or bi-weekly batch loads to naturally dilute over a wider historical window. ... View more