Currently, when creating a deployment pipeline and defining a workspace as development, it is blocked from being used by other workspaces. I understand that it should be possible to have a dev workspace and for it to be available to other pipelines. In my current project, I only have one dev workspace and more than 20 production workspaces (this architecture was planned because, due to the volume of data, loads, and clients, it became necessary), and for every new feature in the dashboard or data engineering, I have to reconfigure the deployment pipelines (today I have one for each client in production due to the API parameters that each one has). ... View more

I am using a For Each loop in a pipeline that contains a Copy Data activity to move data tables sequentially. In the Run History the Copy Data activity is listed again and again. I believe that we should be able to supply the name of the object being copied in each line of the run history. ... View more

Often when I am writing queries I end up having multiple queries within the same script in Fabric Warehouses/ Lakehouse SQL endpoints. This results in this nice dropdown for navigating between each of those queries but as more queries are included in the script, it gets to be a lot. Currently I leave comments in my code like "Result 1: Query Subject" but that means I need to track down which query is which still and if I reorder the queries then I need to update the query numbers. What if there was a command or a wrapper that could be a flag to name these something set by the user (or dynamically) so that it would be easier to click through results?   ... View more

We really would like the MS Fabric team to include the possibility of adding cell conditions inside the notebooks so we can decide to run or skip a cell based on the value of a parameter. Vote please! Thanks! ... View more

Need Purview data source connector in Power BI desktop ... View more

Need Preview data source connector in Power BI desktop ... View more

Problem Description When using Microsoft Fabric Data Factory’s Copy Activity with an OData v4 source, any column defined as an enum type in the OData service is silently dropped during schema inference and data ingestion. This occurs because Fabric Copy Activity performs strict metadata‑based type validation and only materializes properties that map directly to supported primitive types. Since OData enums are logical types rather than primitive scalars, they are excluded from the inferred schema. This behavior results in incomplete datasets, unexpected data loss, and inconsistent ingestion outcomes—especially for systems that rely heavily on OData metadata and enum‑based domain modeling. Expected Behavior Power BI, which uses the same OData v4 metadata document for schema discovery, successfully handles enum types by gracefully coercing them into strings when no native type mapping exists. This demonstrates that a metadata‑driven fallback is technically feasible and consistent with Microsoft’s broader OData tooling ecosystem. The expected behavior for Fabric Copy Activity is to follow the same principle: If an OData enum type cannot be mapped to a native Fabric type, Automatically fall back to string, Instead of dropping the column entirely. Why This Matters Many enterprise OData services rely on enums to model business concepts such as status, category, priority, workflow state, and other domain‑specific classifications. Losing these fields during ingestion creates several issues: Data loss: Critical columns disappear without warning. Broken lineage: Downstream transformations and semantic models cannot rely on stable schemas. Inconsistent behavior: Power BI and Fabric interpret the same OData metadata differently, causing confusion for users who expect parity. Workarounds are impractical: Switching to Web API is not viable because it lacks metadata, type information, and relational structure required for OData‑based ingestion. Requested Enhancement Implement a fallback mechanism in Fabric Copy Activity so that: OData enum types are automatically materialized as string columns. Schema inference remains metadata‑driven and predictable. No columns are silently dropped due to unsupported logical types. Benefits to Microsoft Fabric Users Consistent behavior across Microsoft products (Power BI and Fabric). Improved reliability of OData ingestion pipelines. No unexpected schema loss, reducing operational risk. Better support for enterprise OData services, which frequently use enums. Reduced need for custom workarounds, manual schema overrides, or alternative APIs.   Thank you for reading 😉 ... View more

Currently, the Capacity metrics app only shows data from the last 14 days regarding Capacity Consumption. This amount of data is insufficient, and the Customer would prefer to view capacity consumption by month to better understand their monthly usage. To get 30 days of data, they must manually export the 14-day data, as there is no automation for this process. This makes it difficult for the Customer to review their Capacity consumption for an entire month. ... View more

Customer would like to know more details on how the Average utilization% is calculated in the Capacity Metrics app. As per the official documentation: Understand the metrics app compute page - Microsoft Fabric | Microsoft Learn, it is only mentioned that the Average Utilization% is the Average utilization percentage of the capacity. The utilization is calculated with respect to base capacity units of the capacity and does not consider autoscale capacity units. However, this doesnot mention any formula used to calculate Average Utilization. Customer is using this formula as per the above definition to calculate the Average utilization:  However, this doesnot match with the Average utilization% values displayed on the Capacity Metrics app. Hence, it would be great to display the formulas used to calculate the average utilization in the Metrics app or in the documentation for Customer reference. ... View more

