Currently, Microsoft Fabric (and Power BI) does not provide a tenant setting to restrict workspace app creation to specific security groups.   The available controls are:   Workspace roles: Member role includes the ability to publish apps and manage permissions. Contributor role removes app publishing rights but also removes the ability to manage permissions on reports/models. Tenant settings: You can restrict workspace creation to specific security groups. You can control whether users can publish apps to the entire organization, but not who can create apps in general. There is no built-in setting today to allow Members to manage permissions but block app creation.   The only way to achieve this currently is: Use Contributor role for self-service workspaces (blocks app creation). Grant item-level permissions on reports/models to allow sharing without giving full Member rights.   Could I please ask for a tenant setting that would allow me to control who can create workspace apps, regardless of their workspace roles?   Thank you. ... View more

The current Test 2.5 validation requirement states that all items must have independent per-instance state. This requirement is valid for authoring workloads where each item represents a distinct user-created artifact. However, it does not account for a recognised class of workloads that Microsoft itself documents: operational monitoring tools. For monitoring workloads whose data source is the tenant itself, two items in the same tenant will always surface identical data by architectural necessity. This is the same pattern used by Microsoft's own Fabric Capacity Metrics app and Workspace Monitoring Eventhouse, both of which surface shared tenant-wide data regardless of how many instances or consumers access them. Applying Test 2.5 uniformly to monitoring workloads produces a requirement that is architecturally impossible to satisfy without misrepresenting the underlying data or fundamentally breaking the product's value proposition. Request: Review Test 2.5 applicability for workloads declared under the trackData itemJobTypes category or any workload whose architecture is tenant-scoped by design. Introduce a formal distinction in the validation framework between authoring workloads and monitoring/operational workloads. Where a workload demonstrates that shared state is architecturally intentional and documented in the attestation, allow the Not-Supported with attestation path as a valid resolution for Test 2.5 rather than a hard fail. Impact: This currently blocks certification for a valid and well-architected class of Fabric workloads that Microsoft explicitly encourages partners to build. ... View more

It would be great to have the option to use visual calculations in card visual reference labels ... View more

Ciao! I think it could be very nice to have the widget in the ipad for PowerBI, as you can do in powerpoint for example ... View more

Currently, in the Power BI Service → Workspace → Refresh history, we can see the following columns: Details Type Start (Date & Time) End (Date & Time) Status Message However, there is no column that shows how long the refresh actually took. Requested Enhancement Add a new column called “Refresh Duration” that automatically calculates the difference between Start and End date/time and displays the total refresh time (for example: 42 minutes 58 seconds or 00:42:58). Why this is useful Helps quickly identify long-running refreshes without manual calculation Makes it easier to compare performance between refreshes Useful for capacity monitoring, troubleshooting, and optimization Improves visibility for admins and report owners, especially when dealing with multiple datasets Current Challenge Right now, users must manually subtract the Start and End times or export the data elsewhere to calculate refresh duration, which is inefficient for routine monitoring. Expected Benefit This enhancement would improve usability and provide immediate insights into refresh performance directly within the Power BI Service UI. Thanks, Prasad Patil   ... View more

Body Microsoft Fabric Data Pipelines currently expose only a binary run result (Succeeded or Failed). This works well for execution errors, but becomes limiting when pipelines are used for logical checks or validations, such as: data existence checks rule or condition evaluation control or decision pipelines In many real scenarios: the pipeline completes without execution errors, however, the evaluated logical condition is false. Today, pipeline authors must either: use Fail for expected logical outcomes (making them appear as system failures), or always return Succeeded, losing semantic meaning. Proposal Allow a pipeline run to expose an optional structured logical result (for example, enum / string / JSON), independent of execution failure. This would clearly separate: execution failure logical or validation outcome and improve observability, orchestration design, and interface clarity. Design intent This proposal does not aim to weaken or redefine execution failure semantics. Fail should remain a clear signal for true execution errors or unrecoverable exceptions. The intention is to allow pipeline executions to expose logical evaluation results without overloading failure states that are currently reserved for system-level errors, thereby reducing false failure signals in monitoring views while preserving strict execution semantics. ... View more

It could, at least point to the offending query.   It is very hard to troubleshoot which of the query is causing powerbi to refuse automatic update ... View more

