Current Situation (Problem) In Power BI, users currently have to choose between two separate slicer types: a dropdown slicer for selecting individual values, and a range/slider slicer for selecting intervals such as dates or numeric ranges. If both options are needed, report designers must add two separate slicers, which increases report complexity and reduces usability. Proposed Solution (Feature) Introduce a single slicer that can be dynamically switched by the end user between two modes: dropdown mode for selecting individual values, and range/slider mode for selecting intervals. The end user should be able to toggle the mode directly within the slicer without requiring multiple visuals or edit mode. Business Value This feature will simplify report design by reducing the number of visuals required, improve user experience through greater flexibility, and save time by reducing the number of interactions needed to filter data. Example Use Cases Date: A user selects a single day using dropdown mode, then switches to a date range using slider mode. Numbers: A user selects a specific value or switches to a range to analyze intervals—all within the same slicer. ... View more

Currently, Power BI Report Server only supports creating linked reports for paginated (.rdl) reports. There is no equivalent option available for Power BI (.pbix) reports, and it is unclear why this limitation exists. Introducing linked report functionality for PBIX reports would provide significant benefits. For example, it would allow teams to manage access more effectively through folder-level permissions, without needing to compromise security or duplicate reports across multiple locations. At present, the only workaround is to publish the same report multiple times, which creates additional overhead and increases the risk of version inconsistencies. Supporting linked reports for PBIX files would help ensure a single source of truth while still enabling flexible access for different teams. ... View more

Problem Statement Currently, Microsoft Fabric’s Zero-Copy Cloning functionality is limited in scope, making it difficult to implement robust CI/CD and "environment-switching" workflows for dbt projects. Specifically, we cannot perform a cross-warehouse clone for tables and views when the source and target warehouses reside in different Fabric Warehouses, even when they are within the same Capacity and Workspace. Use Case I am utilizing dbt to manage data transformations in Microsoft Fabric. To follow best practices, I need to maintain distinct environments (e.g., DEV, STAGING, and PROD) represented by separate Warehouses. In a dbt workflow, the dbt clone command is critical for: Environment Parity: Creating lightweight, ephemeral copies of production data for testing changes without duplicating storage costs or incurring massive data movement overhead. Safe CI/CD: Validating dbt models against a snapshot of current data before merging into production. Requested Feature Please extend the CREATE TABLE AS CLONE OF / CREATE VIEW AS capabilities to support cross-warehouse cloning within the same Workspace and Capacity. This would allow dbt to seamlessly manage environments by cloning objects from a PROD warehouse into a DEV or STAGING warehouse instantaneously, without physically copying the underlying data. Expected Business Impact Cost Efficiency: Eliminates the need to physically copy large datasets across environments, drastically reducing storage and compute costs. Development Velocity: Allows data engineers to create production-mirror environments in seconds rather than minutes or hours, leading to faster iteration cycles. Adoption of Data Ops: Removes a significant barrier for dbt users migrating to Fabric, making Fabric a first-class citizen in the modern Data Ops ecosystem. ... View more

