We are observing Copilot in Power BI returning semantic‑model‑grounded responses (including DAX calculated results) for reports and models hosted entirely in shared capacity, even when the user has View‑only access. This appears to conflict with current Microsoft documentation around Copilot capacity and  behaviour. Environment / Setup Fabric F4 capacity enabled for a Copilot PoC (all existing reporting is on a shared capacity) Test report and semantic model: Both saved in a shared capacity workspace Workspace is not Fabric‑backed User permissions: Viewer access to the report No Build permissions on the semantic model Copilot accessed via: Copilot pane in the Power BI Service (within the report) We expected that copilot will only provide responses at the visual level for any artefacts in shared capacity workspaces and that model grounded responses would only be provided where the model is in the fabric workspace. Believe this is unexpected behaviour or a bug? If it is expected behaviour then the issue of preventing copilot accessing existing models is then our very big issue as there seems to be no way to control access to existing models that are published on the service is we enable copilot for our users.. ... View more

Since updating to the March 2026 version of Power BI Desktop, I am unable to connect to a specific Tabular model on Azure Analysis Services (AAS). Error Message: "The connection failed. An error occurred while trying to connect. Details: Could not connect to the Analysis Services server because the connection timed out or the server name is incorrect.". Key Findings: Regression: The connection works perfectly with the November 2025 version of Power BI Desktop on the same machine and with the same credentials/network. Specific Context: The issue occurs only with one specific Tabular model, while others remain accessible. Community Feedback: Other users and clients have reported similar connectivity issues specifically with the latest March 2026 update. Steps to Reproduce: Open Power BI Desktop (March 2026 version). Select "Get Data" > "Azure Analysis Services database". Enter Server and Database name (Connect Live). Error appears after a short attempt. Environment Details: Current PBI Desktop Version: 2.151.1182.0 Previous Working Version: November 2025 Data Source: Azure Analysis Services (Tabular) Authentication: Azure Active Directory - Universal with MFA ... View more

Regardless of desktop appearance selection (dark, legacy, light, system default) the top three icons on the left nav (Report view, Table view and model view) are now rendered solid black.  Has anyone seen this? The icons are functional, just solid black.  Pretty sure this showed up just today; repaired the install to no effect. - Using November 2025 Release.       ... View more

  Feedback Type: Frown (Error) Timestamp: 2026-03-06T18:19:06.7423766Z Local Time: 2026-03-06T12:19:06.7423766-06:00 Session ID: d138d906-42e5-459d-9e66-75bfdd06282a Release: February 2026 Product Version: 2.151.1182.0 (26.02)+b81be254f3450e536a43f73a9777be8307916ef0 (x64) Stack Trace: Javascript:TypeError at SandboxDelegate.persistProperties (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:3036206) at SandboxVisualProxy.onMessageReceived (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:12686173) at https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:12681723 at MessageChannelProxy.invokeHandler (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2854412) at MessageChannelProxy.dispatchMessage (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2854294) at MessageChannelProxy.onMessageReceived (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2853959) at e.source._peerWindow._peerOrigin.e.origin._peerOrigin.e.data.type.e.data.nonce._handshakeNonce._peerPort.onmessage (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2852283) PowerBINonFatalError: {"AppName":"PBIDesktop","AppVersion":"2.151.1182.0","ModuleName":"https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js","Component":"SandboxDelegate","Error":"TypeError","MethodDef":"persistProperties","ErrorOffset":"1:3036206","ErrorCode":""} OS Version: Microsoft Windows NT 10.0.19045.0 (x64 en-US) CLR Version: 4.8 or later [Release Number = 533325] Peak Virtual Memory: 87.7 GB Private Memory: 1.12 GB Peak Working Set: 1.2 GB IE Version: 11.3636.19041.0 User ID: ee65ea6f-6dfa-4919-aa17-f724be5fcc43 Workbook Package Info: 1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False. Telemetry Enabled: True Model Default Mode: Composite 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_directLakeOnOneLake PBI_advancedSlicerTypeList PBI_aiNarrativesVisual PBI_visualCalculationsAuthoring PBI_copilotUnifiedTooling PBI_sqlDbNativeArtifactsOnDesktop PBI_dataFunctionActions PBI_enableExportQueries Disabled Preview Features: PBI_snowflakeLegacyOdbcVersionEnabled PBI_shapeMapVisualEnabled PBI_SpanishLinguisticsEnabled PBI_qnaLiveConnect PBI_b2bExternalDatasetSharing PBI_onObject PBI_publishDialogsSupportSubfolders PBI_enhancedReportFormatPBIX PBI_qnaImproveLsdlCopilot PBI_customCalendars PBI_UserInstalledNetezzaODBCDriver MashupFlight_EnableOracleBundledOdacProviderV2 PBI_supportUDFs Disabled DirectQuery Options: TreatHanaAsRelationalSource Cloud: GlobalCloud Recent Actions: VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties DPI Scale: 100% Supported Services: Power BI WebView2 Runtime Version: 145.0.3800.82 WebView2 SDK Version: 1.0.2365.46 ... View more

