Hi Microsoft Team, I'm trying to activate Microsoft Fabric for my account kwagle@procareer.ai, but I’m receiving the message:"We cannot assign you a free Microsoft Fabric trial capacity due to an error." The support page says I need to wait 60 days, but I urgently need access to Fabric for hands-on learning as I’m preparing for the DP-700 certification. This account is part of a legitimate startup domain and hasn't used any Microsoft product trials previously. Could you please manually enable Fabric trial access for this email or guide me on how to get it activated sooner? Appreciate your support in helping independent learners and startup professionals explore Microsoft Fabric.   Cheers, K**bleep**ij ... View more

Background We’re building an end‑to‑end ingestion pipeline entirely within a Microsoft Fabric Lakehouse Notebook. Our source is an AWS‑hosted Delta Share, and our target is OneLake staging (schema raw) followed by loads into a Fabric Warehouse. What We’ve Tried Delta‑Sharing Spark Connector (delta-sharing-spark_2.12:0.14.0 via %%configure spark.jars.packages) Delta Sharing Python client (delta-sharing PyPI package, v1.1+) REST + spark.read.parquet() fallback via pre‑signed file URLs All of these approaches work for simple Delta tables, but they fail on tables that use the Deletion Vectors feature (delta.enableDeletionVectors = true). Error Messages REST Read → HTTP 400 with DS_UNSUPPORTED_DELTA_TABLE_FEATURES: Table features delta.enableDeletionVectors are found in table version: … Delta Sharing Connector → session crashes with ClassNotFound for deltaSharing format unless a JAR is attached (which Fabric does not allow) Direct Spark → unable to interpret deletion vectors, causing read failures Fabric Limitations Identified Cannot attach external JARs or use spark.jars.packages in Lakehouse Notebooks reliably Does not support Delta Sharing REST’s "responseFormat":"delta" mode, which is required for Deletion Vectors Spark runtime in Fabric Lakehouse cannot interpret Deletion Vectors metadata in Parquet files Why We Can’t Work Around on Our Side The provider is unable/unwilling to disable Deletion Vectors or rewrite tables. Fabric’s current Spark runtime lacks the downstream capability to read DV‑enabled tables. We have no administrative access to modify the platform’s classpath or install custom connectors.  Requested Enhancements for Fabric Engineering Enable external Spark JARs in Lakehouse Notebooks (or at least allow the Delta‑Sharing connector JAR) Support the Delta REST API’s “delta” responseFormat, including Deletion Vectors, in spark.read.format("deltaSharing") or via REST+Parquet fallback Upgrade the Fabric Spark runtime to a Delta library version (3.x+) that natively understands Deletion Vectors Impact: Adding support for Deletion Vectors in Fabric would unlock seamless ingestion of modern Delta tables—without requiring table rewrites—enabling Fabric users to consume advanced Delta features and maintain performance/efficiency on deletes and updates. Thank you for considering these enhancements. We’d be happy to provide additional logs, reproduce steps, or collaborate on testing once support for these scenarios is available. Thanks! ... View more

To Whom It May Concern: This June, Databricks introduced the Databricks Free Edition—a no-cost offering targeted at students, educators, technologists, and enthusiasts looking to explore data and AI. It’s a smart, inclusive move that builds long-term loyalty and broadens the Databricks user base at every level of expertise. By contrast, Microsoft Fabric currently only offers a time-limited Free Trial based on the F64 SKU. While this may seem generous, it’s functionally impractical. The F64 SKU is not a realistic production option for most small or midsize organizations. These teams need to validate their workloads and test real usage scenarios, but the F64 trial is disconnected from the environments they'd actually deploy. I’ve run a POC through it myself, and the metrics I obtained weren’t actionable because the SKU didn’t match our operating realities. Software time-limited trials are synonymous with early-stage startups trying to spur fast conversions. Microsoft, however, is a company with global reach, deep enterprise credibility, and a reputation for empowering customers. It shouldn’t rely solely on free trials with expiration dates—it should offer a true Microsoft Fabric Free Edition. One that mirrors the Databricks model and gives users the flexibility, time, and resource-appropriate scale they need to confidently test and evaluate the platform. In a AI competitive landscape, accessibility is adoption. A Fabric Free Edition would ensure organizations have the freedom to plan thoughtfully, assess realistically, and migrate with confidence. CTA - Vote for this Idea which would empower Microsoft Fabric to build long-term loyalty and broaden adoption and user base at every level of expertise.  Thanks! ... View more

