Possibility for Power BI Apps to choose content across different Workspaces. ... View more

In SSMS, we have the option to add a vertical or horizontal tab group, to enable side-by-side viewing of 2 queries at once. This is great for comparisons, multi-tasking and trouble-shooting. Please add this option to the Fabric Warehouse SQL Query Editor view so we can see multiple queries on the same screen without having to constantly switch back and forth between tabs. ... View more

Description: Currently, Power BI treats the primary and secondary Y‑axes as fully independent scales. This often results in misaligned visuals where one measure extends beyond the visible range of the other, depending on which axis has the larger values. As a result, important data points can disappear from view unless users manually adjust axis ranges or build complex DAX measures to force alignment. I would like to propose a simple toggle option in the formatting pane: Secondary Y‑Axis → “Align with primary Y‑axis” (On/Off) What this toggle should do: Automatically synchronize the min/max scale of the secondary Y‑axis with the primary Y‑axis Ensure that the highest value—regardless of whether it comes from the primary or secondary measure—remains visible Remove the need for custom DAX measures that artificially scale values just to achieve alignment Reduce unnecessary model complexity and improve performance by avoiding additional calculated measures Provide a more intuitive and consistent visual experience for end users Why this matters: Many common scenarios (e.g., comparing MTD vs. MTD PY, actual vs. forecast, revenue vs. cost) require both lines to be visually aligned Excel already supports synchronized axes, so users expect similar functionality in Power BI Manual axis configuration is not dynamic and breaks when slicers or filters change A simple toggle would dramatically improve usability without compromising flexibility This feature would make dual‑axis visuals more reliable, easier to interpret, and significantly more user‑friendly. Thank you for considering this improvement — it would be a highly impactful addition to Power BI. ... View more

The Dynamics 365 Business Central connector in Power Query only supports authentication using a user account.   Please add support for Service Principal authentication using Azure AD App Registration with Client ID and Secret.   This would allow automated refresh processes and remove the dependency on personal user accounts.   Business Central APIs already support Service Principal authentication so enabling it in the Power BI connector would greatly improve enterprise scenarios and Microsoft Fabric integrations. ... View more

Power BI displays numbers correctly based on regional settings (e.g., comma as decimal separator), but copying values exposes the raw floating‑point value with a dot separator. Please add an option to copy the formatted (displayed) value so locale, rounding, and readability are preserved. ... View more

I currently use Clustered Column Chart to show data by a field called Inception Year.  I have to select and set the colors for each year by Formating Columns and applying Series settings for each year and selecting a color for each new year.  Why can we not have conditional colour formatting when we need to use a Legend for a chart? ... View more

Scenario summary The customer initially encountered a refresh failure with the following error: To resolve this, the customer modified the Power Query (M) code to make it more robust, primarily by improving error handling and attempting to remove or handle blank values. Original M code was working but failed on refresh due to the error above. Updated M code successfully handled the error and allowed the refresh to complete. Observed behavior After applying the updated M code, the existing relationship between the RLS (Row-Level Security) table and the MOA table was automatically removed without any warning or notification. As a result, the semantic model was left in a vulnerable state until the customer manually identified and fixed the broken relationship. During this period, RLS behavior was impacted.   Customer understanding The customer understands why this happened from a technical perspective: The M code changes affected the underlying data shape (rows / key values). This caused the relationship to be invalidated. However, the customer expressed concern that no warning was shown before or after applying the change, especially given the impact on RLS and model security.   Feedback / Feature consideration The customer would have expected some form of safeguard, such as: A warning when applying query changes that affect columns or keys used in relationships (especially RLS-related relationships), or A notification indicating that model relationships were removed or invalidated as a result of the change, or A rollback or review mechanism when model-impacting changes are detected. A warning or validation step when working with semantic models—particularly when changes affect relationships or RLS dependencies—could help prevent similar issues and reduce the risk of production-impacting scenarios. ... View more

Is there any way that Power BI Service provides a built‑in rule or setting to automatically stop a semantic model refresh, dataflow refresh, or paginated report execution after a custom duration such as 30 minutes. ... View more

Currently when there is an outage as per the tenant setting Service interruption notifications - Microsoft Fabric | Microsoft Learn customer will erceive notification for the following reliability scenarios: Open report reliability Model refresh reliability Query refresh reliability Notifications are sent when there's an extended delay in operations like opening reports, semantic model refresh, or query executions. After an incident is resolved, you receive a follow-up email.   As the current tenant setting is limited to reports and semantic models, we would like to have an option that enables customers to receive all outage-related notifications for both Microsoft Fabric and Power BI. ... View more