Hello, The November update of Power BI Desktop messed up the metrics and visuals in my new card visual. It happened with the image in the callout, and the reference labels had their layout changed, no longer keeping the spacing I wanted. This is really frustrating because the users who view the report daily (including the bosses) are not getting the metrics they need. Could you please provide a fix or workaround for this problem? Thank you for your support. Just a sample image for your reference.   ... View more

Hi,    When refreshing the schema and data in a PowerBI dashboard, i received an "Object reference not set to an instance of an object" error for all tables. This error does not occue if only the data is updated, so it seems to be an issue with updating the schema.    I experience this error with the February 2026 version of the PowerBI desktop app, however when reverting to the November 2026 version of PowerBI, this error does not occur.    Thanks! ... View more

Following the post: https://community.fabric.microsoft.com/t5/Desktop/ALT-letter/m-p/5108912 The Alt + [letter] shortcuts are not working. I also tested this on version 2.150.2455.0 64-bit (January 2026). ... View more

Dear MS Power BI Team,   Since ± the beginning of October 2025, I have noticed an issue that the "Grid" type of Arrangement is broken on the service side:   Expected: in case of having 4 columns out of 6, an extra space on the right side left for 2 empty columns     Once published to the service side, the buttons stretch across the entire width, same way as behave "Horizontal" type of arrangement:     Can you please pay attention to this service side issue and fix?   regards, Alena ... View more

I created  .pbip file, everything worked well; Suddenly yesterday something changed - it can be worked on and saved; however, the second I close file and try to reopen it. or try to publish the pbip, or sync workspace with git branch - it returns this error: 'pages/4dbd8244539262a7c568/visuals/e7c9a06c5e6a8566ddbe/visual.json': Property 'showActionsInTooltips' has not been defined and the schema does not allow additional properties. Path 'visual.visualContainerObjects.visualTooltip[0].properties.showActionsInTooltips' I tried to google this, but i think this Action in Tooltips feature is too new to be reported anywhere yet. I am wondering if it's only me experiencing this issue... or it's a common "bug"? ... View more

Power BI Desktop February 2026 — "Refresh All" Permanently Stuck on "Evaluating" Issue Description: After updating to the February 2026 release of Power BI Desktop, "Refresh All" hangs indefinitely on the "Evaluating" stage and never progresses. This affects multiple semantic models of varying sizes — not isolated to a single file or large model. Individual table refreshes complete without issue. The problem occurs only on "Refresh All" Affected Versions: - Version 2.151.1052.0 64-bit (February 2026) — issue present - Version 2.151.1182.0 64-bit (February 2026 QFE) — issue still present Working Version: - Version 2.150.2102.0 64-bit (January 2026) — refresh completes normally Environment: - Data source: SQL Server (import mode) - Multiple models affected, ranging from small to ~2.8 GB - 64-bit Power BI Desktop - Hardwired ethernet connection Troubleshooting Steps Taken (none resolved the issue): - Updated to the latest February 2026 QFE build (2.151.1182.0) - Changed "Parallel loading of tables" from Default to "One (disable parallel loading)" under Current File > Data Load - Individual table refreshes all complete successfully - Reverted to January 2026 build (2.150.2102.0) — Refresh All works immediately, confirming this is a February 2026 regression Expected Behavior: "Refresh All" should evaluate and refresh all tables as it does in the January 2026 release. Actual Behavior: All tables remain in "Evaluating" status indefinitely. No error is thrown. The process must be force-cancelled. This behavior is consistent across multiple models of different sizes. This is a clear regression introduced in the February 2026 release. Rolling back to January 2026 immediately resolves the issue. Please investigate and patch in a future QFE or the March 2026 release. ... View more