Category Microsoft Fabric – Administration / Governance / CI-CD Business Need Many enterprise customers use Service Principals (SPNs) for CI/CD deployment automation in Microsoft Fabric. As part of security compliance, organizations periodically rotate, replace, or decommission Service Principals. Currently, Fabric items such as Data Pipelines, Notebooks, Lakehouses, Warehouses, Environments, and other artifacts retain ownership metadata associated with the identity that originally created them. There is no unified mechanism to transfer ownership of existing Fabric items from one Service Principal to another Service Principal. This creates operational challenges when an existing Service Principal must be retired. Current Challenges Existing Fabric artifacts remain owned by the old SPN even after redeployment using a new SPN. Customers are often required to recreate or redeploy artifacts to establish new ownership. Large production environments may contain hundreds or thousands of Fabric artifacts, making recreation impractical. Decommissioning old Service Principals becomes risky due to ownership dependencies. This increases governance, operational, and compliance overhead for enterprise customers. Requested Enhancement Provide a supported mechanism to transfer ownership of Fabric items from: Service Principal → Service Principal User → Service Principal Service Principal → Workspace Identity Service Principal → Managed Identity The capability should be available through: Fabric Portal (GUI) REST APIs PowerShell/Automation Bulk ownership migration across a workspace Suggested Features Workspace-level ownership reassignment wizard. Bulk transfer of ownership for all artifacts within a workspace. Validation report showing impacted artifacts before transfer. Audit logs tracking ownership changes. Support for rollback. Support for CI/CD automation scenarios. Expected Benefits Simplifies Service Principal rotation and credential lifecycle management. Improves enterprise governance and security compliance. Reduces downtime and migration effort. Eliminates the need to recreate production artifacts. Enables scalable DevOps and CI/CD practices in Microsoft Fabric. Example Scenario An organization migrates from an existing Service Principal to a new Service Principal for CI/CD deployments. While deployments succeed using the new identity, ownership of existing Fabric items remains linked to the old Service Principal. When the old Service Principal is decommissioned, customers face operational and support challenges. A direct ownership transfer capability would resolve this problem without requiring artifact recreation. Impact High This affects enterprise customers operating production Microsoft Fabric environments with automated DevOps, security-driven Service Principal rotation policies, and large-scale deployments. #Fabric #ServicePrincipal #CI/CD #Governance #OwnershipTransfer #Administration #WorkspaceManagement #DevOps #Security #Enterprise ... View more

Currently, resuming or pausing a Microsoft Fabric capacity requires navigating to the Azure portal. It would be extremely valuable to have these capabilities directly within the Microsoft Fabric portal: Resume Capacity from Fabric Allow authorized users to start (resume) a paused Fabric capacity directly from the Fabric UI. Eliminate the need to access the Azure portal. Simplify self-service and improve the user experience. Intelligent Auto-Pause Provide a configurable option to automatically pause the capacity when it is no longer being used. Possible settings could include: Pause after 30 minutes, 1 hour, or a custom period of inactivity Prevent pausing while jobs are still running. Benefits Significant cost savings, especially for non-production environments (DEV, TEST, QA). Reduced dependency on Azure. ... View more

Schemas can be created using the set quoted identier switch. SET QUOTED_IDENTIFIER ON This allows for distinct Schema names to be created within a warehouse, including ones with the same name. CREATE SCHEMA [TEST]  CREATE SCHEMA "[TEST]" However CICD for the warehouse stores these the same as  TEST.sql -> CREATE SCHEMA TEST  [TEST].sql -> CREATE SCHEMA [TEST]  Without the qutoed identifiers moving this warehouse into another workspace "environment" will fail  with error : File: schemas/[TEST].sql, Error: There is already an object named 'TEST' in the database. I assume this would also cause special character objects to lose special characters when being moved via deployment pipelines. ... View more

When sharing a report from a Power BI App, the link always opens the default unfiltered view. The "Include my changes" option available in the workspace experience is missing from Apps entirely.   We use Apps specifically because they handle access management for us — but that means our users have no way to share a filtered view with a colleague. Their only option right now is Chat in Teams, which isn't always practical.   Would love to see an "Include my changes" option in the App share dialog, the same way it works in the workspace.   Thank you! ... View more

Hi Team, We are encountering an AccessDenied error when trying to refresh the Power BI report in the Power BI Service (workspace/online). However, when we refresh the same report locally using Power BI Desktop, it works without any issues. Could you please help us investigate and resolve this issue? Please let us know if you need any additional details from our side. Data source error: AccessDenied. The exception was raised by the IDbCommand interface Thank you for your support. Best regards, Sunit Kumar ... View more

