Issue:   Error refreshing the Dataflow Gen2 with multiple Lakehouse Schemas selected as the data destination: WriteToDataDestination: There was a problem refreshing the dataflow: "Couldn't refresh the entity because of an issue with the mashup document. MashupException.Error: Expression.Error: We cannot convert the value null to type Table. Details: Reason = Expression.Error; ErrorCode = 10277; Microsoft.Data.Mashup.Error.Context = User". Error code: 104100.    Investigation:   Reproduction Steps:  Create a Dataflow Gen2 and in the Data destination settings, choose the default Lakehouse destination and save it:  Proceed with the refresh.  The refresh completes successfully without any issues.  Also, if we modify the Data destination to a Lakehouse and select the single schema for all destination tables and save it:  Trigger the refresh again.  The refresh succeeds as expected.  But the issue is when we, update the Data destination to a Lakehouse, but this time map the tables to multiple different schemas instead of a single schema and save it: Initiate the refresh. The refresh fails and throws the below error:  Observed Behavior The failure occurs only when multiple schemas are configured as the destination. The issue is reproducible across refresh attempts. The Dataflow Gen2 UI allows selecting multiple schemas, but the refresh runtime does not handle this configuration correctly. Additional Observation (UI Inconsistency) When “Full hierarchy” is set to True in the Dataflow Gen2 data destination: The runtime effectively expects one schema for all tables. However, the UI still allows users to select different schemas per table. Saving this configuration is allowed, but refresh fails afterward. This strongly suggests a design inconsistency rather than an intentional limitation.   Current Workaround & Impact To work around this issue, we are currently: Creating multiple Dataflow Gen2 instances Each Dataflow writes to the same Lakehouse, but only one schema per Dataflow.   Due to this limitation, the number of Dataflows that need to be created and maintained has increased significantly.   Ask to Product Team If multiple schemas are not supported, the UI should prevent users from configuring them. If the UI allows this configuration (as it does today), Dataflow Gen2 should support writing to multiple schemas within the same Lakehouse without refresh failures. We request the Product team to: Review this behavior as a potential defect or design gap Align the runtime behavior with the UI experience Consider enabling multi‑schema destinations in a single Dataflow Gen2, or clearly blocking it in the UI if unsupported   This enhancement would significantly improve usability, scalability, and customer experience when working with structured Lakehouse environments. ... View more

Si tienen la siguiente opción dentro de la versión web de Power BI quizás sería buena idea QUE HAGA LO QUE MENCIONA DENTRO DEL RECUADRO Que es esto de tener que ajustar mis filtros de fecha porque al pasar a la versión web el BI en lugar de marcar con NOW() mi fecha hora actual (UTC -4) marca el UTC normal. Literalmente el apartado ZONA HORARIA debería estar arreglando eso pero no lo hace ???????????????????????????????? ... View more

Microsoft:   Assume you have created a Hierarchy in Table Panel. It becomes a container now.   Now Right-click on table  field (Region) , and add to the Hierarchy. Repeat this step for (State). Now drag the Hierarchy in to the canvas   -or-    Click on the check-box before the Hierarchy name   When you perform one of these, the visualization panel shows the Hierarchy with Region and state as subcategory.   Remember:   Why am I writing to Microsoft is that the Hierarchy in Visualization panel is not linked to the Hierarchy in the table, which is the limitation. I hope Microsoft PowerPoint BI team would have fixed.   So, what is the result of this, your Hierarchy in the Visualization pane will not automatically update, if add another field in, City as subcategory to this  hierarchy, So to reflect the updated Hierarchy in the Visualization panel, delete the Hierarchy with Region, and State, and drag the updated Hierarchy containing Region, State, and city fields.   Prabhu   ... View more

It would be nice to have a new Azure map style that is similar to the current greyscale (light), but would allow for better distinguishing of water and natural features. These features would be a muted blue green, and ideally this would be done through a checkbox to let you turn off/on different features depending on the use case, as well as a transparency slider on the map style (base). The current grey scale (light) makes it hard to distinguish rivers and bodies of water an robs the user of additional context.   Thank you for your consideration.   ... View more