Issue Description We are experiencing an issue with Text Input Slicers in Power BI Service where the slicer value does not reset when using bookmarks or the Clear All Slicers option. Observed Behavior A user types a value into a Text Input Slicer (e.g., MRN). Clicking a Reset/Clear bookmark visually clears the slicer. When the user interacts with the slicer again, the previously typed value automatically reappears. This behavior occurs only in Power BI Service. The same report works correctly in Power BI Desktop. Expected Behavior Text Input Slicer values should fully reset when a reset bookmark or Clear All action is applied. After reset, the slicer should not retain or reapply previously typed values. Additional Notes This issue affects all reports using text-based slicers (e.g., MRN, Account Number). Dropdown slicers work as expected and reset correctly. This behavior appears to have started after a recent Microsoft Fabric / Power BI Service update. The issue is not related to report design, bookmark configuration, or persistent filter settings. Business Impact Prevents reliable Reset Filters functionality. Causes user confusion when old values reappear. Forces redesign of production reports to avoid text input slicers. Current Workaround Replace Text Input Slicers with Dropdown slicers, which reset correctly. Request for Clarification Could someone from the Power BI / Fabric product team please confirm whether this behavior is by design or a known issue planned to be addressed? This impacts multiple production reports and is forcing us to replace text input slicers with dropdowns. Understanding whether a fix or configuration option is planned would help us decide whether to wait for a resolution or permanently redesign our reports. ... View more

A couple of days ago we noticed an issue with our Azure maps in reports published via public to web. The map will load like below but without any data points mapped. The only way to get it to load is to switch from using data such as postcodes or street addresses in the 'location' input, to using the 'latitude' and 'longitude' inputs instead.   I tried this on various devices and internet connections and kept getting the same issue.   We think this indicates an issue with publish to web reports not being able to lookup related mapping coordinates to the provided location field? As it always displays as expected in the desktop file and the app.powerbi.com workspace, even when using our location field input.   Some clarification of why this is happening, and whether it can be fixed would be helpful thanks.   I've created a public report that demonstrates the Bing vs Azure map for postcode location (1st page - Azure map doesn't work) and then using latitude/longitude for the Azure map (2nd page - works) https://app.powerbi.com/view?r=eyJrIjoiYmFkNGI3MjItNmU2Yi00OGViLWI3N2MtMGRlMzY5MmQ1MWRiIiwidCI6IjM3YzM1NGIyLTg1YjAtNDdmNS1iMjIyLTA3YjQ4ZDc3NGVlMyJ9   ... View more

Hi all, I’m seeing recently a recurring issue in Power BI Desktop where a brief CMD window appears during report load and sometimes during semantic model-related changes. After digging into it, I found that the CMD window is actually SQLDUMPER.EXE. From what I understand, SQLDUMPER.EXE is a Microsoft diagnostic utility that gets triggered when an internal Microsoft component crashes or throws an exception. In this case, the actions seem to be tied to msmdsrv.exe, which is the backend model/query engine used by Power BI Desktop. What the issue looks like The black CMD window appears briefly. It first happens while the report is opening, specifically during “Preparing report”. It can also happen later when making changes that affect the semantic model, for example renaming a field or making other model-related modifications. The issue does not seem to be a simple visual/UI problem. It looks more like the backend model engine is hitting an exception and SQLDUMPER is collecting a dump. My troubleshooting so far Confirmed the CMD window is SQLDUMPER.EXE Using process monitoring, I confirmed that the CMD window is SQLDUMPER.EXE. Looking deeper, the process triggering it appears to be msmdsrv.exe, which is the Analysis Services/model engine running behind Power BI Desktop. No issue with a PBIX that has no external file connection In my tests, the issue does not appear when the PBIX contains only embedded data and no external data source connection to a file. You can simulate it just entering a dummy data using "Enter Data" in power bi. Issue will not happen on those reports. Happens in both Store version and downloaded version I tested both: the Microsoft Store/App version the downloaded installer version The issue happens in both. Preview features do not seem to be the root cause Turning off some preview features, such as On-object interaction, seemed to reduce the frequency somewhat, possibly because they trigger semantic model changes more often. However, this did not solve the issue completely, so I do not think this is purely a preview feature problem. Cache clearing and fresh install did not fix it I tried: clearing cache fresh installation switching to the downloaded version None of these resolved the problem. Running Power BI as Administrator prevents the issue While investigating logs, I noticed some apparent file access-related problems involving msmdsrv.exe. That led me to try Run as administrator. When I ran Power BI Desktop as Administrator, the issue did not appear. I even turned all preview features back on and tested again as Administrator, and it still did not happen. Moving the PBIX to a simple local folder did not help I also moved the report to a simple folder path such as: C:\test. This did not solve the issue. Current conclusion So far, on my machine, the only thing that prevents the issue is running Power BI Desktop as Administrator, which is obviously not a real solution. At this point, I suspect this may be one of the following: a Power BI Desktop bug a permissions / file access / credential issue something related to external data source connections possibly some interaction between the local Analysis Services engine (msmdsrv.exe) and file-based external sources Main questions Is anyone else seeing SQLDUMPER.exe appear during “Preparing report” or during semantic model changes? Has anyone identified the exact trigger? Has Microsoft acknowledged this anywhere? Is there any proper fix besides running Power BI as Administrator? Thanks in advance. I’m sharing this in case it helps others narrow down the issue. ... View more

