I successfully separate Selection State(Selected) from Selection State(Unselected) with transparency option. However, If the user does not make any selection(means selects all) the display of the button is same as Selection State(Unselected). It must be same as Selection State(Selected). Technically, none selected means All selected(same as any selection) ... View more

The UI for using variables in a shortcut could also be enhanced by adding the "Value set name" below the value when shown in the "Manage Shortcut" slide out.   This would indicate which set the value came from to verify it is as desired if you don't recognize the guid (don't we all have every guid in our tenant memorized already? who needs workspace names, I know all the guids!!!)     ... View more

Status: Power BI Desktop currently uses a Power BI–specific project structure inside PBIP files, which includes additional metadata files such as definition.pbidataset, diagramLayout.json, and other Power BI–specific annotations. While this structure is required for Desktop functionality, it differs significantly from the clean, TOM‑compatible TMDL folder structure produced by Tabular Editor (“Save to Folder”).  This creates friction for teams who want to: Maintain semantic models in source control using the pure TMDL folder structure Use Tabular Editor as the primary modeling tool Keep Power BI Desktop as a consumer of the model rather than a co‑author Avoid unnecessary metadata churn in Git Track changes on individual artifacts (Columns, Measures,...) Align Power BI Desktop with Azure AS / SSAS / Fabric semantic model workflows Request: Change Power BI Desktop to load and save semantic models directly in the Tabular Editor TMDL folder structure, and add PBIP‑specific metadata files within this structure.    Benefits: Full alignment between Power BI Desktop and Tabular Editor Cleaner Git diffs and better DevOps workflows Easier migration from SSAS/AAS to Power BI Reduced metadata noise More predictable modeling workflows for enterprise teams Why this matters: Tabular Editor’s TMDL folder structure is already the de facto standard for semantic model development. Allowing Power BI Desktop to work directly with this structure would unify the modeling experience across tools, simplify governance, and reduce friction for enterprise deployments. ... 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

Mirrored DBs do not support ownership transfer today. This becomes an issue when someone leaves the company. And the user tied to the ownership is beeing disabled. That means you need to recreate the whole mirroring database and recreate all shortcuts, jobs pipelines etc etc.. Alot of work. The Take‑Over functionality exists for other Fabric items but excludes mirrored DBs. This is a critical operational need for enterprise workloads. Please consider developing this functionality.  ... 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

Many customers migrating from AWS to Microsoft Fabric use AWS Glue Data Catalog as their central metastore for data stored in Amazon S3. While Fabric supports accessing S3 data (for example, via shortcuts), it cannot consume or reuse Glue Data Catalog metadata. As a result, customers must manually recreate databases, tables, schemas, and partitions in Fabric Lakehouse, even though this metadata already exists and is actively maintained in Glue. Impact Increased migration effort and time Duplicate metadata management (Glue + Fabric) Higher risk of schema drift and inconsistencies Reduced value of shortcut-based migrations from S3 Friction for hybrid or phased AWS - Fabric adoption Customer Expectation Customers expect Fabric to: Discover databases and tables already defined in Glue Reuse existing schemas and partition definitions Register Glue tables from S3 as Lakehouse tables without rebuilding metadata Suggested Enhancement Native connector or integration with AWS Glue Data Catalog Ability to import or synchronize Glue metadata into Fabric Lakehouse Support for registering Glue-managed tables as external tables in Fabric Business Value Significantly reduces AWS to Fabric migration friction Improves hybrid cloud and coexistence scenarios Makes Fabric more attractive to AWS-centric customers Aligns with Fabric’s goal of simplifying data lake interoperability ... View more

Today, changing collation settings such as case‑sensitive or case‑insensitive behavior in Semantic Models and Lakehouse environments is not straightforward. It usually requires using JSON DDL scripts, advanced SQL commands, or backend configuration changes. This makes the process difficult for many users. Business users are unable to manage it on their own, and even technical users often find it complex and error‑prone. Small mistakes can lead to misconfiguration, unexpected query results, or broken relationships. In many cases, customers need to raise support tickets or rely on experts to make these changes, which slows down their work. The experience is also inconsistent across different artifacts. In Lakehouse scenarios, collation behavior is tightly linked to the SQL endpoint, which adds more complexity and confusion. Customers generally expect such a basic and important setting to be available through a simple, guided user interface instead of low‑level scripts and manual steps. Proposed Solution Introduce a simple, user‑friendly button in the UI that allows users to control collation behavior without needing scripts or advanced configurations. For Semantic Models or Datasets, add a Collation Mode option under Model Settings. This should be presented as a clear toggle or button where users can switch between Case‑Insensitive and Case‑Sensitive. The button should include brief, helpful text explaining how the selected option affects DAX queries, SQL queries, relationships, and overall performance. This allows users to understand the impact before making the change. For Lakehouse and SQL Endpoints, add a Collation Configuration button directly in the Lakehouse settings and SQL Endpoint settings. With a single click or toggle, users should be able to choose between Case‑Sensitive and Case‑Insensitive behavior. Once selected, the setting should be applied consistently across tables, metadata, and query execution to ensure predictable and consistent results. By introducing a simple button or toggle in the UI, customers can manage collation settings confidently and independently. This removes the need for manual scripts, reduces errors, improves consistency across artifacts, and provides a much better overall user experience. ... View more

