Currently if you have a lot of elements on a dashboard and you want a slicer to only impact some of them, you have to manually go through and turn off the interaction with everything else. This can be very time consuming. What would be great is if there was an option within the edit interactions to turn it off for everything at once. This would mean that rather than having to turning the interaction off for everything manualy, you could quickly turn it off for everything then select just the ones you want it to interact with.   Just to be clear, I'm not suggesting the default be changed, only to have an additional functionality to make it quicker if you only want a particular slicer to impact a small number of elements on the page ... View more

I would like to have more control over which queries are sent to a particular custom sql pool in the warehouse experience. As things exist now, only application name can be used to filter queries between custom sql pools. Have the option to create tags to identify queries/workloads would be a nice feature.  I could then prioritize Central-to-whole-business Reporting queries from Power BI versus departmental reporting queries. As things stand now, both would just be classified as application name.  ... View more

When using visuals such as clustered column charts or column charts, adding a legend automatically assigns a different color to each item, but there are cases where I want all the colors to be the same. Currently, it is not possible to change all colors at once, and I have to select a color for each item individually. I would like to be able to change the colors of multiple items at the same time. ... View more

When working in the Fabric Developer experience (experience=fabric-developer), navigation should consistently preserve this experience across all pages and links. Today, many internal links redirect users back to experience=power-bi, which breaks context and requires manual switching back to the Fabric Developer experience. This is especially noticeable in Monitor, but also occurs in other areas.   Requested behavior: Automatically retain the active experience when navigating within Fabric, or Provide a user-level preference to set a default experience (e.g., always open links in Fabric Developer). Persisting the selected experience would significantly reduce friction, avoid repetitive context switching, and improve overall developer productivity.   ... View more

