The show tables spark function should be lakehouse aware.  If it is without a schema, then search the root of the catalog.  If it has the schemas option enabled, then default to the "dbo" schema.  Otherwise, allow a "schema name" to be passed as an option.   A work around for now is the mssparkutils.fs.ls("Tables/Schema").  Then filter by any folder names only, these are the table directories.         Here is a screen shot for a schema less Fabric Lakehouse that works as expected.     Please fix this bug!   ... View more

Semantic modelling is fundamentally important to provide context to data, however AI tools are able to build out designs much quicker than report developers.   I think the report designer of Power BI / Fabric could largely be replaced by a prompt mechanism where a user can detail which measures / dimension fields are important, add a brand guideline file (fonts are currently very limited in PBI, so even more UI customisation could also greatly enhance the product) and the AI creates the visualisations based on Gestalt principles etc.   A user can then edit the layout, but having the AI make the first attempt could be a real time saver. Ongoing prompts to modify the report design for features that are currently onerous (e.g. layering) would also be great. ... View more

Add filter for items with errors.       ... View more

When editing an Import mode semantic model in the Power BI service, the Refresh operation always runs an "Autodetect relationships" step at the end — even when the source .pbix has both "Autodetect new relationships after data is loaded" and "Update or delete relationships when refreshing data" disabled under Current File > Data Load options.   These per-file settings are intentionally turned off for models with complex or carefully managed relationship structures, but the web editor appears to ignore them entirely.   Expected behavior: The web editor should respect the Data Load settings already defined in the semantic model metadata. Ideally, these settings would also be exposed in the web editing experience so they can be viewed and modified without needing to download to Desktop.   Current behavior: Autodetect relationships runs on every refresh in the web editor regardless of the existing setting. This adds unnecessary processing time (especially on capacity-constrained Fabric workspaces with large models) and risks creating unintended relationships.   Workaround: None in the web editor. The only option is to monitor for unwanted relationships after each refresh. This is documented as a known gap — the Microsoft docs state that "Data Load settings defined in the Options dialog in Power BI Desktop aren't available for viewing or modification in the web experience" — but the expectation is that existing settings should still be honored even if they aren't yet editable in the browser. ... View more

Situation: Source table has rows.  The copy produced an error.  No rows copied.  Copy Job reports Success despite the error causing none of the rows to be copied.  This should be a status other than “Succeeded”.  It would also be helpful to allow sorting by the column header (Status, Rows read, Rows written, etc.) Also, it would be great if we could pause the constant refreshing of the Results, so we can actually look at the results.   The link for troubleshooting Error 1000 contains no info on Error 1000. https://learn.microsoft.com/en-us/fabric/data-factory/connector-troubleshoot-overview#error-code-1000     ... View more

IMHO, the filter options should match all of the possible statuses.  There is no filter option for "Not Started".  The Incactive filter does NOT show items with a status of Not Started.  Also, it would be nice if there was a quicklink to check all the boxes. Why?  Because I would like to look at all of the items that are other than Succeeded.  With a quicklink to check all of the boxes, I just select the quicklink and then UNselect Succeeded Also, it would be nice if changes to the Column Options would work while the job is running.     ... View more

Make a native feature that allows you to change the settings in your desktop environment to default to a specified Display Unitys Type.  I spend a lot of time changing from auto to other units.  ... View more

I swap back and forth between Fabric and regular PowerBI workspaces. I get hit by this multiple times a day. Please move the 'Workspaces' menu item to the same place between the two platforms, right under 'Home'. Y'all even faked me out with that 'Browse' item on the PowerBI page as the 2nd item until I un-pinned it.   I am begging you. ... View more

Please Don't remove Q&A features. This helping more for all data analysis work easily.  ... View more