Enable the Variable Library as a centralized location for storing all environment‑specific variables, allowing us to adjust them for promotion scenarios (e.g., from dev to prod) without relying on deployment pipelines.   It would be ideal if semantic model parameters or data sources could reference a Variable Library, similar to how deployment pipelines handle variables today. When using CI/CD Option 1 — Git‑based deployments — it isn’t possible to hardcode environment‑specific values or data sources, since these differ across environments. Example: If I build a report in a dev workspace/branch that uses a dev data source, and then promote it to a prod workspace/branch via PR, I have no way to automatically switch the data source to the production version. I would need to submit an additional PR just to update the prod branch, resulting in the same report with different hardcoded sources.  ... View more

When the user clicks on show as table on a visual in report, and the user does not want to see the total option. Can this be made as customisable? ... View more

Add an “Exact Match” option to the Find and Replace functionality in notebooks.   Currently, find and replace may match partial strings, which makes it painful to use when what you really want is an exact match. ... View more

Feature Request: Allow Users to Permanently Set the “Simplified” Layout as the Default Title: Add an option to permanently set the “Simplified” layout as the default view on the Power BI Home page Description: Currently, the Power BI Home page displays the new Copilot layout by default. While users can manually switch back to the “Simplified” layout via the selector at the top of the Home page, this preference is not saved permanently and must be reapplied frequently. Recommended apps are not immediately visible to new users. The official documentation only confirms the manual toggle but does not provide a way to persist this setting.  This creates friction for users who prefer the classic, cleaner layout for daily work. Requested Enhancement Introduce a persistent user setting that allows individuals to set the “Simplified” layout as their default Home page view. Optionally, add a tenant‑level or admin‑level setting for organizations that want to define a default layout for all users.  Benefits Improved usability and reduced manual steps A more consistent and predictable user experience Better alignment with user or organizational preferences Enhanced onboarding and orientation for non‑technical users  Background Recommended apps are not immediately visible to new users At the moment, no option exists to make the simplified layout the default. Microsoft documentation mentions only how to switch manually, with no support for saving the preference long‑term ... View more

Description Currently in Power BI, when a visual contains multiple columns or measures, filtering values within that visual often requires writing complex DAX expressions or creating additional measures and calculation logic. I would like to suggest a feature where users can filter values directly within a visual column, similar to the filter/drop-down functionality available in Excel tables, without relying on DAX. Proposed Feature Once a visual is prepared with multiple columns: Each column should have an Excel-like filter option Users should be able to: Include / exclude specific values Apply simple conditions (equals, greater than, less than, blank, non-blank) Filter at the visual level only, without affecting other visuals Example Scenario A table visual contains: Area Town village Activation Count Qualification Status Instead of writing DAX to: Remove blanks Exclude zero values Show only qualified Towns The user can simply apply filters directly on the relevant column inside the visual—just like Excel. Business Impact 🚀 Reduces dependency on complex DAX 🧠 Improves flexibility for business users ⏱ Saves development and maintenance time 📊 Makes Power BI behave more intuitively for Excel users 🔧 Enables faster ad-hoc analysis without model changes Current Limitation / Workaround Requires additional DAX measures Calculation groups or field parameters add complexity Not user-friendly for non-technical report consumers Expected Outcome Power BI visuals become more interactive and flexible, enabling self-service filtering while keeping the data model clean and simple. ... View more

We want to enforce a workspace consumption limit based on CU not percentage. We have several capacities shared by multiple teams. These capacities are scaled based on demand. With the current configuration options we need to update these settings based on scaling. e.g. We want to set the threshold to max F8 worth of capacity per workspace across three capacities (C1: F256, C2: F128, C3: F64). If we scale any of these capacities we need to adjust the percentages.  ... View more

I would like the ability to assign multiple legends in a scatter chart visual and select which legend label should be used as the data label from those multiple options. ... View more

From the Fabric Monitor, we need an option to either select ALL pipelines or select multiple pipelines at once, with the ability to perform bulk actions such as Cancel or Rerun. This feature would greatly improve operational efficiency, especially when managing large workloads or responding to failures across multiple pipelines. Thank you! ... View more

It would be very useful to make the Power BI Desktop role management window modal and resizable so that the names of the RLS, the roles, and the involved resources can be displayed correctly and fully.   https://community.fabric.microsoft.com/t5/Issues/The-Manage-Security-Roles-window-in-Power-BI-Desktop-should-be/idi-p/3174180       ... View more

We are currently unable to share an Office 365 Email Fabric Connection using a Service Principal. This capability is required for our implementation, and we would like to request support or enablement for this feature. Thank you! ... View more