We are currently in the process of migrating a large number of SQL Server (SSMS)–based workloads to Microsoft Fabric Spark SQL / Lakehouse notebooks. In SQL Server, most of our legacy queries rely on case‑insensitive collations (for example, SQL_Latin1_General_CP1_CI_AS). As a result, string comparisons such as attribute names, option‑set values, and metadata fields work seamlessly regardless of casing (camel case, upper case, lower case). In Fabric Spark SQL, however: String value comparisons are case‑sensitive by default The spark.sql.caseSensitive setting only affects column names, not string data There is currently no way to define or enforce a case‑insensitive collation similar to SQL Server Because of this difference, when migrating existing SSMS queries to Fabric: Queries that worked correctly for years now fail silently or return no data Every affected comparison must be manually rewritten using LOWER() / UPPER() This change needs to be applied across hundreds of views, CTEs, and joins The manual effort is significant and error‑prone, especially for large enterprise DW migrations From a migration and maintainability standpoint, this creates a major challenge: It substantially increases migration effort and timelines It introduces risk of missed transformations and data quality issues It makes direct parity between SSMS and Fabric difficult to achieve Request / Ask We would like to understand if Microsoft Fabric has: A roadmap item to support case‑insensitive collations (or equivalent behavior) in Spark SQL A recommended platform‑level configuration or abstraction to handle SSMS‑style case‑insensitive comparisons Any best‑practice guidance or tooling to reduce the manual refactoring effort during large‑scale migrations Even a feature such as: Session‑level or notebook‑level case‑insensitive string comparison, or Table/view‑level collation behavior, or A Fabric‑native compatibility mode for SQL Server migrations would significantly ease enterprise adoption and migration workloads. We would appreciate your guidance on the best approach going forward and whether this limitation is expected to change in upcoming Fabric releases.   Thank you for your support. Best regards, Naveen   ... View more

Currently, when a Fabric SQL Endpoint or Warehouse hits the 2,048 max connection limit due to application leaks (e.g., JDBC/TDS), the workspace enters a "hard deadlock." The Critical Gap in P-SKU: Unlike F-SKU (Fabric) users who can at least restart their capacity via the Azure Portal, P-SKU (Power BI Premium) customers lack a capacity restart button. If a rogue application saturates the gateway: T-SQL is blocked: Admins cannot connect to run KILL commands. No Self-Service Reset: There is no UI-based mechanism to "reboot" the endpoint or flush sessions. Support Dependency: We are forced to wait hours for 1st-level support to escalate to SRE teams just to clear a session table. It took 24 hrs to resolve and all admin & users not able to login and consume data. The Proposal: I am calling for a REST-API or Portal-based "Emergency Valve" in the Fabric/Power BI Admin portal: "Force-Disconnect All Sessions": A UI trigger that instructs the Gateway to drop all active TDS handles for a specific Lakehouse/Warehouse without requiring a T-SQL handshake. "Emergency Single-User Mode": A toggle to block all non-admin incoming connections while we remediate rogue application code. Why this is urgent: As we migrate enterprise workloads to Fabric, a single coding error in a JDBC-connected portal (internal app, external app) shouldn't be able to paralyze a P-SKU capacity with no path for admin recovery. ... View more

When using a dark theme, the loading icon is very difficult to make out, please give us the ability to change the colour of this, or make it larger/more prominent.   Loading spinner on a dark background ... View more

Currently when using the URL icon in a table or matrix the colour of the icon is stuck as blue. This is very difficult to make out when using a theme that doesn't have a white background. Please give us the ability to customise the colour of the icon ... View more

When deploying a Variable Library using Fabric Deployment Pipeline, make it possible to set the active value set of the target workspace by using Deployment Rules.   Currently, we need to set the active value set manually in the workspace after deploying. This is cumbersome and error prone as we might forget to do it. ... 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

Hi,   I created a shortcut table in the Lakehouse where one of the columns has a length greater than 8,000 characters. However, when I reference this shortcut table in Data Warehouse views, the data in that column gets truncated. How can this issue be resolved?   Thanks, Venkat ... 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

Currently for some charts we can define the default color from theme or we can define it by choosing color manually. It will be a benificial if Microsoft introduce fx option for definening color. This will help to manage multiple corporate branding within same powerbi app.   ... View more

A DROP STREAM command is getting automatically excuted shortly after a STREAM gets created ... 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

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

Hello,   Currently it's not possible to update our gateways through the web portal. After checking a few things with the admin and machine admin, it doesn't work at all. The problem is identifed on our side: the update process doesn't take the proxy into consideration. So the idea is : Is it possible for the update process to take the machine’s proxy settings into account, or, if not, to allow configuring a proxy specifically for the update process?   ... View more

Currently, Materialized Lake Views (MLV) in Microsoft Fabric offer two actions when a data quality constraint is violated: FAIL (which stops the refresh) and DROP (which silently removes the record). While these are useful for binary "all-or-nothing" or "clean-data-only" scenarios, they lack the flexibility required for robust production data engineering.   The Problem: FAIL is too disruptive for large datasets where a single minor violation shouldn't halt an entire pipeline. DROP results in data loss. While the lineage view shows the count of dropped records, there is no native, automated way to inspect or recover the specific rows that were excluded without manual auditing. Proposed Solution: I am suggesting a third option: ON MISMATCH QUARANTINE. When this option is selected: 1. Violating records are excluded from the main Materialized Lake View (similar to DROP). 2. These records are automatically redirected into a system-managed "quarantine" table or a sidecar hidden table associated with the MLV. 3. The quarantine table should include metadata such as the Constraint Name violated and the Timestamp of the refresh. Why this is needed: This feature would allow data engineers to maintain "Medallion" architecture integrity while providing a clear path for data remediation. It turns MLVs into a true data quality gate where bad data is captured for review rather than simply deleted or used as a reason to crash the system. ... View more

In Fabric Warehouse T-SQL datetime functions like GETDATE(), GETUTCDATE() return DATETIME which is not supported on the fabric Warehouse Similarly SYSDATETIME() and SYSUTCDATETIME() return DATETIME2(7) but fabric Warehouse supports only precision up to 6.  Those fuctions should return supported data types.  Initial issue with some code examples: issues with datetime2 and datetime functions in fabric warehouse and datetime functions in fabric warehouse ... View more

Hi, on desktop version ( propertis \ Header icon ) can be helpful to have an option " OFF All, to have all "Icons" OFF with one click  ... 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

I would like to suggest adding more flexibility to how page tabs are displayed in Power BI Desktop, especially for users working with large semantic models and reports containing many pages. In reports with long page names, the current horizontal tab strip can become difficult to manage. When adding a new page, it often gets inserted between existing tabs, which makes it time-consuming to locate—particularly in complex reports with many similarly named pages. It would be very helpful to introduce either: An option to switch between horizontal and vertical tab orientation, A hover-based pop-up panel that displays a full, scrollable list of pages, or A fixed navigation pane that shows all report pages in a structured list format. Any of these options would significantly improve navigation efficiency and overall usability for developers working in larger models. ... View more

Helllo, Can we please get these boxes removed from showing on the RHS Column. They always fault and get stuck there and are in the way and arnt required as no one uses them on that side. Thankyou ... View more