The Deployment Pipeline Compare function is very useful to highlight differences between objects in the various deployment stages.  But it would be useful to have an option to not identify objects as different if the only difference is in a schedule.  It would be common for an object to have a schedule in a Production stage but not in others, or to have different schedules in different stages.  If those are the only differences it would be nice for an option to not identify those objects as different in the stages. ... View more

The detection data type on the Power Query Editor for data flows, and the transformation data on the Power BI Desktop, don't account for all data when column profiling is set to the entire data set. It is problematic. It introduces refresh errors because it doesn't use distinct column values to ascertain the data type it should be. ... View more

I can't be the only one who can't stand using this thing with all the panes on the right. It's always panes on the left, visual studio, SQL, File explorer, Windows settings just to name a few I use each day. Let us rearange this stuff it's insanely annoying. Consider my OCD triggered. ... View more

“When a user accesses a report via a shared URL (using the Share button), they are unable to create a Usage metrics report, even if they hold an Admin, Member, or Contributor role in the workspace.” Please check there is "Usage metrics report "option.   Please make that Admin, Member, or Contributor role user can create Usage metrics report no matter in what way they open report.   ... View more

I am using multiple Excel and CSV files as data sources, and when I try to refresh my report, I get the following error message which doesn't specify which file it refers to: Data source error: DataFormat.Error: We were unable to load this Excel file because we couldn't understand its format. File contains corrupted data.. Microsoft.Data.Mashup.ErrorCode = 10942. ;We were unable to load this Excel file because we couldn't understand its format. File contains corrupted data.. The exception was raised by the IDbCommand interface. After checking all files, I found that they all have regular extensions (.csv or .xlsx), which doesn't match the error description. It would be helpful if the error message could specify which file is causing the problem.   ... View more

Es ist momentan in PowerBI nicht möglich einzelne Tabellenwerte, unter der Funktion "Bedingte Formatierung", in den üblichen Windows-Schriftschnitten (Fett, Kursiv und Unterstrichen) zu formatieren. Dabei würde sich nach meiner Meinung die Funktion im  Bereich 1 oder Bereich 2 sehr hilfreich machen, um wichtige Tabellenwerte nochmal hervorzuheben: ... View more

It would be very useful if “About the report” pages in Power BI could automatically adjust their dimensions based on the content included. Currently, these pages have a fixed size, which limits their use for technical documentation, institutional messages, or more extensive visual explanations. ... View more

Es wäre hilfreich bei der Veröffentlichung eines PowerBI-Berichts nach der Auswahl des Arbeitsbereichs in den Folgedialogen, diesen Arbeitsbereich auch namentlich mitzuführen. Wenn man mehrere Arbeitsbereiche hat, in denen dieser Bericht veröffentlicht werden soll, verliert man sehr schnell den Überblick.   ... View more

Current situation: When you start viewing previews of your table in SQL Database, you will only see part of the column names, Values and also the preview mouseovers in a cut-off mode and are not able to adjust the windth an the values:     Future Situation: You're able to adjust the width of the column via drag & drop or even adjust it to the max-width of the values with a double click. Values will be displayed with their full length instead of being cut off.   ... View more

Feature Request: Two UI enhancements to improve readability and workspace in Power Query While working with medium to large datasets in Power Query, the available screen space becomes very limited, especially when dealing with many columns. I would like to propose two UI improvements that will give users more control and make data transformation easier and more comfortable.   1. Option to Move/Shift the Query Settings Pane to the Left Side (or Dock Anywhere) The Query Settings pane currently appears fixed on the right side. When working on smaller screens or with wide tables, the right-side pane occupies valuable horizontal space.   Suggested Enhancement: Allow users to dock the Query Settings pane on the left side, similar to how the Queries pane is docked. Even better, allow a drag-and-drop, customizable docking system (left, right, bottom, or floating window). This will help users who prefer to keep important panes together and free up more room for the data preview.   Benefits: More intuitive layout (Queries + Query Settings on the same side). Less horizontal scroll when working with wide datasets. Improved ergonomics and workflow efficiency. 2. Provide a “Maximize Data Preview” or “Full-Width Table View” Mode When working with many columns, the data preview area becomes too narrow.   Suggested Enhancement: Add an option such as “Maximize Data Preview”, which temporarily hides: Queries pane Query Settings pane Ribbon (optional toggle) Or provide a single-click “Expand Table View” button that gives more horizontal reading space.   Benefits: Cleaner, distraction-free data view. Easier to inspect, clean, and transform wide tables. Reduces excessive horizontal scrolling. Greatly improves usability on laptops and smaller monitors.   Why This Matters Both enhancements will significantly help analysts and developers who: Work with datasets having 20+ columns Build complex transformations Use Power Query daily in Power BI, Excel, or Fabric These changes will improve productivity, reduce frustration, and enhance the overall user experience.   ... View more