When converting from a local semantic model to a live connection, it leaves local semantic model folder intact. This can be removed using a workaround but it would be much more convenient if this could be done within the app.   The workaround is here; Solved: Re: Remove local model after switch to direct quer... - Microsoft Fabric Community Specifically michelsilva's response.   When developing, it is useful to use a local model and switch to a published "live connection" later. Various posts say switching back is not possible but the workaround shows there is no reason for this to be the case.   ... View more

Below is an explanation of my IQR Clustering Analysis in Excel hotspot model analysis applied to over 190,000 records of 311 Toronto Customer Initiated Service Request Data from January 1 to April 30, 2026. Model Input:   The input data for this model analysis was an Excel worksheet (or it could be queried from or located in some other place like a database) with 26 columns and 533 rows of data.   Column A of the Excel worksheet lists each of the 533 reasons (Service Request Types) why a resident of Toronto has contacted 311 Toronto to complain or make a request over the four month period studied.   Columns B-Z column headings are the names of each one of the 25 City of Toronto wards.   Each cell contained a raw count of the number of 311 Toronto Customer Initiated Service Requests made by residents of a City of Toronto ward about a specific Service Request Type.   Model Output:   The output data for this model analysis is shown in an Excel worksheet that you can email me to obtain: it still has 26 columns and 533 rows of data (buy I do also have output without the raw counts overwritten).   Instead of raw counts for the cell values, one of the following 5 text labels are used: 'High Outlier', 'High', 'Normal', 'Low', 'Low Outlier'.   The 'High Outlier' values in cells indicate that, based on distribution of raw counts of service requests (across Service Request Type) received by 311 Toronto within a given ward, complaints for a specific Service Request Type in a ward have been found to be significantly, statistically high based on the IQR Rule theory of the box & whisker plot.   Model Conclusion:   Based on the attached Excel output sample, my analysis revealed that not all City of Toronto Wards are the same in terms of the time, energy and resources that the City must spend fixing the various service requests logged by residents.    Animal Noise complaints are significant issue in only 3 of the 25 City of Toronto Wards for the first four months of 2026: Parkdale-High Park (04), Toronto Centre (13) and Toronto-Danforth (14). It is for this reason, that their cell values are shaded yellow and have the words 'High Outlier' written in red.   Residential / Yard Waste / Missed proved a significant issue for only 2 Wards and their cell values are shaded yellow with the words 'High Outlier' written in red.   The Hotspot Analysis Spreadsheet Template used to automate this analysis works on over 8,000 columns and as many rows of data as your version of Microsoft Excel accepts. The process will run as fast as your computer chip can handle. And, this IQR analysis process is an easier to apply and interpret segmentation process than either K-means Clustering or Hierarchical Clustering. ... View more

It would be good to have a recycle bin in Power BI. Today, we can recover the workspace from Admin center but their is no way to recover the reports which are deleted.   Expected Behavior Recyle bin should hold all the deletion which has happened. A restore option should then be avaiable. ... View more

PROBLEM STATEMENT The PBI Audit Log doesn't provide a way to link App-Owns-Data activity to a user since it is "user-agnostic". Everything shows under the app's identity rather than logging a property that distinguishes User A from User B activity. As it stands today, App-Owns-Data logs basically show "we know SOMETHING happened but can't tell WHO produced it"; that doesn't offer much value.   IMPACT SUMMARY This poses signficant challenges to adoption/implementation when needing to track activity for audit/security/compliance reasons. This forces customers to create custom solutions to export data rather than leverage PBI's built-in Export feature, which is a shame.   SOLUTION By tagging App-Owns-Data activity with the EmbedTokenID that produced it, this would make it possible to correlate log activity. This empowers orgs to then ensure EmbedTokenIDs are unique to users and capture the IDs so they can link a user to the logs.   RELATED IDEAS Add Export Triggered Event Handler Include User Identity in Power BI Embedded Logs ... View more