Problem: The Fabric Monitoring Hub (https://app.powerbi.com/monitoringhub?experience=fabric-developer) does not expose its filter or sort state (e.g., workspace, item type, status, time range, start time sorting) via URL parameters. As a result, it is not possible to save or share filtered and sorted views using browser bookmarks or links.   Request: Expose both filter selections and sorting options in the Monitoring Hub as URL query parameters     Benefits:  Ability to save bookmarks for commonly used operational views. Share direct links that open Monitoring Hub in a predefined filtered and sorted state. Improve on‑call / operations workflows. Reduce repetitive manual filtering and sorting.   Example (conceptual): https://app.powerbi.com/monitoringhub? experience=fabric-developer &workspace=PROD &itemType=Pipeline &status=Failed &timeRange=Last24Hours   Expected Behavior: Opening a bookmarked URL loads the Monitoring Hub with the specified filters applied and results sorted by Start Time. ... View more

Problem Fabric pipeline failure notification emails should clearly include the Workspace name in both the email subject and body.   Today, these emails contain the pipeline name and technical details but do not specify the workspace, making it difficult to quickly assess urgency - especially when viewing the notification on a mobile device.   Proposed Improvement Including the workspace name (for example: Prod / Test / Dev) would allow developers and operators to immediately understand whether the failure is business‑critical or lower priority.   Why This Matters Faster triage directly from the email reduces response time for production incidents. ... View more

Introduce tenant setting capabilities that allow controlled exceptions to centrally enforced tenant‑level policies (such as Allow non‑Entra ID authentication in Eventstream or Block Public Internet Access), enabling governance‑approved deviations by domain or workspace without requiring full tenant‑wide enablement. ... View more

I suggest allowing users to filter by columns that are present in the underlying source table used for configuring 'Verified Answers' within the 'Prepare data for AI' section of semantic models. For example: the source table have collumns: - country - sales_representative - fit_score (business metric)   If I set an verified answer like: 'Please rank the top performers sales representatives for last quarter' it works just fine. But if I add one aditional when I am using copilot to verify the outputs it doesnt work 'Please rank the top performers sales representatives for last quarter for Finland' We added the for Finland to filter specific country.   Please investigate how to allow end users to use it, right now the viable solution would be seting up one question per country which is very demanding. ... View more

Stop releasing garbage software that doesn't work and breaks constantly, just an idea ... View more

Currently, I am not able to use STRING_AGG and/or JSON_AGG in Scalar UDFs in Fabric Warehouse and SQL anlalytics endpoint. I would like to be able to do that w/o needing to do a code change. We need more votes to understand importance of this requirement. Please describe your exact scenario(s). ... View more

Purview + Fabric Warehouse ≠ enterprise‑ready governance. In our environment, the Fabric Warehouse is the system of record, but Purview can only catalog the warehouse container—not the tables or columns that actually matter for governance. That makes Purview unusable for core enterprise requirements: business glossary mapping, data products, stewardship, discoverability, and trustworthy AI/Copilot grounding. Microsoft’s message is effectively “go redesign your architecture around Lakehouse,” which is unacceptable: we will not duplicate, mirror, or re‑platform our data just to make governance work. Until Purview supports sub‑item metadata scanning for Fabric Warehouses (tables + columns), Purview is not fit for purpose in a Fabric‑first enterprise—and we will drop it. This gap directly contradicts the “single, integrated SaaS framework” promise of Unified Catalog for governance in the AI era. ... View more

If would be nice to disable drill capabilities for a page; either in the canvas properties or URL parameter (similar to &pageName or &authAuth) ... View more

Hi Team,   The code below does not find any files.  However, if I replace 'S&P-2013' with 'test' and move over a single test file, it works fine. I am pretty sure this is a bug since it is a allowable path name in ADLS.   Sincerely,   John Miner   PS:  The new statement aligns with other vendors such as SNOWFLAKE.  I wish there was a way to place the secret into a vault and reference the vault instead of hard coding a SAS key that could be an attack vector.    https://docs.snowflake.com/en/sql-reference/sql/copy-into-location    -- -- Load table - all years --   COPY INTO [stocks].[snp500] FROM   "https://sa4adls2030.dfs.core.windows.net/raw/stocks/S&P-2013/*.CSV" , WITH (     FILE_TYPE = 'CSV',     CREDENTIAL=(IDENTITY= 'Storage Account Key', SECRET='<skipped>'),     FIELDQUOTE = '"',     FIELDTERMINATOR=',',     ROWTERMINATOR='0x0A',     ENCODING = 'UTF8',     FIRSTROW = 2 ) ... View more

There doesn't appear to be an easy way to set a default value for Slicers following a data refresh, which is possible in Reporting Services report parameters.   For example, if I have a Slicer that lists Dates in descending order (with the latest date at the top), when I refresh the data I would like the report to always select the latest date, regardless of what that is. Without this, the report always defaults to whatever value was selected when the report was published and users have to change it to the most recent date themselves, which is not a great user experience.    This could be done via a variable Visualisation option (e.g. provide a default value via a DAX measure), or simply an option to 'Select top value after refresh' ... View more

when you have a slicer as a drop down, the list is set to the width of the slicer, if the drop down list could expand or text wrap the values (or an option for both) as you interact with it, it would make selections easier for then there are wide lists of values. ... View more

When I get error in I can't find which query has the error, that was existing already at the last year. ... View more

when i open up my power bi i get a black dos prompt looking that with sqldump.exe error march edition ... View more

When setting a Default Destination inside Gen2 Dataflows, it would be nice to have schema support rather than everything going to dbo. ... View more

I would like to report a bug in Microsoft Fabric's Copy Activity when the source is an empty Delta table in a Lakehouse. **Environment:** - Service: Microsoft Fabric - Activity: Copy Activity - Source: Lakehouse Delta Table - Destination: Fabric Warehouse Table **Issue Description:** When the source Delta table is empty (0 records), the Copy Activity fails with the following error: ErrorCode=UserErrorFileNotFound Message: ADLS Gen2 operation failed: Operation returned an invalid status code 'NotFound'. ErrorCode: 'PathNotFound' - The specified path does not exist. Path references an internal Staging path: 'MSSQLImportCommand' **Steps to Reproduce:** 1. Create a Copy Activity in Fabric Pipeline 2. Set Source to a Lakehouse Delta Table that is empty (0 records) 3. Set Destination to a Fabric Warehouse Table 4. Run the pipeline **Expected Behavior:** The Copy Activity should complete successfully with 0 rows copied, similar to how it behaves in Azure Data Factory. **Actual Behavior:** The Copy Activity fails with PathNotFound error related to an internal staging path that is not created when the source is empty. **Impact:** This forces users to implement workarounds (e.g., Spark Notebook checks before Copy Activity) to avoid pipeline failures, adding unnecessary overhead and latency to data pipelines. **Additional Notes:** - The issue does not occur when the Delta table contains data - The staging linked service cannot be manually configured in Fabric Copy Activity (unlike ADF), so there is no workaround within the activity itself Please advise on a fix or official workaround. Thank you. ... View more