It would be nice to be able to Get Data from a dbase file. Especially when working with GIS (ArcGIS) files: Instead of seperately saving the shapefiles .dbf as an .xlsx then uploading it into Query Have the ability to upload and transform the .dbf within PBI Query Thank you  ... View more

The Theme gallery does not make it simple to import a svg or png icon file into the current theme. It can only be coded into a JSON then reimported which could be detrimental to a company theme being used accross many areas. ... View more

Hello team,   I would like to propose two related enhancements to the Fabric Link synchronization experience.   Background Fabric Link is a powerful capability that enables near-real-time data synchronization from F&O or Dataverse  into Microsoft Fabric. As someone who works with it regularly in client-facing scenarios, I have seen firsthand how much value it brings — and I believe two targeted enhancements would make it even more impactful in production deployments.   Enhancement 1 — Sync job execution timestamp Fabric Link currently shows a "last synchronization" date, which updates only when actual data changes are detected. This is useful to know when data was last modified, but it does not tell users whether the synchronization job itself ran recently. In practice, this creates ambiguity: if the last synchronization date has not changed, it is impossible to know whether the sync ran and found no changes, or whether the sync has not executed at all. For teams that need to validate that the integration is working correctly — regardless of whether there was new data — this distinction matters.   Proposal Add a dedicated column or field showing the last sync job execution time, independent of whether any data changes were detected. This would give users two complementary pieces of information: when the sync last ran, and when data last actually changed — making it much easier to distinguish between "no new data" and "something is not working."   Enhancement 2 — Flexible synchronization frequency The current synchronization interval of approximately 15 minutes works well as a default, but real-world scenarios demand more flexibility. Two distinct needs emerge in practice: Option A — Configurable interval within Fabric Link Allow users to set the sync frequency directly in Fabric Link configuration, supporting a range of intervals to accommodate both batch-oriented workflows (where a longer, more predictable cadence is preferred) and more frequent refresh requirements. Option B — Official Eventstream endpoint for high-frequency ingestion For scenarios requiring near-real-time data ingestion — below the 15-minute threshold — expose a supported and documented Eventstream endpoint as a first-class integration path. This would give teams a clear, official alternative for high-frequency needs without resorting to custom workarounds.   Both options address the same underlying need from different angles and could be delivered independently or together.   Expected benefits Operational clarity: teams can distinguish between a sync that ran with no changes and a sync that did not run at all Flexibility for all scenarios: batch and near-real-time clients both find a supported path within the Fabric ecosystem Reduced architectural complexity: fewer teams need to rely on undocumented workarounds for requirements that should be native Stronger integration positioning: Fabric Link or Fabric Link + Eventstream or Eventstream together cover the full ingestion frequency spectrum Closing These enhancements address real requirements that teams are already encountering in production deployments. All three improvements — the execution timestamp, the configurable interval, and the Eventstream endpoint — are independent and could be prioritised separately, allowing for incremental delivery without dependencies between them. I would be happy to share specific client scenarios or provide additional technical context if helpful.   Thank you for your continued innovation. ... View more

Hi Team, I’ve observed an issue with Implementation 2.0 during data import where Power Query does not load complete data after applying filters. After filtering a date column, Power Query loaded only 18 records instead of the expected 208. This results in incomplete data in the model. I have used Implementation 2.0 in multiple reports earlier and did not face this issue. As a workaround, switching from Implementation 2.0 to 1.0 loads the complete and correct dataset. Requesting the team to please investigate and fix this issue in Implementation 2.0, as it may lead to data inconsistency in reports. ... View more

Dear Fabric Community Team, I would like to provide some feedback regarding the handling of column totals in the Power BI Matrix visual, specifically for measures where aggregating across columns does not yield meaningful results—for example, Month-over-Month (MoM) calculations. Currently, the Matrix visual automatically sums values in the total row, which can be misleading for measures such as growth rates, percentages, or other calculations that are only relevant at the individual period level. This default behavior may result in confusion for users who expect the total to reflect a more meaningful aggregation, or in some cases, no aggregation at all. Suggestions for Improvement: Provide an option to customize or suppress totals for specific measures in the Matrix visual. Allow users to define alternative aggregation logic (e.g., display last value, average, or a custom label such as “N/A”) for totals and subtotals. Enhance documentation and in-product guidance to help users understand how totals are calculated for complex measures. Thank you for your continued efforts to improve Power BI and for considering this feedback. Enhancing the flexibility of Matrix totals will greatly benefit users who rely on advanced calculations and help ensure that reports communicate accurate and meaningful insights. Best regards, ... View more