Please add support for additional authentication methods for the Azure Databricks connector in Fabric/Data Factory Copy Data and Copy Job activities. Current documentation shows that Copy supports Personal Access Token authentication, whereas other experiences such as Dataflow Gen2 support additional authentication methods including Microsoft Entra ID.  PAT-only authentication is not sufficient for enterprise production scenarios. PATs introduce challenges around security governance, token rotation, ownership, expiry, and operational support. Databricks also recommends OAuth where possible instead of PATs because OAuth provides stronger security.  In our current Copy Data / Copy Job implementation, we are only able to connect to serverless Databricks SQL/warehouse-style endpoints, and we are not able to use the other Databricks cluster types required for our workloads. This limits flexibility for existing Databricks architectures where teams need to connect to specific non-serverless or interactive compute resources. Please consider adding support for enterprise authentication options such as: Microsoft Entra ID authentication Service principal authentication System-assigned managed identity User-assigned managed identity This would reduce dependency on PATs, improve security and governance, simplify credential lifecycle management, and provide more flexibility when connecting Fabric/Data Factory Copy activities to Azure Databricks compute. ... View more

We have data agents working on top of date that comes from medallion layer, shortcuts and other fabric sources. every time we try to share an agent, we start jumping through which access is the user missing loop. is in one of the medallion layers, is it in one of the lakehouses, is it in a specsific table or something else. the agent itself just returns generic responses (sometimes with actual production layer suggestion like: i can't help you right now, try asking specifically about an asset like ZCR443322 - which actaully exists somewhere in the data). this is counter-productive and very frustrating consideting that the agent itself is semi-intelligent. the idea is that the agent, instead of providing error codes that no-one understands or spewing some AI-SLOP type generic answers not connected to the data, will respond with the missing access rights that user needs in order for it work (like when trying to access a sharepoint site with no access etc.)  ... View more

The new "Grow to fit" table layout option is amazing and long overdue. I would like to suggest an improvement. Please can we have an additional option that grows to fit with equal sized columns widths in the same way that you can "Distribute Columns" in word. I appreciate that there is a custom width option however to have it automatically do it would make the end result super clean automatically ... View more

Hi Power BI Embedded is currently incompatible with web applications that enforce the Cross-Origin-Embedder-Policy (COEP) security header   Since Power BI Embedded does not currently support this scenario, applications are forced to disable COEP globally, introducing architectural and security limitations   Please provide official support for COEP-compatible Power BI Embedded scenarios or document the limitations and recommended workarounds Our applications need to enable the following HTTP response header: <add name="Cross-Origin-Embedder-Policy" value="credentialless" /> Thanks ... View more

Hey team, Is there an ETA for supporting Fabric Capacity Contributor assignment via API? The Capacity Contributor permission is critical for organizations that want to give end users the ability to create workspaces and assign Fabric capacity — without granting full Capacity Admin permissions. This is an important permission boundary that many customers rely on for least-privilege access models. However, based on my current understanding, the API only supports assigning Admin permissions. Assigning the Contributor role is currently only possible through the Fabric Admin Console, which introduces two significant pain points: Operational overhead — It requires manual effort from Fabric admin teams for every new Fabric capacity. Limited automation — It blocks the ability to set up and manage Fabric environments programmatically at scale. Supporting Capacity Contributor assignment via API would unlock fully automated Fabric provisioning workflows and reduce the administrative burden on platform teams. Would love to hear if this is on the roadmap! ... View more

We have DEV -> UAT -> PROD workspaces with deployment pipelines moving content between these.  We also use variables to allow us to dynamically change connections destinations and other names that changes between these, but there are some things that can't use variables, which requires pipeline rules.    The problem with these rules are that only the person who creates them are able to see the content of it, and change it. It is a very immature system as it is hard to maintain and organize properly. If these deployment rules were stored in a variable object instead, it would be easier to maintain and more flexible. ... View more

The current dashboard subscription has only options for Hourly, Daily, Weekly and monthly. However, it would be helpful if we have option for fortnightly too. There are lots of organisation that have payment cycles fortnightly in NZ. Please have this option added in the repeat category.  ... View more