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

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 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

Hi Microsoft Fabric Team, We are encountering a sign-in error when trying to use the Fabric MCP connector. The error is not on our tenant side — the app registration belongs to Microsoft. Error Code: AADSTS50011 Full Error Message: "The redirect URI 'https://global.consent.azure-apim.net/redirect/fabricmcp' specified in the request does not match the redirect URIs configured for the application '3f021233-1542-41f0-8faa-ca8aca37ace'." Details: - App ID: 3f021233-1542-41f0-8faa-ca8aca37ace - Missing Redirect URI: https://global.consent.azure-apim.net/redirect/fabricmcp - This application is NOT registered in our Entra tenant — it belongs to Microsoft This means the redirect URI needs to be added by Microsoft on their side in the app registration for the Fabric MCP application. Requested Action: Please add 'https://global.consent.azure-apim.net/redirect/fabricmcp' as an allowed redirect URI in the Microsoft-owned app registration (App ID: 3f021233-1542-41f0-8faa-ca8aca37ace). Thank you.       ... 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,    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

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

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

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

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

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

Hi, Since the update July 2025, Matrix visuals with fields parameter hierarchies show a confusing behavior when one field is on different hierarchy levels. To illustrate the issue I created a test report with the following field parameter:   FP_Test = { // Group1 ("Category", NAMEOF('Product'[Category]), 0, "Group1"), ("Business Type", NAMEOF('Reseller'[Business Type]), 1, "Group1"), // Group2 ("Country", NAMEOF('Sales Territory'[Country]), 10, "Group2"), ("Category", NAMEOF('Product'[Category]), 11, "Group2"), // Group3 ("Business Type", NAMEOF('Reseller'[Business Type]), 20, "Group3"), ("Color", NAMEOF('Product'[Color]), 21, "Group3") }   The fields "Category" and "Business Type" are part of 2 hierarchies but on different levels. The visual looks like this:   If I now switch to Group2, I get the following display:   For the users, it looks as if the button did not work, as the category is still displayed. They can't even recognize that they are at a drilled down level because no +/- signs and no elements of the next higher hierarchy are displayed.  Switching now to Group3 it gets completely weired because only the lowes level ("Color") is visible whereas the user would expect to start with "Business Type". The users have to be very experienced to notice that they are looking at a drilled down level and need to drill up  to see the full hierarchy for this group:   Starting with an expanded hierarchy in Group1, it is not apparent in which case the hierarchy remains expanded, when it is collapsed and when a drill down takes place without a top level hierarchy. Anyway, a hierarchy that is expanded by default is not recommended or possible for a large number of hierarchy elements.   The same behavior applies to bar charts and column charts, where it is even more difficult to recognize that it is a next lower level and you have to drill up.   Please add a formatting option to all visuals that works with the drill-up/drill-down functionality, where the developer can choose whether the matrix/chart should collapse when switching the dimensions or retains its expanded state.   And if a matrix/chart retain the expanded state, please add the upper levels as well! I'm working as BI Consultant for customers and they complain about this new behavoir, because it appears as if the dynamic doesn't work anymore. I don't want to go back to bookmarks switching between various matrix visuals.   Thanks and best regards! ... 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

I have a report with a matrix visual, which is powered by a DirectQuery source that gets updates every minute. The report refreshes automatically with a change detection on the column with last updated timestamp. The problem is that the matrix visual scrolls up to the 101st position after each visual refresh. Users have to scroll back down to the position they were looking at before, and after a minute it jumps back up again. The faster I wish to refresh this report, the more prominent this issue becomes. The position of the scroll bar does not reset when the visual displays records in range 1-101 prior to refresh. The root cause seems to be present in the DAX query generated on the matrix refresh event - it contains "TOPN(101)" filter. Each scroll event past that number of rows generates a subsequent query that fetches next 101 records. This degrades the user experience massively, and puts unnecessary strain on my source by sending lots of small queries. In this case, I'm working with around 3000 raw records, which aggregate to 350 rows in the matrix. This could be easily fetched with a single query, which should keep the position of the scroll bar in place between refreshes. I would like to be able to specify the number of records fetched in a single query to my source; 101 is a very conservative number. ... View more

Since the August 2025 update it appears Direct Query connections cannot be selected when connecting to Dataflow Gen 1 sources. Any reports that were previously setup using Direct Query return the following error: "This query contains transformations that can't be used for DirectQuery." ... View more

I'm encountering the following error when trying to connect to a Dataflow using the Dataflow connector in Power BI: The name 'Lakehouse.Contents' does not exist in the current context. This happens when attempting to access a Dataflow that is stored in a Microsoft Fabric environment, specifically within a Fabric workspace. Context: I'm using the Dataflow connector in Power BI Desktop. The Dataflow is created and stored in a Fabric workspace (not a legacy workspace or classic Power BI workspace). The error appears immediately after selecting the Dataflow and trying to load or transform the data. Troubleshooting so far: Verified permissions to the workspace and the Dataflow. Confirmed that the Dataflow is published and accessible via the Fabric UI. Tried using both organizational and personal accounts for authentication. Question: Has anyone else experienced this issue when working with Dataflows in Fabric environments? Is there a known workaround or update needed to support this connector in Fabric? Any insights or suggestions would be greatly appreciated!   Thanks in advance, David ... View more

A huge range of app use cases don’t involve the Power BI homepage at all, so why do we need a button that takes you “back” there? In my own tenant, only a small percent of users ever discover the button — and when they do, it usually causes confusion. Most of our audience comes in through our company intranet or a saved bookmark directly to the app. Hitting “Go back” takes them somewhere unfamiliar (Power BI home) and disrupts their workflow. This could be fixed with one of two approaches: Let admins remove or hide the button entirely Or at least rename it to something clearer like “Power BI Home” so expectations match what it does Either way, making this change would help avoid confusion and keep users focused on the content that matters most: the app itself. ... View more