When looking up a filter on a filter pane using the search bar, currently there is no indication to which level (visual, page, report) the filter belongs. This often causes confusion for users.   A proposed solution would be to still display "Filters on this visual"/ "Filters on this page"/ "Filters on all pages" while filtering matching fields. Other options, like small icon/ diferent coloring/ shading would be welcome as well.  ... View more

We have started working using PBIP and Git integrations recently. It's been helpful but what's frustrating is the long list of Diffs we see on TMDL files where the relationships / measures being reordered even though the developer has not touched these measures. this is causing a lot of strain reviewing pull requests.  ... View more

The new report creation experience in PBIP / Git integration world is convoluted.  we should just be able to create a new report in powerbi deskto and choose a semantic model in our git repository.   the current process is convoluted which requires us to create a report using live connection - publish and then the pbir definition file getting updated with bypath reference ... View more

Power BI currently supports data-driven repetition only at the single-visual level (small multiples). There should be native support for data-bound visual containers, allowing a group of visuals to be repeated by a categorical field, with support for nesting, adaptive layout, and isolated filter context. This would enable reusable, scalable report patterns and align naturally with PBIP and CI/CD workflows. ... View more

Power BI and Microsoft Fabric currently do not offer a tenant‑level or portal‑wide banner capability that allows administrators to proactively notify all users when data is stale, delayed, or impacted by upstream system failures. In real‑world enterprise environments, pipelines, dataflows, and semantic models frequently depend on external source systems. When these sources are unavailable or delayed, reports may continue to load successfully but display outdated data, creating a silent failure scenario. Users have no visible indication that the information they are viewing may not be reliable. Today, administrators lack a centralized, in‑product mechanism to communicate these conditions to all users at the moment they access Power BI / Fabric. ... View more

Pipeline schedules should not have an end date by default.   The current 1-year default end date introduces a hidden failure mode where pipelines silently stop running.   Most pipelines are intended to run indefinitely, so this default creates unnecessary operational risk and maintenance overhead.   Removing the default end date would make scheduling more reliable and predictable, while avoiding unexpected disruptions. ... View more

There is a notification that gets sent out automatically when an Email Subscription to a report is about to expire. The suggestion here is to have an option to customize when this email goes out and how often this will get sent. For example, if the subscription is ending in 30 days, the ask would to be able to set up notification emails that go out 15 days before the subscription ends. Basically, just able to customize the time and frequency of these notifications. This will help control the subscription process more thoroughly.   ... View more

When exporting data from Power BI using “Summarized data (.xlsx with live connection)”, the resulting Excel file does not inherit the sensitivity label applied to the dataset or report, even when the tenant setting “Automatically apply sensitivity labels to downstream content” is enabled. This behavior creates a potential data leakage risk, as file‑level protection controls are not enforced on the exported Excel file.   Expected Behavior: Automatically apply the dataset/report sensitivity label to Excel files created using Summarized data (.xlsx with live connection) OR Clearly document and surface warnings in the export UI indicating that this export option does not support sensitivity label inheritance ... View more

Hello Microsoft Team,   Currently, Power Automate offers a trigger for Power BI dataflow refresh completion, but there is no native trigger for Power BI semantic model (dataset) refresh completion. According to community and documentation, this gap forces users to rely either on data‑driven alerts, which cannot detect failure states, or REST API polling, which requires Premium HTTP actions.   Many business workflows depend on knowing whether a dataset refresh succeeded or failed, especially when downstream automation or data quality processes rely on up‑to‑date semantic model data.   I would like to request a new built‑in trigger:  “When a Power BI semantic model (dataset) refresh completes” with outputs such as:   Refresh status (Succeeded / Failed) Error details Start and end time Workspace ID and Dataset ID This would eliminate the need for complex REST API workarounds and significantly improve automation reliability for Power BI + Power Automate users. Thank you. ... View more

Live embedded reports maintain state in PowerPoint. When changes are made to the report (such as adding new slicers), the embedded session may not fully isolate page-level visuals, causing slicers to appear unexpectedly.  ... View more