Consider a test user who has been assigned Lakehouse  Write permission to a specific folder in a Fabric Lakehouse using one lake security roles. This permission reflects correctly in Azure Storage Explorer, and the user can access the folder as expected. However, the permission does not appear correctly in OneLake Explorer. Specifically, the Lakehouse does not appear under 'My Workspace' in OneLake Explorer for that specific user. Seems like a limitation with the one lake explorer as it is still in preview. Would be of great help if this is fixed. ... View more

To address the limitations of our current slicers, which are less advanced and potentially confusing compared to our competitors, a new and enhanced list and dropdown slicer should be designed with a wider range of customization options, incorporating industry best practices, and include innovative features like the ability to copy and paste lists. ... View more

I would like to be able to schedule a data refresh of the Auto Attendant & Call Queue historical reports to the PowerBi service I publish reports to the PowerBi service so managers can view data on their call queues and auto attendants. This feature was available in previous version of this report. Version 3.2.3 no longer allows you to schedule a refresh of the report due to a data source query error. ... View more

Microsoft Fabric currently provides lineage at the item level (datasets, lakehouses, notebooks, pipelines), but does not expose column-level lineage within Fabric itself. For teams building transformations using: Fabric Lakehouse (Delta tables) SQL Analytics Endpoints Dataflows Gen2 Pipelines / Notebooks there is no way to see how individual columns flow, transform, or propagate between sources and downstream tables/views inside Fabric. Ask: Provide a column-level lineage view directly in Microsoft Fabric, showing: Source column -> target column mappings Transformation paths across notebooks, pipelines, SQL, and dataflows Cross-artifact lineage (Lakehouse -> SQL Endpoint -> Dataset, etc.) Limits: Fabric lineage graph only shows artifact-level relationships No visibility into column-level dependencies Purview does not currently provide complete or end-to-end column-level lineage for Fabric workloads. ... 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

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

Renaming objects such as Tables, Measures, etc. in a semantic model breaks all reports that leverage the old naming convention. So, if I make a change to a measure name all Power BI reports leveraging that name change. My suggestion is for each measure to have a Measure ID or Table ID that it references. So if the Name of the Table changes a name the semantic model knows what ID the Table is, and all related measures in various reports still refence the ID so that a name changes doesn't break everything. ... View more

Description: When running multiple cells in a Fabric notebook (via "Run All" or "Run All Above"), the UI should automatically scroll to follow the currently executing cell and display its output in real-time. Currently, users must manually scroll to watch execution progress, and output sometimes doesn't render until the entire run completes. This makes it difficult to monitor long-running notebooks or catch errors early. Requested behavior: Automatically scroll the notebook view to the active cell as execution progresses Stream cell output in real-time as each cell runs Provide an option to toggle auto-scroll on/off for user preference This would bring the Fabric notebook experience in line with Databricks, where real-time output streaming during "Run All" is the default behavior. It improves productivity by allowing users to monitor progress, spot issues immediately, and better understand execution flow without manual intervention. ... View more

The subscription email always contains "You’re receiving this email because you subscribed to the 'First' page of the ..." even when the email subscription has removed the first page screenshot.  This text only confuses users. ... View more

We love Polars. It is user friendly and it works great for our data volumes.   Today, V-Order can be applied to delta parquet tables using Spark notebooks, but not Python notebooks.   Please make it possible to apply V-Order to delta parquet tables using Polars in pure python notebooks.   We encourage Microsoft to cooperate closer with Polars, as most customers can save a lot of CUs (money) by switching from Spark (distributed compute) to Polars (single node). ... View more

Right now, only users with at least the Contributor workspace role can see or edit Shared queries in the Lakehouse SQL analytics endpoint. There's no difference in seeing or editing the queries.   I would like to have the option to share / give read access to the Shared queries to more users. So users with Read or ReadAll permissions on the lakehouse can see the Shared queries created by others, but cannot edit them.     ... View more