In need to programmatically retrieve the status of all gateways in a cluster, not just the primary. Specifically, require status per gateway, detection of states like 'Partially offline', and alerting when any gateway becomes unavailable. Currently, APIs seem to return only the primary gateway status, with no visibility into secondary nodes and also alerting options, such as triggering alerts if a threshold of refresh failures is exceeded, for example, 20% failures within the last hour to ensure high availability and monitoring. ... View more

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

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

Need option for tenant‑wide UI view in Power BI Service that shows all subscriptions across the entire organization.   ... 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

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

When visiting the monitor page, not all refresh events appear. Monitor page does not show all semantic model refresh failures. The failed refresh events shows in refresh history of semantic models. Even the details are available in onelake catalog when searched for the semantic model -> monitor -> we could see the failures events but in monitor hub the details are not available. The Engineering team confirmed it by design but however the monitor hub should provide all the details so that it provides a centralized view of job execution health, progress, and outcomes to quickly identify problems and take action. ... View more

Description Currently, SQL Server mirroring in Microsoft Fabric does not support User-Defined Data Types (UDTs). This limitation blocks ingestion and mirroring scenarios for databases that rely on UDTs, even when those UDTs are simple aliases of fully supported native SQL Server data types. Business Impact We are working with a third-party vendor database where: The schema is not under our control UDTs are used extensively throughout the model These UDTs are aliases of standard SQL Server data types (e.g., VARCHAR, INT, etc.) Because of this limitation, we are unable to leverage Fabric mirroring for this data source without introducing complex and potentially fragile workarounds (e.g., schema replication, type conversion layers, or ETL pipelines). Rationale Under the hood, SQL Server alias UDTs map directly to base system types. From a data movement and storage perspective, these should be fully compatible with existing Fabric mirroring capabilities. Blocking on UDTs: Creates unnecessary friction for onboarding common enterprise systems Prevents adoption in scenarios involving vendor-managed schemas Requested Enhancement Enable support for User-Defined Data Types (UDTs) in SQL Server mirroring by: Automatically resolving alias UDTs to their underlying base data types during ingestion/mirroring or Providing a configuration option to map UDTs to their base types Expected Outcome Seamless mirroring of SQL Server databases that use alias UDTs Elimination of unnecessary preprocessing or schema transformation steps Broader adoption of Fabric mirroring in enterprise environments with vendor-controlled schemas Additional Notes This request specifically targets alias UDTs, not complex CLR-based types. ... View more

Instead of deployment rules let us just define the connection parameters in PQuery and then let those be controlled by Variable Library, eliminating the need for creating the same deployment rules for same data sources for all the semantic models uploaded for the first time.  ... View more

Currently the personal bookmarks reference to text names of the columns in the reports hence when we make a change in the field name the personal bookmarks break. With the addition of PBIP format column names should be able to reference IDs hence we would be able to change the column name but keeping the column ID the same (this is only a suggested mechanism that comes to mind). This would provide flexibility for the development process and adaptibility to the business terminology changes in the future. ... View more

Pipeline schedules should not have an end date by default.   The current 1-year default end date introduces a hidden failure mode where pipelines silently stop running.   Most pipelines are intended to run indefinitely, so this default creates unnecessary operational risk and maintenance overhead.   Removing the default end date would make scheduling more reliable and predictable, while avoiding unexpected disruptions. ... View more

