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

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

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

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

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

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

When we create a connection using a key vault reference, it properly allows us to select the reference in a drop down, type the secret name, and it works perfectly.  Whenever you come back to the same connection, which is now using the key vault reference, the UI behaves the same as if it was using a service principal key, meaning: - no dropdown or something pointing to the key vault reference - a masked value, implying it is actually a key, and not a key vault reference.   Problem this brings is that any issue with the connection will lead to an inestigation if it is actually using the KV reference or direclty a key. This usually will require updating the key of the SP, the key stored on the key vault, and in the connection to confirm what is actually happening.   Expectation would be that whenever a key vault reference is used, the UI clearly shows that (blocking edits on the key value, and probably showing the key vault reference name) ... 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

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 are currently using Matrix and Chart visuals in Power BI reports with enabled Drill Through, Drill Down, and Drill Up functionality for end users.   However, when users right-click on a visual, Power BI displays a wide range of context menu options beyond the drill-related actions. This includes several additional options that are not relevant to our reporting scenarios. Current Behavior: Right-clicking on a visual displays multiple context menu options. Users are presented with actions that are not required for their use case. The large number of options can be overwhelming and confusing for business users. This impacts usability and reduces overall adoption of reports. Expected Behavior: We would like report developers to have more control over the right-click context menu. Specifically: Ability to customize which options are shown in the context menu. Option to restrict the menu to only essential drill-related actions: Drill Through Drill Down Drill Up Ability to hide or disable unnecessary options based on report design. Business Impact: Improves overall user experience and usability for business users. Reduces training efforts and user confusion. Simplifies report interaction and navigation. Enhances governance and control over report behavior. Encourages wider adoption of Power BI reports across the organization.   ... View more

when using a slicer with a slider bar, there is always a popup with the fieldname that shows directly over the value that you want to change, how helpful would it be to optionally (or by default) hide this popup?     Thanks! ... View more

I'm 99% sure that Version: 2.155.756.0 64-bit (June 2026) power BI desktop broke snowflake key pair auth.   I am only getting this back from even a plain query that has just 1 line of doing the database connection: Expression.Error: We cannot convert the value null to type Text. Details: Value= Type=[Type] These queries were working a few days ago, and I know the user/account/warehouse/key pair are good, I'm actively using them elsewhere. ... 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