Problem Currently, Microsoft Fabric capacities run continuously once they are enabled. Many organizations only need Fabric workloads during business hours (for example, Monday–Friday, 9 AM–6 PM). If the capacity continues running outside these hours, it can lead to unnecessary compute costs. At the moment, administrators must rely on external automation tools such as: Azure Automation Power Automate to schedule capacity start and stop operations. While these solutions work, they require extra setup, permissions, maintenance, and monitoring. Proposed Solution Introduce a built-in scheduling feature inside Fabric Capacity Settings that allows a Tenant Admin or Capacity Admin to define when a Fabric capacity should automatically start or stop. Example scheduling options could include: Start capacity at 8:00 AM Stop capacity at 7:00 PM Capacity pause during weekends Custom schedules for holidays or non-working days This configuration could be added directly in: Fabric Admin Portal → Capacity Settings → Scheduling Benefits Cost Optimization Organizations only pay for capacity when it is actually needed. Simplified Administration No need to configure external automation scripts or workflows. Built-in Governance Centralized scheduling managed directly inside Fabric. Better Cloud Cost Control Especially useful for development, testing, and non-production capacities. Real-World Example A company runs its analytics workloads during business hours only. Instead of running Fabric capacity 24/7, the admin could configure: Start: 8:00 AM (Monday–Friday) Stop: 7:00 PM (Monday–Friday) Paused on weekends This could significantly reduce operational costs while maintaining performance during working hours. Why This Matters As adoption of Microsoft Fabric grows, organizations are increasingly focused on cost governance and efficiency. Providing native scheduling for Fabric capacity would be a highly valuable feature for many customers. 👍 If you find this idea useful, please vote so the Microsoft Fabric team can consider adding this feature. ... 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

The current card visual forces users to overlap elements or waste copious amounts of time creating custom visuals. The new card feature should give users the ability to create multiple cards in a single container and provide a greater level of customization. ... View more

It would be beneficial to incorporate features from Pivot tables that allow for the expansion and collapse of columns and hierarchical column groups within tabular visuals. This would not only solve the current limitations of matrices but also provide report creators with the flexibility to hide and show rows and columns, saving these settings for future use, thus eliminating the need to scroll through irrelevant data. ... View more

We need a feature for testing the access of audience members in apps akin to test as role on semantic models and power bi desktop. This would help a lot with checking if the access works properly on all the reports of the app.  ... View more

Enabling customized calculations at the query level for subtotals and grand totals would offer greater flexibility in reporting and preserve performance. Efficient organization of control settings to modify the style of these totals separately will empower report creators to achieve their desired appearance, while addressing their need for more control and customization in reporting. ... View more

Currently, the Capacity metrics app only shows data from the last 14 days regarding Capacity Consumption. This amount of data is insufficient, and the Customer would prefer to view capacity consumption by month to better understand their monthly usage. To get 30 days of data, they must manually export the 14-day data, as there is no automation for this process. This makes it difficult for the Customer to review their Capacity consumption for an entire month. ... View more

Imagine a world where report creators can automatically apply slicer and filter selections based on specific logic, revolutionizing data analysis and user experience. This innovative approach eliminates any need for complex workarounds, optimizes slicer functionality, and paves the way for more efficient and effective data reporting. ... View more

We really would like the MS Fabric team to include the possibility of adding cell conditions inside the notebooks so we can decide to run or skip a cell based on the value of a parameter. Vote please! Thanks! ... View more

Customer would like to know more details on how the Average utilization% is calculated in the Capacity Metrics app. As per the official documentation: Understand the metrics app compute page - Microsoft Fabric | Microsoft Learn, it is only mentioned that the Average Utilization% is the Average utilization percentage of the capacity. The utilization is calculated with respect to base capacity units of the capacity and does not consider autoscale capacity units. However, this doesnot mention any formula used to calculate Average Utilization. Customer is using this formula as per the above definition to calculate the Average utilization:  However, this doesnot match with the Average utilization% values displayed on the Capacity Metrics app. Hence, it would be great to display the formulas used to calculate the average utilization in the Metrics app or in the documentation for Customer reference. ... View more