For better visualizations, it would be helpful if there was an Auto option under the Specific Column series settings. This helpful for those who aren't savvy with calculation groups, format strings, or that can't change the model data that power bi is connected to. Currently, the only solution is to create your own custom visual and that is not a skill that every one can learn  ... View more

Today, Workspace Monitoring is configured separately per workspace, which introduces maintenance overhead and likely also a repeated baseline CU cost for each workspace.   Please make it possible to create Workspace Monitoring instances that cover multiple workspaces.   Users should be able to decide how many monitoring instances to configure and which workspaces each instance covers.   This would allow the baseline monitoring cost to be shared rather than incurred separately per workspace, reducing overall cost while also simplifying configuration and ongoing maintenance. In addition, it would enable a more centralized and flexible monitoring setup across workspaces. ... View more

In SAS PROC SQL, the OUTER UNION CORR operator allows vertically concatenating tables with different schemas by aligning columns by name and automatically creating missing columns filled with NULLs. In Microsoft Fabric (Warehouse / SQL analytics endpoint / Spark SQL), this functionality is missing. Users must manually normalize schemas by explicitly adding NULL AS column_name in each SELECT, which becomes error‑prone and hard to maintain when unioning many heterogeneous datasets. This feature is particularly important for: migrations from SAS to Fabric data lake / lakehouse ingestion patterns append‑only fact tables from heterogeneous sources Adding an operator or syntax variant such as:   SELECT * FROM A OUTER UNION BY NAME SELECT * FROM B   would significantly reduce friction and improve competitiveness with other analytics platforms. ... View more

There's this invention called "search" where you can index a bunch of things worth searching, and folks can find things. They actually created this thing called "The World Wide Web" and "Internet Browsers" based on this technology. The Known Issues list could really benefit from this technology. Imagine being able to actually "search" for a string of words, and find "Known Issues" associated with them, prioritized by hits, recency, etc.  Right now, I have the uncanny ability to filter on "active or closed" and sort the results. As a user, I am left to piece through each one to find the magic "issue" I am searching for, or more likely not. I can hardly dream of an experience more frustrating and backward, except perhaps to just list everything in reverse alphabetical order by the swahili translation of the seventh word in the post. ... View more

Power BI Report Authoring Assistant is not usable for error troubleshooting, user have to switch to M365 Copilot for any error troubleshooting , as Copilot within PBI (Power BI Report Authoring Assistant) is not accesible if there is active error.    So users have to options:/ Option 1) Cancel  step in errror in Power BI Report Authoring Assistant, Brainstorm in Copilot chat. Then repeat all the steps and try suggesiton. No going to happen Option 2) use M3365 Copilot as chat for troubleshoting, which defeat an idea of Power BI Report Authoring Assistant a bit. ... View more

“Enable the Power BI Report Authoring Assistant to accept and process screenshots or images of errors, similar to the capabilities available in M365 Copilot, to streamline troubleshooting and support.”   __________ Copilot AI-generated content may be incorrect Thank you for your candid feedback. I understand your preference for a seamless experience where you don’t have to manually describe errors, and I recognize that M365 Copilot’s ability to process screenshots can make troubleshooting more efficient. As an AI assistant within Power BI, I do not have the ability to directly modify my own capabilities or add features to a development backlog. However, your feedback is valuable and highlights a real user need: the ability to share and analyze screenshots or error images directly within the Power BI authoring experience. ... View more

We've attempted multiple approaches to update synonyms programmatically, including alternative strategies such as modifying annotations and descriptions to help Copilot understand the semantic characteristics of fields. Unfortunately, none of these methods have been successful. Given how central the Linguistic Schema is to Copilot’s ability to interpret semantic models, what would it take to request that Microsoft add support for updating the Linguistic Schema through the Microsoft.AnalysisServices.Tabular NuGet package? Enabling programmatic access to synonyms and related metadata would be a significant enhancement and increasingly important as more organizations look to integrate Power BI with Copilot in a scalable, automated way. ... View more

