We have been observing that Power BI semantic models are automatically triggering a refresh immediately after being republished to the Power BI Service. In the refresh history, this is tagged as "On-demand", even though no manual action was performed. Upon reaching out to Microsoft, we received the following confirmation: “This is the expected behavior from the Power BI Service once a semantic model is republished. The behavior is by design and applies to all semantic models in Import mode (or those using auto-aggregations). This behavior has been consistent for several years, and there are currently no plans to change it in the product roadmap.”   While this behavior can be beneficial in certain scenarios—particularly for smaller models that complete refreshes within seconds—it introduces challenges in the following cases: Incremental Refresh Models:  In some situations, the refresh may process more data than expected, leading to longer execution times. Large or Complex Models: Models with sizes exceeding 5–10 GB or with high complexity may require several minutes to refresh, increasing resource consumption.   This behavior can significantly impact capacity resources, especially in Fabric capacity-enabled workspaces, where such unintended refresh activity may lead to unnecessary resource utilization and potential performance issues.   It would be highly beneficial if this behavior could be controlled at the user level or at least at the tenant level, allowing organizations to prevent unintended refreshes and better manage capacity consumption. ... 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

  Description / Problem Our organization has fully enforced phishing‑resistant authentication methods for all employees and administrative accounts, in line with Microsoft security best practices. These include passkeys and FIDO2 hardware security keys (for example, YubiKey). However, we currently need to maintain Power BI on‑premises data gateway (February 2026 version) as an exception to these policies. The reason is that the embedded web authentication engine used by the gateway does not support FIDO2 authentication. Because of this limitation, we are unable to enforce phishing‑resistant authentication methods for gateway sign‑in and administration. Current Behavior The Power BI on‑premises data gateway currently supports: Password‑based authentication, or Passwordless authentication using number matching While number matching improves security, it does not meet the definition of phishing‑resistant authentication required by many enterprise security and compliance standards. Impact Forces organizations to maintain authentication exceptions Creates a security gap in otherwise fully phishing‑resistant environments Prevents full alignment with Zero Trust and passwordless‑first strategies Affects enterprises with strict regulatory, compliance, or security mandates Requested Enhancement Please add FIDO2 authentication support (passkeys and hardware security keys) to the Power BI on‑premises data gateway in a future update. This would allow organizations to: Fully enforce phishing‑resistant authentication across all Fabric and Power BI components Eliminate password‑based authentication for gateway administration Align the gateway with Microsoft’s broader identity and security roadmap ... 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

Power BI and Microsoft Fabric currently do not offer a tenant‑level or portal‑wide banner capability that allows administrators to proactively notify all users when data is stale, delayed, or impacted by upstream system failures. In real‑world enterprise environments, pipelines, dataflows, and semantic models frequently depend on external source systems. When these sources are unavailable or delayed, reports may continue to load successfully but display outdated data, creating a silent failure scenario. Users have no visible indication that the information they are viewing may not be reliable. Today, administrators lack a centralized, in‑product mechanism to communicate these conditions to all users at the moment they access Power BI / Fabric. ... View more

Currently, the “Apply to entire organization” option is not enabled in Copilot Capacity Settings. As a result, to restrict Copilot CU usage to a specific capacity, administrators are required to create and maintain a group that includes all users in the organization. From an admin and UX perspective, this introduces unnecessary overhead and ongoing maintenance. Enabling the “Apply to entire organization” option would significantly simplify configuration, reduce operational effort, and improve the overall administrator experience. I’ve already discussed this topic with the PM responsible for Power BI Copilot, and I understand the design considerations behind the current approach. That said, I would like to encourage the team to reconsider the factors leading to this restriction, as the current setup adds complexity without clear value for administrators. Allowing Copilot to be applied to the entire organization at the capacity level would be: Easier to configure Easier to govern Less error‑prone More intuitive for Fabric administrators I hope other Fabric admins find this improvement valuable and can vote to support this idea. Thank you for considering this feedback. ... View more

Live embedded reports maintain state in PowerPoint. When changes are made to the report (such as adding new slicers), the embedded session may not fully isolate page-level visuals, causing slicers to appear unexpectedly.  ... View more

The data preview in the Results section of a SQL query (in either a warehouse or lakehouse) is very difficult to read as it is currently set up. It would be massively improved by implementing the following: Show the total row count at the bottom of the Results rather than just showing the row preview limit (10,000) if the actual row count goes beyond this Ideally, this would show something like Columns: 4  Rows: 56012  Rows Displayed: 10000 Allow columns in the Results to be dragged wider so it's possible to read the full column names and data As far as I can see, there's currently no way to do this in Fabric ... View more

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

When exporting data from Power BI using “Summarized data (.xlsx with live connection)”, the resulting Excel file does not inherit the sensitivity label applied to the dataset or report, even when the tenant setting “Automatically apply sensitivity labels to downstream content” is enabled. This behavior creates a potential data leakage risk, as file‑level protection controls are not enforced on the exported Excel file.   Expected Behavior: Automatically apply the dataset/report sensitivity label to Excel files created using Summarized data (.xlsx with live connection) OR Clearly document and surface warnings in the export UI indicating that this export option does not support sensitivity label inheritance ... View more

Product Microsoft Fabric Area Data Warehouse / SQL Type Bug / UX issue Description In Microsoft Fabric Warehouse, queries using CTEs behave inconsistently between execution and UI-based view creation. A SELECT statement with CTE runs successfully, and the following also works when executed manually:   ``` CREATE OR ALTER VIEW schema.view_name AS WITH ... SELECT ... ``` However, using the “Save as view” button on the same query fails with the error: > Incorrect syntax near the keyword 'WITH'. This error is misleading. The SQL syntax is valid, and the view can be created successfully when CREATE OR ALTER VIEW is executed explicitly. The failure appears to be caused by how the UI wraps the query internally. Impact Valid SQL is rejected only via the UI Users are led to believe CTE is unsupported in Warehouse views Results in unnecessary investigation and loss of trust in the authoring experience Expected behavior “Save as view” should preserve valid CREATE VIEW semantics, or Clearly communicate any limitations instead of returning a misleading syntax error   ... View more

Fabric notebooks run inside a managed execution environment that includes built‑in libraries, system packages, runtime versions, and environment bindings. Today, there is no external API that exposes these built‑in resources for a given notebook. While the existing Fabric REST APIs support CRUD operations and job scheduling, they do not provide visibility into the runtime resources that a notebook depends on. This creates gaps in automation, governance, reproducibility, and environment transparency. This feature request proposes a Notebook Resources API that allows programmatic access to the full resource profile of a notebook. In more simpler words, this picture tells you exactly what items the api should retrieve.   ... View more

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

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

The primary axis are outdated and require significant improvement when compared to Excel. This makes it difficult for report creators and often leads to problems when trying to manage and style them effectively. By offering more format settings, greater control over displayed data can be provided, especially if axis ticks, new gridlines, and separators are also included. ... 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

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

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