Microsoft Fabric down?   Localization: Europe   Can anyone confirm ? ... View more

The 'Microsoft 365 Usage Analytics' template app has been failing since the 8th of May giving "DataSource.Error: Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed: OData Version: 4, Error: The remote server returned an error: (500) Internal Server Error. OData Version: 3, Error: The remote server returned an error: (500) Internal Server Error.. Microsoft.Data.Mashup.ErrorCode = 10122. Microsoft.Data.Mashup.ValueError.DataSourceKind = OData. DataSourcePath = https://reports.office.com/pbi/v1.0/556f4662-c7de-4312-9a81-dd4e68521c32. . The exception was raised by the IDbCommand interface."   When trying to authenticate I get: "Failed to update data source credentials: Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed: OData Version: 3 and 4, Error: The remote server returned an error: (500) Internal Server Error. OData Version: 4, Error: The remote server returned an error: (500) Internal Server Error. OData Version: 3, Error: The remote server returned an error: (404) Not Found. (Not Found)"   This suggests to me that something has changed on the Microsoft side.  The template app itself feels a little out of date already but our business does find some of its output very useful.  The template app did receive some updates back in Feb, so not abandoned by Microsoft.     ... View more

I am unable to find or access the new "Set as landing page" feature in Power BI, despite having the latest software version installed. The option does not appear anywhere in the UI (neither by right-clicking the page tabs nor under the "Page information" format pane).   ... 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

Issue Summary The On-premises Data Gateway version 3000.314.5 (released April 27, 2026) fails to install on Virtual Machines without GPU acceleration. The previous version 3000.310.1 installs correctly on the same environment with a workaround.   Environment OS: Windows Server 2019 Standard (Build 17763.8644) Machine type: Virtual Machine (no GPU acceleration) .NET Framework: 4.8 (Release 528049) WebView2 Runtime: 147.0.3912.86 Visual C++ Redistributable: 14.44.35211 Gateway version failing: 3000.314.5 Gateway version working: 3000.306   Steps to Reproduce Provision a Windows Server 2019 VM without GPU acceleration Download and run the Gateway installer version 3000.314.5 Observe the installation failing at the service start step   Error Details From Windows Event Log: Application: Microsoft.Mashup.Container.NetFX45.exe Framework Version: v4.0.30319 Description: The application requested process termination via System.Environment.FailFast Message: Unexpected exception in background thread of Mashup container (error code -2146233088) Exception: CLR20r3 — FatalError   From MSI log: Product: GatewayComponents -- Error 1920. Service 'On-premises data gateway service' (PBIEgwService) failed to start. Return value 3.   Additional log evidence: Even with all workarounds applied simultaneously (--disable-gpu, --no-sandbox, --use-gl=swiftshader, WEBVIEW2_USER_DATA_FOLDER), the MSI log confirms the installer returns 1603 with Return value 3 at the INSTALL action, consistent across all attempts on this environment.     Workarounds Attempted — None resolved on 3000.314.5 Workaround Result --disable-gpu --no-sandbox --disable-software-rasterizer ❌Crash persists --use-gl=swiftshader added ❌Crash persists WEBVIEW2_USER_DATA_FOLDER set with full permissions ❌Crash persists Visual C++ updated to 14.44.35211 ❌Crash persists Windows Defender exclusions added ❌Crash persists Performance counters rebuilt (lodctr /R) ❌Crash persists Service account changed to Local System ❌New error: "service is marked as interactive" Working Workaround Version 3000.306 installs successfully on the same VM with the following environment variables: WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS = --disable-gpu --no-sandbox --disable-software-rasterizer --use-gl=swiftshader WEBVIEW2_USER_DATA_FOLDER = C:\GatewayWebView2Data   Expected Behavior The Gateway should install successfully on Virtual Machines without GPU acceleration, as it did in version 3000.306. Actual Behavior Microsoft.Mashup.Container.NetFX45.exe crashes with a fatal error during service initialization, causing the installer to roll back. This appears to be a regression introduced in version 3000.314.5. Additional Context The crash occurs because Microsoft.Mashup.Container.NetFX45.exe requires an interactive desktop session that is not available in VM service context The --use-gl=swiftshader flag (SwiftShader CPU fallback) does not resolve the issue in this version Community thread with full investigation details: [Re: On-premises Data Gateway 3000.314.5 - Microsof... - Microsoft Fabric Community] ... 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