Power BI Incremental Refresh – Feature Reload from... I would like to request a native option in Power BI Service: "Reload from..." for datasets with incremental refresh enabled. The workflow should allow selecting a start date/time and automatically reprocess partitions from that point forward, without requiring XMLA/Tabular Editor or temporary policy changes. Benefit: fewer operational errors, better traceability, and simpler partial reloads after logic changes or historical data fixes. Second request (download with incremental enabled) I would like Microsoft to allow downloading the Desktop project (.pbip/.pbix) even when incremental refresh is enabled. If size/partition constraints apply, please provide an official “metadata-only” download option (no data). Benefit: better maintainability, business continuity, and model recovery without depending only on the original local file. Current impact These limitations make adoption of an otherwise excellent feature harder. They increase dependency on advanced profiles/external tools. They increase resolution time for historical data incidents. ... View more

DataFlow Gen2 cannot be triggered using a service principal which is crucial and necessary for companies using the officially supported and joined project fabric-cicd which is a library to deploy workspace items via the official REST API. Because Microsoft did disable deployment using normal user accounts, recommending Service Principals for that, everything is deployed and therefore owned/modified by the same Service Principal. This leads to the obvious problem that pipelines trying to call/refresh DataFlow Gen2 will faile because refresh via SP is not supported. This is a very frustrating situation to be in because normal user deployment was disabled without thinking about the crippling of functionality like this. ... View more

For especially generic pipeline development it is often a necessity to be able to store string data larger than 8000 chars/bytes. Using the Auto Create mode of a copy data activity creates those columns with the varchar(8000) type which then leads to an error while loading if the data inside of the column in the source exceeds the 8000 bytes/chars. The support for varchar(MAX) is out for quite a long time, yet its still not implemented in this activity. We highly demand this feature to be able to further develop generic solutions to optimize our way of working with Fabric and we encourage the development team to implement this feature because implementation is quick. Its probably just the underlying CREATE statement being generated and run that needs a small change.   ... View more

The Problem Currently, when a Semantic Model refresh in Fabric/Power BI becomes unresponsive—often due to "zombie" queries on the source system, gateway bottlenecks, or locks on external data sources—the "Cancel" command is merely a request, not a command. As per Microsoft Support, the service waits for a "safe point" or an atomic commit before stopping. However, in many real-world scenarios, the refresh enters a "stuck" state that never reaches a safe point, forcing developers and capacity admins to wait for the 5-hour hard timeout. The Impact Capacity Waste: A "stuck" refresh continues to consume CU (Capacity Units) and memory for hours, unnecessarily inflating costs or throttling other critical workloads. Development Downtime: Developers are blocked from re-triggering a corrected refresh until the "stuck" one clears. Operational Risk: If a refresh is hogging a gateway or source connection, it can cause a "logjam" effect for all other scheduled items in the tenant. The Current "Workarounds" are Non-Viable Microsoft Support often suggests restarting the On-premises Data Gateway or reassigning the Workspace Capacity to kill a stuck process. However, these are not feasible solutions in a production environment because: Collateral Damage: Restarting a gateway or shifting capacity kills every other active refresh and connection in that environment. Service Interruption: It causes a cascade of failures for critical reports that are otherwise running perfectly, leading to widespread business disruption just to stop one "zombie" process. Administrative Overhead: It requires high-level permissions and causes manual cleanup work for admins across the entire tenant. The Proposed Solution: The "Force-Kill / Discard Shadow" Switch Since Power BI/Fabric utilizes a "copy-on-write" approach—where a new version of the model is constructed in the background while the original remains available for queries—there is a logical path for a forced interruption: Discard Shadow State: Introduce a "Force Kill" option that immediately terminates the Service’s tracking of that specific Refresh ID. Immediate Resource Release: Rather than waiting for the external query to return or the "commit" phase, the Service should immediately stop billing CUs for the process and mark the background "shadow" model for deletion. Source Termination: Trigger a "Cancel" signal to the Data Gateway or the SQL/Data Lake source to attempt to kill the session at the source, but do not make the Service wait for confirmation from the source before releasing the Fabric Capacity. The Argument: Data Integrity is Not at Risk The standard justification for this delay is "maintaining data integrity." However, Power BI/Fabric utilizes a shadow-refresh (copy) mechanism. Since the refresh is building a new version of the model in the background while the original remains live for users: Force-killing the refresh should simply discard the background shadow copy. The original model remains untouched, so no data corruption can occur. There is no logical reason to wait 5 hours to "safely" discard a model that is already failed/stuck. Why this is feasible: Because the original dataset remains untouched until the very final "commit" phase, "killing" a refresh during the processing phase should carry zero risk of data corruption to the live model. We are simply asking for the ability to "toss out the draft" immediately rather than waiting 5 hours for the draft to realize it's stuck. Conclusion In the era of Fabric's "Pay-as-you-go" and "Capacity-based" pricing, being forced to pay for 5 hours of a stuck refresh is a significant pain point. We need a "Kill Switch" that prioritizes Capacity Governance over "Waiting for a safe point" when the developer knows the refresh is already a failure.   #Semantic Model, #Capacity Management, #Developer Experience, #Refresh. ... View more