Feedback: Scrollbar Visibility & Misclick Issues: In Power BI Desktop, scrollbars (especially in Format and Data panes) are hard to detect — there's no opacity gradient or contrast that hints at scrollability. Often, while working, I accidentally click on fields or properties instead of scrolling, which is very frustrating. Compare this with Gmail’s scrollbar, which is clean, visible, and easy to click. Microsoft should add a fade effect (like in Fabric Community) or a clear scrollbar line with contrast so users can easily grab it without dragging the touchpad every time. Text Box Movement is Too Difficult: Moving a text box in Power BI feels like rocket science. The user is forced to click precisely on the border to move it — there’s no cursor change, no drag support from the center, and no "Move" option in the menu. Suggested improvements: Allow dragging by clicking anywhere inside the text box. Change the cursor to a "move" hand icon on hover. Add a "Move" option in the right-click or "More options" menu. Hover-Based Visual Usage Suggestions: Power BI visuals don’t guide the user much during selection. If a user hovers over a visual icon, it should show a quick tooltip or smart tip like: “Best for Region-wise trend analysis” for Map visuals “Best for Category comparison” for Donut chart “Use for time-series trend” for Line chart, etc. This would save time, especially for new users, and also help users choose visuals more confidently without trial and error. It’s a small but powerful usability enhancement. Thank you. Have a great day. ... View more

Hello Power BI Team, I am experiencing a recurring visual bug in Power BI Desktop version 2.145.1105.0 (July 2025). The issue occurs both in the Microsoft Store version and the .exe installer version. Issue Description: Whenever I delete any visual (such as a chart or card) and then switch to another page in the report, all visuals on the new page temporarily disappear — as if they were deleted. However, the visuals are still there and reappear after saving and reopening the file. This does not affect the data or report structure, but it creates confusion and significantly impacts the report editing experience, forcing me to save and reopen constantly. What I've already tried: Full reinstall (both Store and .exe versions); Cleared Power BI cache; Updated display drivers; Tweaked DPI and display optimizations; Attempted to disable GPU acceleration (not available in UI or config files); Tested on multiple reports and machines with the same result. Suggestion: This behavior appears to be a rendering or caching issue. It would be very helpful to bring back the option to disable hardware graphics acceleration, or provide an equivalent setting in the advanced options. Thank you in advance for your support. I’m available to provide any additional information or diagnostics if needed. Best regards, David Marques ... View more

Recently I had a data type cause a failure when refreshing data. I recieved the error message:  "DIM_INSURANCE_PLAN OLE DB or ODBC error: Type mismatch. (Exception from HRESULT: 0x80020005 (DISP_E_TYPEMISMATCH))". If it is able to tell me there was a type mismatch error on a field, why can it not tell me what field the error is occuring on? I spent a considerable amount of time researching/comparing the data types manually. If the error is already known, why can the error message not be specific to where the error is occuring? It would be much more user friendly and save time.  ... View more

Good day, I would like to suggest a feature enhancement for Power BI. It would be very helpful to have filtering capabilities within the "Manage Relationships" view — specifically, the ability to search by keywords and filter by tables involved in a given relationship. This would greatly simplify the analysis and navigation of complex semantic models that include many related tables. Thank you for considering this improvement. ... View more

While I appreciate Microsoft's commitment to security and stability in Power BI, there are scenarios—particularly in enterprise environments or when working with custom architectures—where the strict enforcement of dynamic data source restrictions can hinder development and innovation. I propose introducing a configurable warning system that alerts users to potential risks but also allows experienced developers to bypass the dynamic data source error when appropriate. This would strike a balance between maintaining security and enabling flexibility for advanced use cases. ... View more

The column remapping UI in a copyjob is impossibly small.  On a 1080p monitor (the only ones I have) the display space isn't big enough for one complete row to display.  Compounding this, the verticle scroll bar arrows do not scroll one row at a time, but instead some other fixed amount.  Often this means that I can only see a sliver of the row that I need to work on.   ... View more

Hello,   Until recently, the standard behaviour of formatting priority for the various formatting levels/groups within the JSON theme file was straightforward, and presented as below (where the view is top-down in reverse order of priority, so that each step down overrides any settings that came previously where applicable): With the addition of style presets, it was hoped this same logic would be in place, so that (where applicable) global values could be leveraged in conjunction with style presets, to minimize code and keep the theme file as lean as possible as per best/standard practice. In this way, the same flow (again top-down in reverse order of priority, so that each step down overrides any settings that came previously where applicable) would be in place, only with the added benefit of being able to choose either 'standard formatting' or style preset at the 'per visual/object type' level, as shown:   However, its currently 'expected behaviour' that the Style presets do not work consistently with global values (wildcards), and instead where conflicts exist the option is to either remove the global value in question (& replicate per visual where required instead) if using a style preset that references the same value, or not utilize that particular style preset. Otherwise, if the conflict is left in place, upon application of the theme the preferred 'default style preset' is not properly inherited when first applying a JSON theme file, leading to various visual errors and glitches (the workaround is to manually select the 'core/native default preset', and then reselect the preferred default). This renders the theme application process counterintuitive and creates too much work for end users at scale (hundreds of reports representing thousands of report pages etc.)   Also, for a complex/detailed JSON theme file, the current 'fix/alignment with expected behavior' means spending a great deal of time undoing the best practice of avoiding code repetition etc., if so much as one visual utilizes a style preset that in turn references a value applied to every other item via global values.   As such, the feature request/idea is that the flow/logic/heirarchy suggested in the second diagram be implemented in the theme file/PBI logic going forward, allowing theme authors to leverage the best of both worlds (global formatting and style presets), rather than being forced to choose. ... View more

