It would be nice to have the ability to move items from one workspace to another (at least the ability to move to "My Workspace") if you have the same privilages in Power BI Service. Right now, It only allows to "save a copy" and that is only for Reports. You cannot move semantic models to another workpsace.  ... View more

When using the Dataflow Query Execution REST API Query Execution - Execute Query - REST API (Dataflow) | Microsoft Learn queries are terminated after ~90 seconds.   This fixed timeout significantly limits real‑world usage. Only very small or simplified queries can be executed, while more complex or parameterized queries (although valid and supported in normal Dataflow refreshes) are cancelled. This limitation makes it difficult to: Build generic or reusable Dataflow solutions Execute dynamic or complex queries via automation Use the API consistently compared to pipelines Suggested improvements: Increase the default timeout Make the timeout configurable   Many users aim to build generic, reusable, and automated Dataflow solutions in Fabric. The current timeout makes this difficult and forces unnecessary workarounds, such as: Over‑splitting queries Avoiding the API altogether Falling back to less flexible execution methods Improving this would unlock significantly more value from the Dataflow Query Execution API. ... View more

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

Current behavior Today, Microsoft Fabric controls item creation through a single tenant or capacity‑level setting: “Users can create Fabric items.” This setting works on an all‑or‑nothing basis: When enabled, users can create all Fabric item types in a workspace. When disabled, users cannot create any Fabric items. There is currently no supported way to selectively allow or block specific Fabric item types (for example, allowing users to create only reports but not Lakehouses, Warehouses, Pipelines, etc.). Problem / customer impact Many organizations have strong governance and separation‑of‑duties requirements. Common scenarios include: Allowing report developers to create only Power BI reports Allowing data engineers to create data engineering objects only Preventing accidental creation of high‑impact objects (e.g., Warehouses, Lakehouses, Pipelines) Because item creation is all‑or‑nothing, admins are forced to: Over‑restrict users (Viewer role), or Over‑expose capabilities that users should not have This creates friction, governance risk, and additional administrative overhead through workarounds such as multiple workspaces per persona. Requested enhancement Provide granular creation controls that allow admins to: Enable or disable specific Fabric item types per tenant, capacity, or security group Align Fabric permissions more closely with real‑world organizational roles Improve governance without limiting adoption or usability Benefits Stronger security and governance Better role separation without workspace sprawl Reduced risk of unintentional resource creation Improved admin and customer experience ... 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

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

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

The current input slicer when enabled to accept multiple values - text is displayed as count - instead allow it to show atleast three words or adjust accordingly to show count once the text is overflowing the search box. This is a UX issue and does not show clearly what is being search in the text box. after the user types the search text - in this case two words - the input slicer by default stars to show count of words searched - this is not very user friendly.  instead allow it to show expanded values by default.. and only collapse when the text is over flowing, the feature is already there just need small refinement in the input slicer.   ... View more

Problem Statement: In complex reports, bookmarks control visibility states across many visuals. However, Power BI Desktop does not provide a way to see which visuals are affected by a specific bookmark. Gap: Although bookmarks and visuals can be grouped, there is no bookmark-to-visual dependency view. Authors cannot easily identify which visuals are shown/hidden by a bookmark. Suggested Feature: Add a dependency/impact view for bookmarks: Select bookmark → list all affected visuals Include: Visual name Page Visibility state (shown/hidden) Optional: highlight affected visuals directly on the canvas Business Impact: Reduces errors when modifying bookmarks Improves maintainability of complex, bookmark-driven reports Speeds up development and debugging Summary: Provide native visibility into which visuals a bookmark controls to enable safe and scalable report design.   @yokof @v-pranithab @Miguel_Myers Since you're all quite active in the Forum, I'd like to know your opinion to this, if possible 🙂 ... View more

Hello, I'd like to suggest an enhancement to Power BI subscription emails: the ability to attach query results as .csv or .xlsx files, driven by predefined DAX queries tied to each subscription. The proposed feature would allow subscription creators to define one or more DAX queries per subscription, with the query results attached to each scheduled email as a .csv or .xlsx file — alongside or instead of the existing visual snapshot.  To be clear, I am not suggesting a complex UI where users configure date ranges, select columns, or build queries through a visual interface. The implementation could be as simple as providing a field where a DAX query can be entered and tied to a specific subscription. An even more elegant approach would be to allow users to reference an existing DAX query view — the query definition would already be maintained and validated within the semantic model, and the subscription would simply point to it. I am raising this from practical experience. As a data analyst at a distribution company operating across the DACH region, I currently produce these exact reports manually — I refresh the data via live connections, attach them and send them by email to recipients on a regular schedule. Almost all of these recipients already have access to and actively use Power BI reports, but for them it remains essential to receive data in tabular form for further analysis. This is a real and recurring workflow that a DAX-driven subscription attachment would automate entirely. I also regularly receive scheduled Looker emails from several of our customers containing sellout and stock data as structured file attachments. This is standard Looker functionality — users can schedule delivery of query results as CSV, XLSX, or JSON directly to email recipients. It is a capability I value highly, and one I find conspicuously absent when working in Power BI. I believe Power BI is the stronger platform overall, and this is one of the few areas where it falls short of a direct competitor. Closing this gap could do more than satisfy existing users — it could serve as a compelling reason for organisations currently using Looker or similar tools to migrate to Power BI. And given that new customers adopting Power BI today are increasingly likely to onboard directly onto Microsoft Fabric, this feature could also contribute meaningfully to Fabric adoption. The building blocks are already in place — DAX queries power Analyze in Excel, XMLA endpoints, and now DAX query views. Extending them to subscription emails would be a natural, high-impact addition. Thank you for considering this. ... 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

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

It would be helpful if the slicer could pass-through NO data when nothing is selected so that downstream visuals don't return errors or consume resources trying to ingest all the data. Currently the slicer treats the "all selected" and the "none selected" states as identical, returning the full data. This is needed and desirable in many situations. The slicer could have an option where the behavior of the "none selected" state could be set to "same as all selected" or could be set to "no data selected". This would allow the report designer to match the behavior to the need. For example, if the full data breaks the limits of a downstream graph, leaving the slicer unselected would leave the graph empty instead of displaying an error. Then, once at least one selection is made in the slicer, the selected data would be passed as normal. There are some situations where this can be accomplished with measures, but they are clunky and not always possible. ... 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

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

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

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

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