In Microsoft Fabric / Power BI, when multiple reports are connected to the same semantic model, Git integration does not preserve or allow control over the default report associated with that semantic model after syncing to a new workspace. This results in unexpected behavior when downloading, modifying, and republishing semantic models—especially after pulling artifacts into a new workspace using Git integration.   Scenario / Reproduction Steps A report is created in Power BI Desktop and published to the Power BI Service. This creates Report 02 test and Semantic Model 02 test. Later, another report is created directly in the Power BI Service using the same semantic model. This creates Report 01 test, also linked to the same semantic model. Both Report 01 test and Report 02 test are linked to the same semantic model in the original workspace, and everything works as expected. Git integration is enabled for the workspace, and all artifacts are pushed to a Git repository. The same artifacts are then pulled into a new workspace using Git integration. Observed Behavior (Issue) In the new workspace, the semantic model automatically selects Report 01 test as the default report. The selection appears to be based on alphabetical order, not on the original or intended default report. When the semantic model is downloaded as a PBIX, modified, and republished: The changes are reflected in Report 01 test instead of the 02 test Report. This issue does not occur in the original workspace and happens only after Git pull into a new workspace. Impact Creates confusion for Fabric admins and developers managing multiple reports per semantic model. Causes unexpected report updates, leading to potential data integrity and governance concerns. Makes Git‑based CI/CD workflows unreliable when: Multiple reports share a single semantic model Default report selection matters for downstream operations. Git integration should provide a way to explicitly define or preserve the default report associated with a semantic model, instead of automatically selecting one based on alphabetical order.   Feature Request Add an option in Git integration / Fabric workspace settings to: Explicitly select or configure the default report for a semantic model or Preserve the original default report association when syncing across workspaces. ... 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

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

The new calendar-based time intel is really good, but the fact that date-related columns (the ones that are not mapped to any calendar category, but still marked as date related using TMDL) are not removed when using DATEADD and SAMEPERIODLASTYEAR means that you need to write REMOVEFILTERS for doing time intel and that does not feel right at all.  Changing current behavior might be tricky but there could be a calendar level setting or yet another column category to make this happen. If I want a column to say as filter I will not mark it as date-related and that's it. If I mark it as date-related is because I don't want to deal with it when doing time inte. Please change that or give us a way around it. Writing REMOVEFILTERS on columns of the date table is very inconvenient and feels like a step back from legacy time intel.  ... View more

We would like to have a Date selection slicer which allows the report viewer to decide which type of slicer to use: relative/between/etc. Nowadays I have both users who like 'relative' slicer and users who like 'between' slicer. Because of that I have to waste space on my reports by including both types of slicers, only because there is no option for end user to manually change it: Instead I would like the end user to decide, some sugestions how it could look like:         ... View more

Distinct counts are the bane of our existence in big data.  Distinct counts over DirectQuery/DirectLake are not fast or efficient enough, and are very expensive from a compute and cost standpoint.  We need a re-aggregable approximate distinct count in Import Mode using HyperLogLog (HLL).  The idea would be to enable the creation/ingestion of a HLL sketch at the same dimensional grain as other user-defined aggregations so that the sketches can be dynamically merged/aggregated to produce an approximate distinct count.     Consider the following example where we need a distinct count of orders across channels and product groups.  Today, we would need to cache 4 unique intersections of data (1. Overall, 2. By Channel, 3. By Product Group, 4. By Channel & Product Group).  Not only is this compute intensive, but it forces us to create really terrible DAX to detect the user's reporting context and return the correct count.  In addition, it still doesn't allow for correct counts when users arbitrarily include/exclude members of a desired grouping (i.e. all product groups except "PRODUCT GROUP 02").  In an ideal world for this example, we would compute an HLL sketch at the Channel and Product Group level (image below), and either have a new DAX function like "HLLMERGE( <sketch> )" or enhance the APPROXIMATEDISTINCTCOUNT function to accept a column of sketchs, and this would dynamically merge the sketches in context to return the correct approximate distinct count. This would be a huge unlock to be able to dynamically reaggregate approximate distinct counts, as they are very difficult to manage today, and Power BI is well-positioned to do this.  It would be a powerhouse feature for big data users. ... View more

Input Slicer   Currently, users are able to choose from a list of filter operators in the dropdown.   It would be helpful to be able to restrict which filter operators are available in the drop down for end-users to choose from.   Case 1: Limit to a single filter operator - e.g. Is Any Case 2: Limit the filter operator to 2 operators - e.g. Is Any, Contains Any etc... ... View more

Currently, Power BI subscriptions can only be managed at an individual report or user level. There is no centralized option for administrators to disable subscriptions at a capacity level or for specific workspaces.  Need a feature to turn off subscriptions for an entire capacity or selected workspaces would greatly improve governance, performance control, and operational efficiency. ... View more