In the user defined reports, When users select multiple fields for their report, the order in which they select these fields determines the order in which they appear in the visual. However, if they later realize that the order is incorrect or not as intended, there is no easy way to reorder the selected fields. The only option that I know is to unselect all fields and reselect them again in the desired order, which becomes a tedious task, especially when working with a large number of fields. Is there any way forward to overcome this in PowerBI user defined reports ? ... View more

We have some groups that want to be assigned database admin to run some management scripts. However, we do not want these groups to be able to access senstivie data(in table and in .show queries). With RLS on tables, we could control the access to table. However, .show queries will return all data to admins which is not what we want. We want Kusto team to support RLS over .show queires so that we could better contribute to the security and compliance of data access even with admin roles. ... View more

Please someone help me out about this community ... View more

Hi, we have our own IKEA Business Department at the IKEA Burbank location. Can it be possible to add IKEA Business as a new department for their deparment to have a physical HCS? It would be a great idea. Currently IKEA Business HCS falls under services but only if the business customers gets delivery but we would like for IKEA Business to have their own HCS. Thank you  ... View more

Dear Microsoft Power BI Team, I would like to propose several enhancements to the PowerBI.com monitoring page to improve visibility, monitoring, and operational efficiency for semantic model refreshes and deployments. Current Challenges: Limited Visibility: The latest status of all semantic model refreshes and deployments is not easily discernible. The current page only shows a history of succeeded and failed refreshes, which makes it difficult to quickly understand the overall health of an instance. Restrictive Permissions: Viewing semantic model refresh statuses currently requires a high-level Contributor role. This restricts DEV/QA teams from monitoring refresh health in non-production environments unless they are granted permissions that may be unnecessarily broad. Proposed Solutions: Comprehensive Monitoring Dashboard: Introduce a new Monitoring view that lists all semantic models in a workspace or tenant, with filters for environment or model name. For each model, display: The latest refresh status (success or failure) A quick visual summary (e.g., green/red dots) representing the status of the last 4–5 refreshes to help identify systemic issues The latest deployment status Role-Based Access Improvements & New Role: Allow users with lower, read-only (R/O) roles to view this Monitoring dashboard. This enables DEV and QA teams to monitor refresh health without requiring Contributor permissions. Introduce a new role: Semantic Model Refresh Orchestrator. This role would have a single permission: the ability to trigger semantic model refreshes. This empowers DEV/QA teams to rerun failed refreshes in lower environments and allows Production Support to rerun refreshes in production, without needing full Contributor or Admin rights. Action buttons (e.g., "Rerun Semantic Model Refresh") should be available only to users with Contributor or Semantic Model Refresh Orchestrator permissions. Improved Issue Detection: The dashboard should visually summarize recent refreshes (e.g., green/red dots for last 4–5 refreshes), making it easier to spot recurring or systemic problems with specific semantic models. Alert Subscriptions for Lower Roles: Enable users with access to the Monitoring dashboard (including R/O and Orchestrator roles) to set up email alerts for failed semantic model refreshes, configurable per model via checkboxes. This allows teams to proactively monitor and respond to issues. Benefits: Improved Operational Efficiency: Teams can quickly assess the health of all semantic models and respond to issues without unnecessary permission elevation. Better Issue Detection: Visual history of recent refreshes makes it easier to spot recurring problems. Granular Access Control: The new role and dashboard sharing options align permissions with actual job responsibilities, reducing risk. Proactive Monitoring: More users can subscribe to alerts, ensuring faster response to failures. Thank you for considering these suggestions to make Power BI’s monitoring more robust and accessible for all teams involved in the data lifecycle. Best regards, ... View more

After public publish, beeing able to download data and a picture of object would be great (Y) ... View more

Can we get a fix for the Bug where when using 2 bookmarks in the same report page, they both simultaniously work without the bug/glitch?    Current Behavior: The report page contains two bookmark navigators: Online/Offline toggle (primary selection) Sales/Visits toggle (secondary selection) Expected Behavior: When selecting "Offline" in the primary navigator, the "Sales" view should automatically display as the default visual (as configured in the bookmarks). The secondary navigator ("Sales/Visits") should reset to show "Sales" as selected   Issue Identified: If a user: Selects "Offline" (shows Sales view correctly) Then switches to "Visits" view Changes to "Online" Returns to "Offline" The visual correctly displays "Sales" (as per default bookmark settings) However, the "Sales/Visits" navigator incorrectly shows "Visits" as selected (retaining the previous selection state)   Visual Reference: The screenshot highlights this discrepancy in pink - the displayed visual (Sales) doesn't match the bookmark navigator's selected state (Visits).     ... View more

