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

Matrix visuals could significantly enhance the user experience by emulating Excel's intuitive sorting, searching, and filtering capabilities, even for hierarchical columns. This idea would the current limitation in Power BI's matrix visuals, which lack a comparable experience to Excel's established standard for data manipulation. ... 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

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

Secondary axes are automatically managed by the system in some cases, making it problematic for report creators with no control over intervals, ticks, and other crucial components, limiting effectiveness of various types of analysis. It would be great if the secondary axis included comprehensive format settings so that greater control over displayed data is provided. ... 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

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

Our team would like join to our security mapping table in the rule and call the employee that is querying's username and filter by it. It would look like: select * from my_table inner join security_table on security_table.projectID = my_table.projectID where security_table.username = username() This would allow us to dynamically set our RLS on the table. ... 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

Enable Incremental Refresh for Power BI Pro users, not just Premium. ... 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

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

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

Having readability issues with the notebook logs where the master notebook is running multiple child notebooks iteratively using notebookutils.notebook.runMultiple() and DAG.   The column widths in the log output cannot be expanded(as highlighted in the snap below), which makes it difficult to review and analyze the log details efficiently. This limitation impacts our ability to quickly identify information related to specific tables or data pipelines in Microsoft Fabric notebooks within Power BI.   Please take this up and fix as early as possible that would help us analyse the logs effectively.       ... View more

Hi, I think that it could more useful to have a Set multi variables activity for pipelines in order to use only one activity to set multiple variables without implementing more Set variable activity in the same pipeline. Less development effort, more readability. Thanks   Work better to work less. ... 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

Paginated reports - please make it available in Pro as well as Premium .. thank you ... View more

Problem Statement: Currently, Power BI only offers Row-Level Security (RLS) to control data access, but there's no native way to control which report pages users can see in the navigation pane. All users with report access can view all pages, even if those pages aren't relevant to their role. Requested Feature: Implement Page-Level Security (PLS) that allows report developers to: Define which user roles can access specific report pages Automatically hide pages from the navigation pane for users without access Prevent unauthorized users from manually navigating to restricted pages Business Use Case: Many organizations have reports with different sections for different audiences: Executive dashboards for leadership Detailed financial analysis for finance teams Operational metrics for operations staff HR metrics for HR department Currently, we must create separate reports or apps for each user group, leading to: Content duplication and maintenance overhead Multiple versions of similar reports to manage Increased workspace clutter Higher administrative burden Proposed Solution: Add a "Page Security" setting similar to RLS in Power BI Desktop Allow assignment of security roles to individual pages In Power BI Service/Apps, only display pages the user has permission to view Integrate with existing RLS roles for unified security management Benefits: Simplified report management (one report instead of many) Better user experience (users only see relevant content) Reduced administrative overhead Consistent with existing RLS security model More scalable enterprise deployment Alternative Considered: Creating multiple reports/apps works but creates significant maintenance challenges and doesn't scale well for large organizations with many user roles. ... 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