When a Gen2 dataflow fails in Fabric, the Power Query editor provides no in-context error details. You must exit the editor and open the “Recent Runs” pane to see diagnostics—interrupting your workflow. Please surface run errors (messages and logs) directly within the Power Query interface so users can troubleshoot without leaving the editor.   Diagnostic information in the "Recent Runs" window is like hanging a toilet paper roll holder in the garage instead of the bathroom.  Maybe kind of nice, but it's not where I do my business.       ... View more

I'm working with a security-first organization and the dependency on the internet for querying Fabric data is a concern. I initially thought that Private Link is available to Fabric, and it is, but the ability to assign a private IP address to a Fabric Lakehouse or Warehouse is not. I don't see this on the roadmap at https://aka.ms/fabricroadmap, but I really think it should be.   Thanks,   Philip ... View more

Business Justification: Tableau has an inbuilt functionality of ‘underlying data export’ at visual level. This is a very useful feature for many users across the organization as they can analyze specific data that was used to calculate a measure or get details on any data point in question. In PowerBI, many users without pro license can also benefit from this feature as they will not have any other way to analyze actual dataset, if need be ... View more

The selected theme is applied to all the pages in the book, but there is no option to apply it to only the current page. It would be great to include an option to apply a theme either to a selected page or to the entire book.     On the Fabric Idea page, I can see a lot of ideas. If I want to check whether someone has already submitted an idea similar to mine, there is no option to search through all the existing ideas. All the ideas are listed on the page, but I don't want to go through each one manually. I would suggest adding a search option so users can quickly check if their idea has already been submitted. ... View more

In Power BI reports that include integrated Power Apps visuals, the deployment pipeline currently updates the dataset connection from test to production environments seamlessly. However, the Power Apps visual does not follow this transition — it remains linked to the original (test) environment and requires manual reconfiguration after each deployment. This creates friction in the deployment process and increases the risk of errors or inconsistencies between environments. Request: Please enhance the deployment pipeline to support automatic environment switching for embedded Power Apps visuals, similar to how dataset connections are handled. This would greatly improve CI/CD workflows and reduce manual overhead for enterprise deployments. ... View more

Hello,   a system variable that contains the timestamp of the schedule (not the actual fired time) would be very useful. Currently, workarounds are needed to store this timestamp. In a data warehouse (lakehouse) environment, this information is very helpful. Example: A Pipeline is scheduled two times a day: 1430 and 2330 This timestamp would be useful as a variable. (At least i could not find it) ... View more

When developing tables in PQ, it's helpful to see columns in a particular order. It's annoying to have to drag...and drag...and drag columns to get them reordered, and tedious at best if you do it in M. (And yes, those steps get removed before going into prod.)   Please add a "Reorder column" option to the the "Choose columns" command options. This would use the same basic dialog as the "Choose columns" command, but would let you drag the column names up or down or have up/down arrows in it. Smaller real estate to drag and faster response because it wouldn't be happening "live," but after you click ok. ... View more

When updating a fact table, particularly when field headers change due to modifications upstream, any dependent measures or calculated columns that reference those now-missing fields can result in errors. Currently, Power BI only displays these errors at the individual measure or column level, requiring users to manually open each folder to identify broken items. It would be highly beneficial to introduce an error indicator at the folder level within the Fields pane, allowing users to quickly see which folders contain errors and efficiently identify and resolve issues caused by schema changes. ... View more

Currently, Power BI does not support manual line breaks in column headers for Table and Matrix visuals. Attempts to insert line breaks using ALT + ENTER, UNICHAR(10), or other newline characters are ignored. This limits the ability to format headers efficiently, especially when trying to save horizontal screen space or improve readability in compact layouts.   Suggested Improvement: Enable support for manual line breaks in column headers, either through: Recognizing ALT + ENTER during column renaming Supporting UNICHAR(10) or similar in DAX expressions used as headers Providing a formatting option in the visual settings to insert line breaks This feature would greatly enhance layout flexibility and improve the user experience when designing reports with limited space. ... View more