Having the option for justifying text like in word would be great (Y) ... View more

By applying a fully consumption-based pricing model to the OneLake API, access to OneLake will be possible even when the Fabric capacity is paused. ... View more

Hi Fabric Team,   I’m writing to report a critical issue we've encountered while using Microsoft Fabric for our ETL and ELT workloads. We rely heavily on both Warehouse and Lakehouse components. As expected, when configuring a copy activity, we can use SQL queries if the source is a Warehouse. However, we discovered that Fabric currently does not prevent queries from referencing Lakehouse tables in a Warehouse-scoped query. This unexpected behavior led to a serious issue in one of our production pipelines—records from a daily load were not copied to Oracle as expected. After an in-depth investigation, we traced the problem to a query that mistakenly referenced a Lakehouse table, even though the copy activity source was configured as a Warehouse. Fabric did not flag this mismatch, and the copy activity silently failed to extract the intended data. This kind of inconsistency is very hard to detect and can have severe consequences in production environments. 🛠️ Suggested Improvement: Implement a validation step during query submission in copy activities to ensure that all referenced tables belong to the selected source type (i.e., Warehouse). This would prevent these subtle but impactful issues. Thank you for your attention to this matter.   Kind regards, Yazdan Aghajanian Data Engineer ... View more

There is title (or subtitle) padding on shapes or buttons, only Text padding. If the title (or subtitle) is left or right aligned, it's too close to the border/edge and there is no way to control that! ... View more

Super simple request - would like to see the ability for a table visual in PowerBI to be able to have the background color modified to make it easier when a row is selected. Often users select a particular row to drive interrelated visuals and then they lose track of the row they selected as the backbround color of grey (blah) is easy to scroll by.   ... View more

enable the possiblity to reposition the formula-bar in Power BI and Power Apps so the formula bar can be positioned to the left/right or bottom of the screen or even better as a floating pop up window 🙂   Especially the formatting the "code" the script get more vertical and takes up space and prevent data model /reports developers to see the impact on screen unless having to collapse the formulabar, and then expand again if adjustment is needed.   ... View more

Power BI currently supports Python visuals in Desktop only, and visuals freeze in the Service due to sandboxing limitations. This blocks real-time advanced visualizations (e.g., forecasting, clustering, statistical modeling) that data professionals increasingly rely on. Allowing this addtional capacity [which could be premium], would allow for more dynamic usage of python generated visuals and more powerful data transformations. ... View more

Whilst a user with pipeline access can see the individual operation history within a pipeline, in order to centrally oversee the movement of artifacts between workspaces in ALL deployment pipelines a user needs to use the REST admin API to extract all Pipelines, PipelineOperations and PipelineOperationDetails records and create a process whereby it joins them together to show an estate-wide record of movements.   It would be easier if the Monitor tab on the Power BI homepage included Pipeline Operations (that the user has permission to access) so that all monitoring can be enabled centrally instead of costly, time-consuming and complicated API exports.   e.g. "On X date user Y deployed artifacts to environment Z. Click to see the artifacts moved and the description added" ... View more

I am currently working with Microsoft Fabric and exploring the capabilities of its REST API to track pipeline execution at a more granular level. Specifically, I would like to retrieve activity-level log data during the runtime of a pipeline to track the progress, status, errors, and other relevant information for each activity within the pipeline. ... View more

Hey Community  , Does Not allowing to change the update method to "replace" from "append" in data flow gen2 , if the df gen2 is craeted from within warehouse has some purpose back picture , or it is limitation which can be updated from microsoft end in near future. I reguest Microsoft team ,  to work on this issue. ... View more

Hi Team, We would like to suggest generating the SLA report based on specific Work Order numbers instead of Task Codes. This would make it easier for us to track and process the work orders accordingly. In addition to that, could you please add two new columns with the headers Root Cause and Mitigation to the report? We appreciate your support in enhancing our operational effectiveness. Thank you! ... View more