To connect to our IBM DB2 database, we need to set a custom "packageCollection" value as an additional connection property in a copy activity.   However, when inspecting the pipeline's JSON, we noticed that "packageCollection" is added with a trailing space ("packageCollection "). This causes issues, as the DB2 database doesn’t recognize the property correctly.   Manually removing the space in the JSON makes the pipeline work again, so for anyone facing the same issue, that’s a temporary fix. But ideally, this bug should be resolved at the source.   As it stands, fixing it manually means the property can’t be configured through the UI anymore.   ... View more

I have an issue where the “new card” visual layout becomes misaligned / messy after publishing to Power BI Service, even though everything looks neat and properly aligned in my PBI local (desktop).     PBI Desktop         PBI Services   is there anyone have same issue guys? ... View more

Hello, Starting today, Power BI Desktop freezes every time I try to save.  This happend to me and at least one other colleague. The freezing does not prevent the saving itself so far, but I need to restart Power BI Desktop after each time I save my Report.   Has anyone had a similar issue so far or any suggestion to resolve it? ... View more

After the latest updates released with the November Update, all our reports that use the New Card Visual have a serious problem with the management of images inserted in the Card. For example. I have this card with three blocks in which I have inserted a small icon (see image). In PowerBI desktop, the rendering is correct and consistent with the values entered in the configuration. However, when I publish the report on PowerBI Service, the card rendering is completely incorrect: (note how the image in the card is significantly larger, as if the “size” 50px parameter were not being taken into account) Could you kindly intervene as soon as possible, as all our reports using the new cards are currently illegible and, in some cases, do not contain any information? Regards -- Gianluca Pinelli ... View more

Good Day,   Occassionally I filter tables using a Table View to copy filtered results to use outside of Power BI - I.E. in Excel.   As of today it appears that when copying the Table View that has been filtered, it ignores the filters and copies the whole table. This is an issue for me as when I have a table in excess of 700,000 rows it makes this process extremely slow to copy from Power BI, and near impossible to paste it into Excel.   I have already tried uninstalling and reinstalling the program.   Is anyone else experiencing this issue?   As an example, we are a service company and we have a geographic alignment for our field service team. Simply, filtering a table by the "East" Region and trying to copy the table when filtered to the East is not working. Instead, the entire table is copied.   ... View more

Hello everyone, I’m facing an issue with the Azure Maps visual in Power BI after this new update and I’d appreciate any help or insights. I added a reference layer to an Azure Maps visual. In Power BI Desktop, the reference layer behaves as expected: the transparency works correctly, allowing me to clearly see the base Azure Maps content behind it (street names, places, establishments, etc.). However, after publishing the report to Power BI Service (web), the same reference layer appears as if its transparency were 0% (fully opaque). As a result, it completely hides the underlying Azure Maps details, such as street names and other map information. Has anyone experienced a similar issue with Azure Maps visuals behaving differently between Desktop and Service? Is this a known limitation or bug, or is there any workaround to ensure the transparency is respected after publishing? ... View more