Enable filtering capabilities in Lineage View (similar to Workspace List View) so that users can apply the same filters and view a consistent, scoped representation of workspace items and their dependencies. This would improve usability and alignment between the two workspace browsing experiences. ... View more

Hello, while working in Power BI I tried to create a banner at the top of the report with a title, and I wanted this banner to remain fixed while scrolling down. However, I see that this option does not currently exist. Could you please add this functionality? It would be much more didactic and professional. A fixed bar at the top of the report, independent of scroll, where buttons can be added for navigation while moving up and down the page. ... View more

Product Microsoft Fabric Area Data Warehouse / SQL Type Bug / UX issue Description In Microsoft Fabric Warehouse, queries using CTEs behave inconsistently between execution and UI-based view creation. A SELECT statement with CTE runs successfully, and the following also works when executed manually:   ``` CREATE OR ALTER VIEW schema.view_name AS WITH ... SELECT ... ``` However, using the “Save as view” button on the same query fails with the error: > Incorrect syntax near the keyword 'WITH'. This error is misleading. The SQL syntax is valid, and the view can be created successfully when CREATE OR ALTER VIEW is executed explicitly. The failure appears to be caused by how the UI wraps the query internally. Impact Valid SQL is rejected only via the UI Users are led to believe CTE is unsupported in Warehouse views Results in unnecessary investigation and loss of trust in the authoring experience Expected behavior “Save as view” should preserve valid CREATE VIEW semantics, or Clearly communicate any limitations instead of returning a misleading syntax error   ... View more

When using the Copy Data activity with a REST source, query string parameters must be manually concatenated into the Relative URL field. This is error-prone, hard to read, and does not scale when parameters are dynamic or vary in number. Every comparable API tool (Postman, Power Automate HTTP connector, Logic Apps) provides a dedicated key-value parameters table that cleanly maps parameter names to values — including dynamic expressions.   Request: Add a "Query Parameters" section to the Copy Data activity REST source, where each row accepts a key and a dynamic or static value, and the tool assembles the query string automatically.   Current workaround: Pre-building the full query string in a Set Variable activity before the Copy, which adds unnecessary steps and complexity.   This would significantly improve usability for anyone calling paginated or filtered REST APIs in Fabric pipelines. ... View more

Currenly the only method to drop / truncate tables in a Lakehouse during a pipeline run is to start a spark session and initiate spark.sql to execute a sql statment. In Data Factory the script activity does not support lakehouse as source and the sql endpoint of a lakehouse does not support drop. Can an activity be created or the script activity updated in Data Factory pipelines to execute a sql statement on a lakehouse without having to start a notebook and spark session to do it.  Starting a spark session can take up to 5 mins so takes too long if we simply want drop/truncate a few lakehouse tables.         ... View more

Can you please update this so multiple people have ownership to update the subscriptions?  This causes dis-satisfaction when someone moves departments are leaves the company.  ... View more

I'm trying to mirror a database on an Azure SQL Managed instance. The SQL instance is currently set to UAMI, and when I try to mirror it in the wizard, I get the error that only SAMI is supported. Since the database is a production database and cannot be modified to SAMI, are there plans to enable mirroring under UAMI as well? ... View more

The data preview in the Results section of a SQL query (in either a warehouse or lakehouse) is very difficult to read as it is currently set up. It would be massively improved by implementing the following: Show the total row count at the bottom of the Results rather than just showing the row preview limit (10,000) if the actual row count goes beyond this Ideally, this would show something like Columns: 4  Rows: 56012  Rows Displayed: 10000 Allow columns in the Results to be dragged wider so it's possible to read the full column names and data As far as I can see, there's currently no way to do this in Fabric ... View more