Summary: When using Snowflake-managed Iceberg tables with an ADLS Gen2 external volume, Fabric requires a manual table shortcut for each Iceberg table. Worse, when the Iceberg table is recreated (e.g., via dbt CREATE OR REPLACE TABLE), Snowflake writes to a new folder with a new unique suffix (e.g., MyTable.ob8ZlxyE → MyTable.Kx9mP2qR). The existing Fabric shortcut continues pointing to the old folder, showing stale data. This requires manual shortcut recreation after every table rebuild — making the ADLS approach impractical for automated dbt pipelines. The OneLake Direct approach (Snowflake database item) handles this automatically, but it has two significant limitations: (1) it requires Snowflake and Fabric to be in the same Azure region, and (2) it locks the data into OneLake as the sole storage location. Writing Iceberg data to ADLS instead of OneLake enables a multi-consumer architecture — the same Iceberg tables can be read by Fabric, SAP Business Data Cloud, Databricks, Spark, or any other Iceberg-compatible engine without granting each system access to OneLake. This is one of the core value propositions of the open Iceberg format: write once to neutral storage, read from anywhere. Forcing data into OneLake to get automatic table discovery reduces Iceberg to a 1-to-1 integration between Snowflake and Fabric, negating much of its benefit as an open table format.   Requested Capability: Automatic Iceberg table discovery and shortcut resolution for ADLS Gen2-backed storage, so that Fabric stays current when Iceberg tables are recreated at new paths. Possible Implementation Paths: Add Iceberg support to schema shortcuts — Schema shortcuts already auto-discover Delta tables in a folder. Extending this to trigger Iceberg-to-Delta virtualization (the same conversion that individual table shortcuts already perform) would allow a single schema shortcut pointed at an ADLS folder to automatically surface all Iceberg tables — and resolve to the current folder when tables are recreated. Allow Snowflake Database Item to work with ADLS external volumes — Today, creating a Snowflake database item in Fabric with an ADLS-backed external volume fails with InvalidExternalVolumeConfiguration: External volume has invalid OneLake URL. Removing the OneLake URL restriction would let ADLS-backed Iceberg tables use the same automatic discovery that OneLake Direct already provides. Fabric would query Snowflake's catalog for metadata (resolving the current folder path) and read data files from ADLS. Support an Iceberg REST catalog as a shortcut source — Allow Fabric to connect to a standard Iceberg REST catalog endpoint (e.g., Snowflake Open Catalog / Polaris) and auto-discover tables. This would decouple Fabric from any specific storage path and work with any Iceberg catalog provider, not just Snowflake. Business Impact: ADLS-backed Iceberg tables enable a multi-consumer data architecture where Snowflake writes once and multiple platforms — Fabric, SAP, Databricks, and others — can each read from ADLS independently. This avoids duplicating data into each platform's proprietary storage and is the intended use case for the open Iceberg format. Without automatic table discovery for ADLS, organizations must either: (a) restrict dbt to incremental materialization only (no full rebuilds), (b) build custom automation using the Fabric Shortcuts REST API to recreate shortcuts after every dbt run, or (c) abandon ADLS and write to OneLake, accepting a 1-to-1 Snowflake–Fabric integration that excludes other consumers. All three add cost, operational complexity, or architectural compromise.   Environment Details: Snowflake (East US 2) writing Iceberg V2 tables to ADLS Gen2 via external volume dbt managing table materializations (CREATE OR REPLACE TABLE) Fabric Lakehouse with schema-enabled shortcuts Tested June 2026 ... 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

PBIX file is not supported for Power BI MCP server as it requires report/UI + packaging layer which is outside of MCP scope. We need a feature where PBIX files can be created using Power BI MCP server ... View more

Currently, Power BI administrators do not have a scalable and programmatic way to extract refresh history across the entire tenant using Admin APIs with a service principal. This limitation creates significant challenges for centralized monitoring, governance, and operational reporting of dataset and dataflow refresh activities.   Proposed Enhancement: Enable a dedicated Admin API endpoint (or extend existing ones) that allows tenant-level extraction of refresh history for datasets and dataflows, accessible using a service principal (app-only authentication), without requiring delegated user context.   Key Requirements: Support tenant-wide refresh history extraction across all workspaces (including personal and shared workspaces where applicable). Allow service principal authentication to ensure automation, scalability, and secure integration with enterprise monitoring tools. Provide granular refresh details, including: Dataset/Dataflow name and ID Workspace name and ID Refresh start and end timestamps User name or Email Status (Success/Failure) Error messages and failure reasons Trigger type (scheduled, manual, API, etc.) Support incremental extraction (e.g., via datetime filters) to enable efficient data ingestion pipelines. Ensure pagination and performance optimization for large tenants. Business Value: Enables enterprise-grade monitoring and alerting solutions beyond current UI limitations Improves data reliability and SLA tracking across BI environments Supports audit, compliance, and governance use cases Reduces dependency on manual exports or fragmented workspace-level API calls Aligns with industry best practices for automation-first administration Current Challenges Without This Feature: Admin APIs today provide limited or workspace-scoped insights, requiring iterative and inefficient API calls Lack of service principal support restricts automation and forces reliance on user-based authentication No unified way to build a centralized refresh monitoring dashboard across the tenant Expected Outcome: A robust, scalable, and secure Admin API capability that empowers organizations to programmatically retrieve and analyze refresh history data at tenant level, unlocking advanced BI operations, observability, and governance. ... View more