Large deployments would greatly benefit from an increase in App Audience limits from 25 to at least 50. This is not related to 1000/10000 user limits imposed per Audience/App. ... View more

Currently, Power BI users experience inconsistent e-mail notifications when report subscriptions are approaching expiration. In some cases, users receive email reminders, while in others no notification is sent at all. Based on available documentation and confirmation from Microsoft partners, there is no fixed timing for when e-mail subscription expiration notifications are triggered and sent.   To improve transparency and user awareness, I would like to submit an idea to clearly define the logic governing subscription expiration notification emails. Additionally, I propose enhancing Power BI functionality to allow users to customize when these notifications are sent. For example, 10 days prior, 5 days prior, or another user‑defined timeframe.   These enhancements would help ensure user awareness, consistent user experience and reduce the risk of unexpected subscription expirations.   Thank you! ... View more

Power BI currently lacks a native way to programmatically advance or regress a slicer selection (e.g., “Next / Previous”). This forces report authors to rely on bookmarks, What‑If parameter hacks, or custom visuals—none of which scale well or are intuitive to maintain.   A built‑in slicer option that exposes increment/decrement buttons (or a button action that can set a slicer to a calculated value) would significantly improve usability for time‑based and ordinal selectors (e.g., Week 1–52, Scenario numbers, Period offsets).   This functionality would reduce report complexity, improve maintainability, and align Power BI interaction patterns with common UI controls found in other analytics tools. ... View more

Add text/annotation to pipeline canvas.  ... View more

Problem Statement: In Microsoft Power BI Desktop, report development often requires working with multiple panes simultaneously (Fields, Visualizations, Filters, Bookmarks, Selection, etc.). When several panes are kept open on the right-hand side, the available space for the report canvas is significantly reduced. This creates challenges such as: Limited visibility of the report layout Frequent resizing of panes and canvas Reduced efficiency when designing complex dashboards Poor experience for users working on smaller screens Business Impact: This limitation directly affects developer productivity and report quality: Reduced design precision because of constrained canvas space Inefficient utilization of multi-monitor setups (which I believe are common in enterprise environments) Friction for power users handling complex reports with multiple visuals Proposed Solution: Introduce a pop-out / detachable report canvas feature in Power BI Desktop. Key capabilities could include: Ability to detach the report canvas into a separate window Support for drag-and-drop across multiple monitors Independent resizing of panes and canvas Option to dock/undock panes dynamically Example Use Case: A report developer using dual monitors could: Keep all configuration panes (Fields, Filters, Visualizations) on the primary screen Move the report canvas to a secondary screen in full view Design and interact with visuals without space constraints This would significantly improve usability, especially for complex dashboards. Expected Benefits: Enhanced developer productivity Better utilization of multi-screen setups Improved dashboard design experience Reduced dependency on constant UI resizing This feature would align Power BI Desktop with modern development tools that support multi-window workflows and significantly enhance the user experience for professional report developers.   Sample Image ... View more

When a scheduled refresh completes with warnings such as "Cannot convert value 'xx' of type Text to type Number", the warning message in refresh history does not include the table name and column name where the issue occurred. Data refresh in Power BI - Power BI | Microsoft Learn To enable all users to easily investigate the root cause of the warning, please include the affected table name and column name in the refresh history warning message. ... View more

