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

We request the addition of Service Principal authentication support for the SharePoint Folder connector in Power BI, including the ability to scope access to specific folders within a SharePoint site for the refresh scenarios. This enhancement would enable app‑only, non‑delegated authentication for SharePoint document libraries, supporting unattended refreshes and eliminating dependency on user‑based OAuth tokens.   Business Impact: Without Service Principal support, SharePoint Folder refreshes depend on user credentials, creating security, governance, and reliability challenges. App‑only authentication would improve refresh stability, security isolation, and enterprise automation, particularly in environments with strict identity lifecycle and compliance requirements. ... View more

Please add the ability to assign titles or labels to notebook cells in Microsoft Fabric.     When notebooks grow large, it becomes difficult to quickly understand what each cell does without adding many markdown cells. A simple cell title feature (displayed near the cell number) would make notebooks much easier to read and navigate.   Example titles Load Source Data Data Cleaning Feature Engineering Model Training Benefits Better notebook readability Easier navigation in large notebooks Improved collaboration across teams Fewer extra markdown cells This small feature would significantly improve the usability of Fabric notebooks for data engineering and data science workflows. ... 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

Use case: We have one particular capacity where we want to allow only ad hoc refreshes, but not schedules. We can audit that with semantic models but not with dataflows.  Request to expose the dataflow refresh type in the Capacity Metric App. ... View more

While creating a SQL Server connection using Service Principal, we have two options. One is to provide the client secret directly and the other is to reference the secret from Azure Key Vault. Both connections get created successfully, but in the current UI both appear exactly the same. Because of this, it is not possible to easily identify which connection is using the direct secret and which one is using the Azure Key Vault reference. In environments where multiple connections are created, this makes it difficult for administrators and developers to manage and verify whether Key Vault is being used for credential management. It would be helpful if the UI could show a clear difference for connections created using Azure Key Vault. For example, showing the credential source, displaying the Key Vault reference, or adding a small indicator in the connection details. This would improve visibility and make connection management easier. ... 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

When a user opens a report and selects the File dropdown, they see the “Embed report” option with the following choices: SharePoint Website/Portal Developer Playground So the Customer wants to Disable “Embed report” for View-only users in power bi ... View more

When using pipelines/notebooks, we can successfully export tables with uppercase names. However, when converting CSV files to tables in Lakehouse today, the names are forced into lowercase. This causes data inconsistency for the enterprise, which requires uppercase naming. The documentation states that both uppercase and lowercase naming are supported; please add a case-sensitive mode for the "Load to Table" feature. ... 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

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

I wish this to be an option to copy the output if a cell by click on "Copy Output" from the cell's output menu as shown below        ... 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

Enterprise customers adopting Microsoft Fabric want to standardize on OneLake as the unified storage layer for both structured data (Lakehouse tables, Warehouse data) and unstructured data (files stored in OneLake). This data may originate from external systems (ADLS, S3, databases, SaaS) or be created natively within Fabric workloads. A growing number of regulated customers have Infosec and compliance requirements to enforce retention policies consistently across all data in OneLake, regardless of source or workload. Today, customers are explicitly asking for a OneLake‑scoped retention capability that they can reason about as a storage‑level control, similar in intent to ADLS lifecycle policies.   A native, Purview‑governed OneLake retention model would materially reduce this adoption barrier and strengthen the OneLake governance story. ... View more

In enterprise environments using Dev / Prod workspaces the current 1,000 item limit per workspace becomes restrictive.   A single domain workspace for ETL activities can easily contain: Lakehouse, Pipelines, Notebooks, Dataflows   Over time, the 1,000 item limit per workspace becomes restrictive and forces teams to: Split domains across multiple ETL workspaces Introduce unnecessary workspace fragmentation Increase permission and governance complexity Add operational overhead The limit works well for small-to-medium environments, but it becomes a constraint at enterprise scale.   Suggestion: Increase the limit or Make it configurable based on capacity (F64/F128) or tenant settings This would reduce workspace fragmentation and better support enterprise-scale Fabric adoption. ... 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

Enable the Variable Library as a centralized location for storing all environment‑specific variables, allowing us to adjust them for promotion scenarios (e.g., from dev to prod) without relying on deployment pipelines.   It would be ideal if semantic model parameters or data sources could reference a Variable Library, similar to how deployment pipelines handle variables today. When using CI/CD Option 1 — Git‑based deployments — it isn’t possible to hardcode environment‑specific values or data sources, since these differ across environments. Example: If I build a report in a dev workspace/branch that uses a dev data source, and then promote it to a prod workspace/branch via PR, I have no way to automatically switch the data source to the production version. I would need to submit an additional PR just to update the prod branch, resulting in the same report with different hardcoded sources.  ... View more