Problem Users Are Facing: Currently in Power BI, Card visuals can display numbers, text, and images (via Image URL), but they cannot be clickable to open a webpage. This forces users to use extra visuals like Buttons or Tables to make links accessible, which: Clutters dashboards Makes the user experience less intuitive Increases development effort for dashboards with KPIs linked to external resources Proposed Solution: Enable Card visuals to accept a Web URL column, similar to Image URL. When clicked, the Card would open the webpage directly. Benefits / What It Will Help: Cleaner dashboards – no extra buttons or tables required Better user experience – users can click KPIs to drill into external reports, webpages, or documentation Faster dashboard creation – developers don’t need workarounds to make links accessible More interactive KPIs – users can combine metrics with actionable links in a single visual Example Scenario: A MovieLens dashboard shows the Selected Movie on a Card visual. Currently, to open the TMDB/IMDB page, a separate Button is required. With this change, the Card itself could be clicked to open the movie page, while still showing metrics like rating or number of reviews. Optional Enhancements: Tooltip showing webpage title or key details Support multiple link types (internal report, webpage, documentation) ... View more

If you like me started with working with notebooks in Fabric and have company policy that dictate using private links you will have discovered Microsoft “starter pools” are no longer an option. The startup time goes from below 10 seconds to  3-5 minutes. Microsoft have luckily decided to do something about this and have now introduced custom live pool in public preview. This is a great first step for customers – however it has one very limiting factor – it only work with workspace pools. These sessions will “only” be available on one given workspace and not across multiple workspaces. My proposal is to introduce custom live pools on capacity level. I want to be able to define environments on capacity level and share custom live pools on any workspace connected to this capacity. This will have the following benefits: Much easier for the admin to administrate custom live pools Cost effective – we would max want to pay for X custom live pools and spread them between all of the workspace for a given capacity – we cannot/“will not” set this up pr. workspace and have idle custom clusters across many workspaces. Link to current configuration on custom live pools on learn: Configure custom live pools in Microsoft Fabric - Microsoft Fabric | Microsoft Learn ... View more

We rely heavily on Dataflows for production pipelines. Currently, the Power BI mobile app does not show Dataflows or their refresh status. This creates a gap for operational monitoring, especially for users who need to quickly check refresh status on the go (e.g., from iPad or mobile devices). Request: Please add support in the mobile app to: View Dataflows within workspaces Check last refresh time and status (Success/Failed) View refresh history Optional: push notifications for failures Business impact: This will significantly improve monitoring and reduce dependency on desktop/browser access for critical daily checks. ... View more

Hello. Could you add an "Ends with" filter option, in the advanced options of the filter menu, just like in Excel : Hopefully this is understandable, I'm not sure of the names in english. Thank you. ... View more

For better visualizations, it would be helpful if there was an Auto option under the Specific Column series settings. This helpful for those who aren't savvy with calculation groups, format strings, or that can't change the model data that power bi is connected to. Currently, the only solution is to create your own custom visual and that is not a skill that every one can learn  ... View more

Today, Workspace Monitoring is configured separately per workspace, which introduces maintenance overhead and likely also a repeated baseline CU cost for each workspace.   Please make it possible to create Workspace Monitoring instances that cover multiple workspaces.   Users should be able to decide how many monitoring instances to configure and which workspaces each instance covers.   This would allow the baseline monitoring cost to be shared rather than incurred separately per workspace, reducing overall cost while also simplifying configuration and ongoing maintenance. In addition, it would enable a more centralized and flexible monitoring setup across workspaces. ... View more

In SAS PROC SQL, the OUTER UNION CORR operator allows vertically concatenating tables with different schemas by aligning columns by name and automatically creating missing columns filled with NULLs. In Microsoft Fabric (Warehouse / SQL analytics endpoint / Spark SQL), this functionality is missing. Users must manually normalize schemas by explicitly adding NULL AS column_name in each SELECT, which becomes error‑prone and hard to maintain when unioning many heterogeneous datasets. This feature is particularly important for: migrations from SAS to Fabric data lake / lakehouse ingestion patterns append‑only fact tables from heterogeneous sources Adding an operator or syntax variant such as:   SELECT * FROM A OUTER UNION BY NAME SELECT * FROM B   would significantly reduce friction and improve competitiveness with other analytics platforms. ... View more