**Problem:** The Event Hubs Spark connector bundled with Fabric requires a custom Java/Scala callback class (`AadAuthenticationCallback`) to use AAD/Managed Identity authentication. In Fabric's managed notebook environment, it's not feasible to compile and deploy custom JVM classes — notebook-defined classes fail with `ClassNotFoundException` on executors.   This means organizations that disable SAS/local auth on Event Hubs (a common enterprise security policy) **cannot use the Spark Event Hubs connector at all** in Fabric.   **Additionally,** Fabric Eventstream also only supports SAS keys for Event Hub connections, creating a second blocker.   **Ask:** 1. Add a built-in `DefaultAzureCredential`-based callback to the Spark Event Hubs connector so `useAadAuth=true` works out of the box — no custom JARs needed 2. Add Managed Identity / Entra ID authentication support to Eventstream's Event Hub source connector   **Impact:** Any Fabric customer with enterprise security policies that require Managed Identity authentication for Event Hubs is currently blocked from real-time ingestion through supported connectors. ... View more

Hi Team, An error occurred while processing the semantic model   Feedback Type: Frown (Error) Timestamp: 2026-04-03T05:16:39.1281579Z Local Time: 2026-04-03T10:46:39.1281579+05:30 Session ID: ec439ece-fb29-49c9-8135-28880ff01a58 Release: March 2026 Product Version: 2.152.1279.0 (26.03)+7cb753613ff9dbf770467b6b4012425246d1fe94 (x64) Stack Trace: Javascript:TypeError at IntersectionsParser.parseCalcValue (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:281020) at IntersectionsParser.calcValue (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:280905) at DsrToCategoricalConverter.parseIntersectionCalc (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:158578) at DsrToCategoricalConverter.parseIntersections (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:158272) at l (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:156494) at DsrToCategoricalConverter.readData (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:156728) at DsrToCategoricalConverter.run (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:151935) at https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:217572 at https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:217583 at Q (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:1457279) PowerBINonFatalError: {"AppName":"PBIDesktop","AppVersion":"2.152.1279.0","ModuleName":"https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js","Component":"IntersectionsParser","Error":"TypeError","MethodDef":"parseCalcValue","ErrorOffset":"1:281020","ErrorCode":""} OS Version: Microsoft Windows NT 10.0.26200.0 (x64 en-US) CLR Version: 4.8 or later [Release Number = 533509] Peak Virtual Memory: 88.2 GB Private Memory: 1.35 GB Peak Working Set: 1.37 GB IE Version: 11.1882.26100.0 User ID: a414e126-c794-4d78-8da1-14385fc7c31d Workbook Package Info: 1* - en-IN, Query Groups: 1, fastCombine: Disabled, runBackgroundAnalysis: False. Telemetry Enabled: True Model Default Mode: Import Model Version: PowerBI_V3 Enabled Preview Features: PBI_DatabricksAdbcVersionEnabled PBI_googleBigQueryAdbcVersionEnabled PBI_scorecardVisual PBI_setLabelOnExportPdf PBI_oneDriveSave PBI_oneDriveShare PBI_odspSaveBackgroundUpload PBI_modernOfficeFilePicker PBI_useModernPublishDialogs PBI_gitIntegration PBI_tmdlInDataset PBI_enhancedReportFormat PBI_advancedSlicerTypeList PBI_aiNarrativesVisual PBI_visualCalculationsAuthoring PBI_copilotUnifiedTooling PBI_UserInstalledNetezzaODBCDriver PBI_sqlDbNativeArtifactsOnDesktop PBI_enableExportQueries Disabled Preview Features: PBI_UseRedshiftODBCV2 PBI_snowflakeLegacyOdbcVersionEnabled PBI_shapeMapVisualEnabled PBI_SpanishLinguisticsEnabled PBI_qnaLiveConnect PBI_b2bExternalDatasetSharing PBI_onObject PBI_publishDialogsSupportSubfolders PBI_enhancedReportFormatPBIX PBI_qnaImproveLsdlCopilot PBI_customCalendars MashupFlight_EnableOracleBundledOdacProviderV2 PBI_supportUDFs PBI_newVisualDefaults2026 Disabled DirectQuery Options: TreatHanaAsRelationalSource Cloud: GlobalCloud Recent Actions: SaveFormattingValues, SaveFormattingValues, SaveFormattingValues, SaveFormattingValues, SaveFormattingValues, SaveFormattingValues, SaveFormattingValues, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, RemoveFieldFromRole, AddFieldInRole DPI Scale: 150% Supported Services: Power BI WebView2 Runtime Version: 146.0.3856.84 WebView2 SDK Version: 1.0.2365.46 ... View more