Soft deletion for OneLake files makes sure that deleted files are restorable for 7 days. However, customers also have to pay for the storage usage during that time. For the scenario, when writing short-lived (large) temporary files to OneLake, this feature might have significant billing cost (see model calculation below).   Scenarios, were deleting immediately would make sense: Executing Unittests and Performance tests, where the written data are only important temporarily When making use of Spark Checkpointing that will offload intermedite compute results to OneLake   Request: give customers more control over that feature and let them descide, what is the right retention period for them, as well as disabling the feature all together for a Workspace, Lakehouse (or idealy for specifc folders).   Cost comparison: Pricing page only states GB/month/GB-price (lets assume $0.023 for this model calculation). What happens when I do some performance testing (that takes 30 minutes) and write some large temporary files (50 TB total) to OneLake and delete it right after my tests? With Soft-deletion disabled, smalles billing period for Azure Storage Hot ist 1h; storing 50 TB for 1h would cost: $1.64 = $0.023 / 24 [hours] / 30 [days] * 1024 * 50 [TB] With Soft-deletion enabled, I'll need to pay for 1h + 7 days (retention period) for the 50 TB: $269.93 = $0.023 / 24 [hours] / 30 [days] * 1024 * 50 [TB] * (7 [days] * 24 [hours] + 1 [hour]) ... View more

It would be helpful to add dynamic context to visuals using a measure within this field:     ... View more

The ability to parameterize the connection would enable using separate identities (e.g. separate service principals) for dev/test/prod environments.    Having to use the same SPN in dev/test/prod introduces unnecessary risks, like accidental data modification across environments - a dev workload accidentally writing to production data, or a production workload accidentally connecting to and using data from the dev environment.   This would be solved if we could use variable library to reference the corresponding connection id for dev/test/prod service principal.   Unfortunately, the connection property in pipeline's notebook activity does not support Dynamic Content yet.   Please make this possible so we can avoid the risk of cross-contamination between environments. ... View more

I need to conditional format the row header, not just the values section.   Also I would like to be able to format the font in bold/italic and be able to define complete rows (values including row headers) to be underline/overline. ... View more

While preparing for the DataViz World Championships, I spent a significant amount of time testing accessibility with NVDA. During this process, it became very clear how important tooltips are for understanding a report, especially when combined with a logical tab order for users with limited vision. Tooltip pages are extremely helpful and visually rich for sighted users. However, in my testing with NVDA, tooltip pages were not accessible at all, as they are interpreted as images and their content is not read by the screen reader. One possible improvement would be to add an alt text field at the page level specifically for pages defined as tooltip pages, with support for dynamic text.   This alt text could describe the tooltip’s purpose and content based on the current context or selection, making the information accessible to screen reader users while preserving the existing visual experience for others. I believe this would be a relatively small addition with a meaningful impact on overall accessibility in Power BI. ... View more

Power BI should treat A and a differently as mostly these depict different values.    ... View more

The Default Value Set in the Variable Library poses a risk.   The Default Value Set will silently apply values when no explicit value set has been selected for a Test or Prod workspace.   There is no warning if we forget to select a value set in Test and Prod. This can result in deployments incorrectly using Dev values in Test and Prod - without any warning. Fabric should allow us to disable or remove the Default Value Set, and require every workspace to explicitly select a value set. ... View more

Feature request: OneLake shortcuts to support connections to ADLS Gen2 storage accounts using managed private endpoints   Currently OneLake shortcuts only support connections to storage accounts that are publicly accessible or accessible with storage networking rules in place. Shortcuts via Managed Private endpoints are not supported yet. Our organization requires all connections to go via Private Endpoints. Furthermore, networking rules are not possible in our situation, since our Fabric instance is deployed in a different Azure Tenant.   OneLake shortcuts are a great way to save compute, as we would be able to query directly on our Delta and Parquet tables in our Storage Accounts, instead of requiring compute to serve this data. Once OneLake Shortcuts via Private Endpoints are supported, I am also hoping that Databricks mirrored catalog would be working via the Managed Private Endpoint connections.   Therefore my feature request is OneLake shortcuts to support connections to ADLS Gen2 storage accounts using managed private endpoints. ... View more

Hi, I've noticed that T-SQL language of a warehouse doesn't support the recursive CTEs. It'a real pity! A such feature is more useful and comfortable one in several scenarios, f.e. to navigate an hierarchy. I hope it will be implemented as soon as possible. Thanks ... View more

Hi   Please change the translation of the panel name Format Image from Formatbild to Bildformat or Formatera bild in Swedish.               Thanks, Anna-Karin   ... View more

Proposed Solution: Allow image visuals to support Report Page Tooltips, similar to charts and tables. Enable theme JSON properties (e.g., visualTooltip) to apply to image tooltips. Provide options for customizing tooltip appearance (background, font color, font size) directly in the Format pane for image visuals. Benefits: Consistent branding and design across all visuals. Improved user experience for reports with interactive images or navigation buttons. Greater flexibility for developers and designers to create visually appealing reports. ... View more

With Snowflake's imminent change to deprecating username and password connections later this year, allowing Mirrored database's in Fabric to connect via OAuth would be an essential option for us.   ... View more

In Power BI, when I insert a new text box the default font is Segoe UI size 10pt. There is a new bug that is driving me bananas.  Every time I hit the return key to make a new line, the font resets to Segoe UI 10pt. Even if I select-all, change the cursor itself to 12pt. No matter what I do, I am constantly forced to select-all and format as 12pt over and over again.  ... View more

New Desktop app update installed an almost white user interface. There is zero contrast which is not good for the eyes. I see where some people have requested a light interface so incorporate an option to select either light or dark theme like in the Office apps. ... View more

When I modify the data desination table name in a Git repository and pull the changes into Fabric, running the dataflow from Fabric results in the old table name being used. It's only possible to change the desination table name through the Fabric UI, not the Git code.  ... View more

Fabric’s SQL endpoint currently fails when the feature.v2Checkpoint flag is present in Delta log history. This flag is automatically set when tables are written with v2 checkpoints, which is the default when adopting Databricks‑recommended practices like liquid clustering. This creates a critical gap: Databricks promotes v2 checkpoints and liquid clustering as best practices, yet Fabric’s SQL endpoint does not support them. The result is brittle workarounds that block enterprise‑scale adoption. Ask: Enable support for v2 checkpoint policy in Delta table shortcuts so Fabric can align with Databricks standards, eliminate fragile workarounds, and unlock enterprise readiness. ... View more

Dataflow Gen2 previews become very slow when a query contains several heavy merges. Right now, the only way to keep developing smoothly is to output those merges to a table and continue the work in a separate dataflow, or switch to notebooks.   If we could stage (freeze) a heavy query during development — and have it only refresh when an upstream step changes — then all downstream queries could reference that staged result instantly. This would make development much faster and let us continue building calculated columns and transformations inside the same dataflow.   This could work in the same way staging already works for refreshes, but applied to development previews to avoid recomputing heavy steps every time. ... View more

  Currently, colors are automatically assigned randomly.  It would be nice if your dev workspace was always blue, and your prod was always pink for example.  Then you'd have a good visual as to where you're working in. ... View more

Power BI report subscriptions currently send only images in the email body and need to have SSRS reports like subscription results where the complete report is available in the email body   ... View more