The copilot narrative is not able to produce a percentage with more than two decimals when connecting to a "composite model" data set measure.   For example, if the number format in the base (parent) semantic model is 36.53% then Copilot Narrative will ALWAYS produce .36 (without the proper percentage format) in a composite model vs 36.53% when connecting to the parent data set directly.    Similarly it will not pick up on currency formatting in a composite model.    Steps to reproduce: Build a power BI data set with a measure that produces 36.53% Publish and create a copilot narrative  Create a second PBIX with composite model based on the first semantic model Publish and create a copilot narrative  Compare the result The first narrative will show 36.53% and the second will show .36   This does not seem to be an LLM issue. The narrative output is consistently missing the decimals and percentage sign via a composite model.  ... View more

I've been trying all day to open both the Microsoft UI String Search and Microsoft Terminology Search pages. Just saw another person posting about it in another forum. I have tried different internet connections to rule out that it isn't my network with a problem. The pages didn't load no matter what.   Error details: Underlying Error: AdalUserAccountDisabledErrorCode Http Status Code: 400 Correlation ID: 108f08d4-b290-3c93-5030-9b4ed93bd126 Activity ID: 6a9b4095-fb15-4b0b-85f8-80b1e8dbc2d6 Request ID: aac0fe68-179b-883a-4bf4-1c7d8466a26d Time: Mon May 04 2026 18:29:32 GMT-0500 (Central Daylight Time) Service version: 13.0.28500.530 Client version: 2605.1.29125-train Cluster URI: https://df-msit-scus-api.analysis.windows.net/ Activity ID: 6a9b4095-fb15-4b0b-85f8-80b1e8dbc2d6 Request ID: aac0fe68-179b-883a-4bf4-1c7d8466a26d Time: Mon May 04 2026 18:29:32 GMT-0500 (Central Daylight Time) Service version: 13.0.28500.530 Client version: 2605.1.29125-train Cluster URI: https://df-msit-scus-api.analysis.windows.net/   Thanks in advance ... View more

I created a semantic model using the 'Paste or manually enter data' option, and used this model to create a report. In my application, using the Microsoft.PowerBI.Api 5.1.0 Nuget package, calls to PowerBIClient..Admin.GetRefreshablesAsync(top: 1000, expand: "group") is throwing an exception, "Unknown RefreshType value. (Parameter 'value') Actual value was WebModeling.". Deleting that semantic model from my workspace resolved the issue, and other semantic models created from sources other than that 'Paste or manually enter data' option do not cause the issue.   The relevant object from the https://api.powerbi.com/v1.0/myorg/admin/capacities/refreshables?$expand=group&$top=1000 call response is  { "value": [ { "id": "...", "name": "Test", "kind": "Dataset", "startTime": "2026-05-11T23:30:24.777Z", "endTime": "2026-05-11T23:30:29.737Z", "refreshCount": 1, "refreshFailures": 0, "averageDuration": 4.96, "medianDuration": 4.96, "refreshesPerDay": 1, "lastRefresh": { "id": ..., "refreshType": "WebModeling", "startTime": "2026-05-11T23:30:24.777Z", "endTime": "2026-05-11T23:30:29.737Z", "serviceExceptionJson": null, "status": "Completed", "requestId": "...", "extendedStatus": null, "refreshAttempts": [] }, "refreshSchedule": { "days": [], "times": [], "enabled": false, "localTimeZoneId": "UTC", "notifyOption": "MailOnFailure" }, "configuredBy": [ "..." ], "group": { "id": "...", "name": "..." } } ] } The RefreshType enum, and the related RefreshTypeExtensions serializer, in the Nuget package need to be updated to handle the WebModeling refreshType.   ... View more

Hello Team,   Could you please review and update on the below feature request. Background Customers have reported a regression in the Power BI Service where owners of on‑premises gateway connections unable to modify key connection properties—specifically: Connection type Server name Database name Business Impact Creating new gateway connections: Requires manual remapping of many datasets Increases risk of refresh failures Causes avoidable downtime and maintenance effort This limitation is especially impactful in environments with hundreds of reports and datasets tied to shared gateway connections. Feature Request We request that Power BI reintroduce support for editing existing gateway connection properties, specifically: Connection type Server name Database name At minimum, this capability should be available to: Gateway Admins / Owners. With appropriate validation and warning prompts to prevent accidental misconfiguration. Example below of a connection that the owner of connection and unable to change at this time.   ... View more