Problem Statement As Fabric/Power BI administrators, there is currently no straightforward, tenant‑wide way to identify which semantic models have Row‑Level Security (RLS) applied. Today, the only option is to: Scan workspaces individually using Workspace IDs Drill down one level to the semantic model Extract metadata to determine whether RLS is configured While this approach works, it is manual, time‑consuming, and not scalable for large environments with hundreds or thousands of workspaces. Proposed Idea Introduce a built‑in, centralized way for administrators to view RLS configuration metadata across the entire Fabric tenant, without needing to scan each workspace individually. Ideally, this would include: A tenant‑level report or admin view showing all semantic models with RLS enabled Exposure of RLS metadata via: Fabric Admin Portal Enhanced Admin APIs or XMLA/Metadata endpoints Filters by workspace, dataset/semantic model, or RLS presence (Yes/No) Why This Matters This capability would significantly improve: Security auditing and compliance Governance and risk management Operational efficiency for admins Administrators need fast answers to questions like: Which semantic models are protected by RLS? Where is sensitive data being restricted (or not)? Are RLS policies consistently applied across the organization? Business Value Reduces manual monitoring effort Improves security posture and compliance readiness Enables proactive governance at scale Aligns with enterprise‑grade admin expectations for Fabric Summary A tenant‑wide, readily available view of semantic models with RLS enabled would be a major enhancement for Fabric administrators. Having this information centrally available—rather than derived through workspace‑by‑workspace scans—would make auditing, governance, and security management far more effective. ... View more

Currently, Eventstreams only display the last modified date, making it difficult to understand the full history of changes applied to a stream.   Having a change log or journal table that tracks all modifications would be extremely helpful for troubleshooting. If an issue arises, it would be much easier to review what changes were made, who made them, when they were applied, and the type of change. This visibility would significantly improve the ability to diagnose and resolve issues efficiently. ... View more

Staring at a white screen all day is frying my retinas. This is a health & safety issue at this point. ... View more

There is currently no native way to enforce a 'Locked Hierarchy' sort in Power BI. While the Matrix visual provides excellent grouping with expand and collapse features, it does not allow users to sort child rows by a measure such as Sales while keeping the parent rows sorted alphabetically or by a different custom logic.   Could you please implement the feature way to enforce a 'Locked Hierarchy' sort in Power BI and  allow users to sort child rows by a measure such as Sales while keeping the parent rows sorted alphabetically or by a different custom logic. ... View more

Description: Current error messages are often unclear and require debugging effort. Errors like bag_pack expects even arguments are not helpful. Current behavior: Errors lack context and actionable guidance. Expected behavior: Include failing expressions and suggested fixes. Show: Exact failing expression Suggested fix Impact: Reduces debugging time and improves developer experience. ... View more

Description: Comparing versions of JSON/XML payloads requires complex custom logic. Current behavior: No built-in diff capability. Expected behavior: Provide functions like json_diff() and xml_diff(). Impact: Simplifies change detection and CDC scenarios. ... View more

Description: We are currently using Microsoft Fabric with Eventhouse -> Shortcut -> Lakehouse -> Snowflake Iceberg architecture. We have observed that datetime values are stored with millisecond precision (3 digits), for example: 2025-05-03 08:09:34.301 However, downstream systems like Snowflake Iceberg require microsecond precision (6 digits), such as: 2025-05-03 08:09:34.301000 This mismatch leads to compatibility issues when reading Fabric-generated Parquet files in Iceberg tables. Current behavior: Fabric stores datetime values with millisecond precision (scale 3), and there is no built-in way to enforce or convert to microsecond precision. Expected behavior: Fabric should support configurable datetime precision (e.g., 3, 6 digits) or automatically pad milliseconds to microseconds when required, ensuring compatibility with downstream systems like Iceberg. Impact: This is a critical blocker for integrating Fabric Lakehouse with modern data platforms like Snowflake Iceberg and affects enterprise adoption of Fabric in production environments.     ... View more