Hi Team, As a Fabric user working with Direct Lake semantic models (created via lakehouse SQL endpoints or OneLake), I've encountered significant challenges in backing up, copying, or migrating these models. The process is restricted and complicated compared to Import mode datasets: Backups require XMLA endpoints, Tabular Editor, or custom scripts (e.g., Semantic Link Labs), with limitations in free tiers or during live edits. Converting between Direct Lake modes (SQL vs. OneLake) involves manual TMDL edits in Power BI Desktop, risking errors. Recreating underlying lakehouse tables often leads to loss of complex measures (e.g., MTD, YTD, dynamic year-over-year comparisons), forcing full rebuilds, especially painful in production with 100+ reports. This results in high rework, time, and effort.   Proposed Improvements: Built-in "Export/Import" or "Clone" button for semantic models in the Fabric UI, supporting Direct Lake modes without XMLA setup. Auto-backup or "snapshot" feature before lakehouse changes, preserving measures/relationships even if tables are recreated (e.g., decouple measures from table IDs). Enhanced version history with unlimited versions, easy restores, and integration for measures only. Simplified migration wizard between Direct Lake on SQL and OneLake, with schema validation. This would greatly ease management for enterprise users, reducing downtime and errors. Similar to Power BI's PBIX exports but optimized for Fabric's lake-centric architecture.   Use Case: Production environments with dynamic reports relying on complex DAX measures over large Delta tables.   Looking forward to community votes and Microsoft response!   ... View more

I have 635 tables (each as it's own query) to peruse, and not being able to sort the "queries" in the "Power BI transform data" view is quite honestly barbaric.  ... View more

The Copilot Narrative visual is extremely helpful for summarizing trends and qualitative data, but the footnote citations are not always necessary or helpful. I currently solve this by adding "do not use footnotes" to the end of my prompt, but it would be better to have a toggle switch where I could turn them off with a single click. ... View more

When creating a Row Level Security Rule, it is limited to one table.   When working with a dimensional model, and I want to apply RLS to dimensions, this works. When the data is later joined to fact tables, the RLS is used. But, when a user connects to just the fact table, the RLS on the dimensional tables is ignored. This opens a possibility to see more information than intended.   So, the idea is to allow for joins between tables in the RLS constructs, enforcing the security on a broader level ... View more

When creating column-level security on a table, these columns are no longer usable for users in the group with this limitation.   However, when running a SELECT * statement, the error reveals the ' hidden' columns. The default SELECT TOP 100 rows error occurs for the same reason. When you click on the table, it shows an error, but no really understandable message.   I would suggest a code change that detects the column-level security and automatically applies it to the user, preventing this user from ever gaining any knowledge of the hidden columns. ... View more

Seriously only the dataflow owner can get failure notifications now? We are a company of a lot of engineers and this is a team business. We work in teams and when something fails I'd like the team to get the notifications so we call jump on fixing it immediately and not have to wait for the owner to say something. this should not be a new idea this is a bug, you took away valuable funcationality! please put it back. ... View more

The Fabric Map item was released in preview in Q3 of 2025. One of the things we've noticed, is that custom coloring of shapes is not possible. Currently only data themes supplied by Microsoft can be choosen. We want to be able to add colors to the GeoJSON shape properties and be able to assign these colors as shape coloring, ovewriting a selected data theme. This can be fill colors, outline colors, text colors, etc.   The colors of the provinces in the map below are now defined by the Data theme.   In the data layer settings un Polygon settings, there should be possibilities to assign properties to shape colors. Or there should be section "Color settings".   Check the community discussion here. Thanks @akaplan1-slcc for asking a question about this. ... View more

As a distribution mechanism apps are great, but when the items they contain become large in number finding the right item(s) can be difficult. Being able to find the right item within an app is vitally important, and descriptions are an easy way to achieve this.   The implemention may be different between org apps and workspace apps. For example, a tooltip may be used in a workspace app, whereas the description field could be added to the org app interface.   This is also relevant to this idea: https://community.fabric.microsoft.com/t5/Fabric-Ideas/add-Description-field-to-workspace-listing-view/idi-p/4790296 ... View more

Hello! I would like to suggest to enable the identation in the Advaced Editor in Dataflow construction. Every time I close and open, all the spaces in each line are supressed.   Thanks! ... View more