Hi Team, For every Power BI report, we have included the report 'Contact' information. However, when we retrieve all report details using the REST API, this information is not visible in the extracted data. I recommend that this important information be made available through the REST API or another straightforward method. Thank you, Mahesh Uppin ... View more

Hi everyone,   I noticed a possible issue in Power BI Desktop 2.150.1926.0 64-bit (January 2026), Report Server version.   In one of my PBIX files, I have a filter set under “Filters on all pages”. The filter is applied correctly at first and still affects the report. However, after hiding and showing the filter pane again, or collapsing and expanding it, the filter is no longer visible in the filter pane.   The filter still seems to be active, but I cannot see or change it anymore in the UI.   So far, I have only seen this behavior in this specific .pbix file/report and I have not been able to reproduce it in a new or different file. Filters on visuals and filters on this page are not affected.   I attached screenshots showing the filter before and after it disappears from the pane.   Has anyone experienced something similar, or is there a known issue or workaround for this? Set Filter:   Collapsing:   Expanding:   ... View more

[Cross-posting from a previous report on the Issues board: link — posting again under a more visible category since the original has been sitting at "New" status with no triage for over a month. This bug is severely impacting Korean Power BI users.] == Summary == When typing Korean (Hangul) in the Power Query Editor (both the Formula Bar and the Advanced Editor), characters overwrite each other instead of composing normally. The bug only occurs when M Intellisense is ON. == Reproduction == Windows 11 with Microsoft Korean IME active Open Power BI Desktop → Power Query Editor Make sure M Intellisense is ON (default) Try typing "고객주소" (Customer Address) in the Formula Bar or Advanced Editor Expected: 고 → 고객 → 고객주 → 고객주소 Actual: 고 → 객 → 주 → 소 (each new syllable replaces the previous one) == Root cause (confirmed by toggle test) == M Intellisense ON → bug reproduces 100% M Intellisense OFF → typing works correctly The Intellisense engine is intercepting IME composition events and committing each syllable prematurely, breaking Hangul composition. == Why this matters == Korean column names, comments, and string literals are extremely common in real-world Korean Power BI projects. Only workarounds available: (a) type in Notepad and copy-paste — extremely tedious; (b) press Space+Backspace after every syllable — unusable for long text; (c) disable M Intellisense entirely — losing Intellisense is not acceptable. This likely affects all CJK IME users (Chinese, Japanese, Korean), not just Korean. == Reproduction caveat for triage == Simply installing the Korean language pack on Windows is NOT enough. You must actually switch the active input method to Korean IME (Win+Space) and type in Korean. Past reports have likely been dismissed as "Cannot Reproduce" because testers only typed English while having Korean installed. == Environment == Power BI Desktop: March 2026 (latest as of report date) OS: Windows 11 IME: Microsoft IME (Korean) == Korean summary (한글 요약) == Power Query 편집기(수식 입력줄, 고급 편집기)에서 한글 입력 시, M Intellisense가 켜져 있으면 이전 음절이 다음 음절에 덮어써져서 글자가 정상적으로 조합되지 않습니다. "고객주소"를 입력하면 마지막 글자 "소"만 남습니다. M Intellisense를 끄면 정상 작동하지만, Intellisense 없이 M 코드를 작성하라는 것은 현실적인 해결책이 아닙니다. 한국 Power BI 사용자에게 매우 큰 불편을 주는 이슈이며, 약 한 달 전 Issues 보드에 보고했으나 상태 변경 없이 방치되어 재제출합니다. Please prioritize. Thank you. ... 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

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

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,   I found a bug with the improved narrator support option. Even though I have disabled this option as you can see in the following screen, I still hear the voice of the narrator each time I open a pbix file. After a moment searching the web, it appears that I am not the only one with this bug and the only "fix" found is more a workaround: disable the sound of the Power BI application.   Thank you !   Olivier. ... 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

Hi, Note: Issue noticed in unreleased July 2025 edition of PBI Desktop.   I m using Field Parameters on Rows of the Matrix and trying to provide dynamic selection for the users. However, the functionality stops after making slicer selection a couple of times and expand/ drill down buttons no longer works.   For the selection as shown in snapshot below, I would expect the user to expand and see Col2 and Col3 in the matrix visual. However.  no matter how many times you click, its not possible to expand. It is not dependent on the order of selection of columns or layout configuration in use. Request you to address the issue ASAP.     Sample PBIX is available at the below link: Test/Test Matrix.pbix at main · modi123p/Test   Thanks & Regards, Madan Prabhakara ... View more