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

Currently, SAP Connectors in Microsoft Fabric do not support integration with Azure Key Vault (AKV). However, in many enterprise environments, it is a mandatory requirement to manage credentials centrally using Azure Key Vault for secure access to databases and external systems. SAP Business Warehouse Server SAP Business Warehouse Message Server SAP HANA       ... View more

When using overlay visuals (such as Cards aligned with Table/Matrix visuals), the vertical alignment appears correct on the design screen but shifts when viewed on different screen sizes or resolutions (e.g., laptop vs. large monitor). This creates inconsistent formatting and impacts the user experience. It would be helpful to have improved support to maintain consistent alignment and better control over visual sizing across devices. ... View more

Hi everyone, I’ve recently started using Fabric IQ Plan, which requires working entirely within the platform. One limitation I’ve encountered is the lack of an undo functionality - there doesn’t seem to be a button for it, and standard shortcuts like Ctrl+Z don’t appear to work either. In other Microsoft tools, this is a basic capability. For example, even in Power BI Service it’s possible to use Ctrl+Z to go back one step, which makes it much easier to safely experiment and correct mistakes. Having a similar behaviour in Fabric IQ Plan would significantly improve usability and user confidence when making changes. Is there an existing feature or workaround to revert changes (e.g. going back n steps)? Thanks in advance! Miriam ... 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 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

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

Please support OneLake Explorer in environments using Workspace-level Private Link. In secure environments where public access is blocked, users may only allow access through Workspace-level Private Link. However, OneLake Explorer currently appears to require public access or tenant-level Private Link for artifact listing. It would be helpful if OneLake Explorer could work with Workspace-level Private Link so that users can browse OneLake artifacts without enabling public access. ... 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 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

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

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

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

It would be valuable for Fabric Eventhouse to provide a built-in, standard replication service for cross-region data redundancy and failover. Today, there is no native solution, and teams must rely on custom approaches.   A first-class, Fabric-native replication capability would simplify BCDR and improve reliability for production workloads. This includes built-in cross-region redundancy and failover for regional outages, as well as native data replication scenarios such as Azure Data Explorer (ADX/Kusto) to Fabric Eventhouse (KQL DB) and Fabric Eventhouse to Fabric Eventhouse across regions. ... 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 problem: repetitive use of "rename for this visual" When using Power Query / making DAX measures, you tend to use more descriptive column names / measure names for clarity within Power BI when editing the data as a Power BI user.   However, when it comes to showing these values (columns, measures, etc.) to the end user in visuals, you often tend to rename these fields to more simplified 'display names', so that they make sense to the everyday report viewer.   I have noticed that for most visuals which use a given measure / column, I use the same 'display name' across all of the visuals.   Please up-vote if you're tired of repeating the "rename for this visual" operation! As is I must rename each of these individually for each visual, by going to the field well in the Build panel, right-clicking on the field, choosing "rename for this visual" and then updating the name. This is very repetitive. Also, if I remove and later re-add a field to the field well, it loses the name that I gave it before, and I have to "rename for this visual" yet again. To be It would be nice when creating a column / measure, if I can, there and then, choose a default display name for that column / measure, which will be used in all visuals by default.   Then, when the column / measure is added to a field well for a visual, Power BI gives it the default name that I specified, rather than the original column / measure name. That default name appears on the visual. No need to rename the field every time.   For a specific visual, a different display name may still make more sense than the default one. Therefore, using the "rename for this visual" method should still work to override the default 'display name' for that specific visual only. Reactive updates to the default 'display name' If I decide on a more meaningful wording / name for the column / measure for display purposes, I would also want to be able to modify this default visual 'display name' in the same place where it was originally defined. For example, by editing the "step" in Power Query or somehow during the creation of a measure.   If I update the default 'display name' for a field, every visual which is using that field should be updated with the new default 'display name'. That way, I don't have to go back into every visual and rename every field that was renamed.   Exception: if I manually used the "rename for this visual" option, the override value set during the "rename for this visual" operation should still be used, not the new default name. Implementation / UI In Power Query, there should probably be two ways to do this: During the Table.AddColumn function. There would need to be an extra (optional) parameter here for the 'display name'. As a button in the ribbon somewhere (for users who don't like editing M language). In this case, this would be added as a separate step after an Add Column step. It could be named something like "Set default display name". In either of these two places, you could come back and edit the display name once, and see it updated everywhere where it is used.   For DAX measures, I'm not sure how best to implement this. My instinct is: A specific function that allows the user to enter this information. For example: myInternalMeasureName = DISPLAYNAME( "default display name for visuals goes here", [normal logic to calculate my measure goes here] ) You could come back and edit the first parameter of the DISPLAYNAME function to change the display name for that measure everywhere where it is used. ... View more

Background OneLake shortcuts are a powerful feature that enables cross-workspace and cross-domain data virtualization without data movement. However, in real-world enterprise scenarios, especially when using: DirectLake semantic models SQL endpoint / TDS access Cross-workspace shortcut patterns we frequently encounter situations where delegated identity mode is required, and user identity passthrough is not consistently applied. Problem This creates a critical governance and security issue. Access is effectively executed using: connection owner workspace-level identity This means that execution context is delegated away from the calling user. As a result: loss of least-privilege enforcement inconsistent authorization behavior across engines reduced auditability of the actual user accessing the data In practice, this forces architectures where: access must be granted more broadly than intended workspace boundaries do not function as security boundaries users gain indirect access via execution context rather than explicit authorization This contradicts the expected behavior of OneLake security, where access should be governed by both shortcut path and target path permissions. Expected Behavior We would like to see support for the following model: Authentication Workspace Identity (service principal) is used for authentication Authorization The calling user's identity is always used for authorization (User identity passthrough) This should be enforced consistently across: DirectLake SQL/TDS endpoints semantic models all engines accessing shortcuts   Why this matters This hybrid model would: Preserve centralized authentication (Workspace Identity) Ensure true least-privilege access control at the user level Maintain consistent and predictable authorization behavior Eliminate reliance on: delegated identity connection owner context Align shortcut behavior with enterprise governance requirements Current Gap Currently: user identity passthrough is not consistently applied across engines delegated identity introduces execution context delegation Workspace Identity abstracts access but does not preserve user context for authorization Proposed Feature Introduce a new data access mode: Workspace Identity (Authentication) + User Identity (Authorization) Conceptually similar to: On-behalf-of (OBO) pattern in Microsoft Entra ID Additional Considerations Workspace Identity is not merely an abstraction of permissions, but introduces delegation of execution context to the workspace itself. Supporting user identity propagation across engines may require architectural changes. However: The current model, where delegated identity is effectively required in some scenarios, results in less controlled and less transparent authorization behavior. Summary To support enterprise-grade governance and security in Fabric: user identity-based authorization must be preserved end-to-end Workspace Identity should complement user context, not replace it delegated identity should be optional, not required ... View more

When I want to format multiple/all the columns in a table based off a condition in one of the columns, I have to add the conditional format to each column in my table individually. I think it'd be really cool if there was a feature where I can either copy/paste the conditional formatting to selected columns or if there was a way to format all the columns at once. ... View more