Semantic model refresh failed - Snowflake Key Pair cloud connection
Hello everyone! I have multiple Power BI semantic models that refreshes via Power Automate. The model connects to Snowflake using a shareable cloud connection with Key Pair authentication (no on-prem gateway). This morning I got several refresh failures with: We are unable to access some data source because the artifact is missing connection details. Please contact the artifact owner to bind the data source to a data connection or use default connection settings for the unbound data source. Refreshes appear to be working again now and it worked automatically for some models at the same time others failed. I didn't change the Key Pair, the cloud connection, or the semantic model binding. What typically causes this error with a Snowflake Key Pair cloud connection? Is this an unbound data source (binding lost) rather than invalid Key Pair credentials? How can I prevent this from happening again (permissions on the connection, avoid Default/Personal mapping, re-bind after publish, etc.)? Thanks!
Desktop link to Community not working
I recently closed a similar ticket because I was still using the July version of PowerBI Desktop - I was told I could logon to the community forum using :Home | Microsoft Fabric Community instead. Desktop updated overnight and I'm now on the latest August version and the link through Desktop still does not work. That link is there as a shortcut, it has always worked and now it doesn't (no doubt related to the recent upgrade). How can I escalate this to Fabric? Thanks
pbivisuals.powerbi.com server failure
We're using PBI Embedded with some certified custom visuals including Plotly. These custom visuals have stopped displaying recently and we've traced the problem to simple GET calls on pbivisuals.powerbi.com returning data so incredibly slowly that the visual times out. Occasionally that server will return the requested json definition (all 38MB of it) in 150ms. But the vast majority of times it will respond at less than 10kb per second (or not at all) and the request will ultimately time out. This is very easy to replicate in any browser by trying to access the Plotly visual definition directly: https://pbivisuals.powerbi.com/plotlyJSVisualEEDDFAAB4619388784AE7972BC162ECDFAAB46196.2.1.0.0.cc6d7a5f02f9a7ef6a04543a2a66140847cec0ac298cbe8d7eb853fead875102.pbiviz.json We've tested fetching this via VPN across multiple global locations, via different browsers on different machines etc and is is almost always paralyzingly slow. Is anyone able to suggest how to get Microsoft to look at this? Just to reiterate, our production reporting platform is effectively down atm because of this server-side issue. Thanks for any assistance you can offer!Share your thoughts on the New Power Query experience in Power BI Desktop (Preview)
We’re excited to begin rolling out the new Power Query experience in Power BI Desktop, starting with the release of a redesigned Get Data experience (Preview) in the May 2026 update—and we’d love your feedback. What is the new Power Query experience? We’re modernizing Power Query to deliver a more consistent, accessible, and streamlined data preparation experience across Microsoft Fabric, Power BI, and Excel. This release is the first step, focused on Get Data, with a modernized Power Query Editor experience planned for later this year. What’s new in this release? The new Get Data experience has been redesigned to help you discover and connect to data faster: Improved data source discovery — A unified, easier-to-navigate experience to find all your data sources Streamlined connection flow — Fewer steps to connect so you can get started quickly Built-in accessibility — Full keyboard navigation and dark mode support out of the box Greater consistency — Aligned experience across Fabric, Power BI Desktop, and Excel How to try it The new Get Data experience is available as a Preview in the May 2026 release of Power BI Desktop. To enable it: File > Options and settings > Options > Preview features > New Power Query experience We want your feedback! This is just the beginning, and your input will directly shape the broader Power Query experience. We’d love to hear: What do you like? What improvements stand out to you? What's missing? Are there data sources or workflows you expected to see? What could be better? Did you run into any friction or unexpected behavior? Share your thoughts in the replies below—whether quick impressions or detailed feedback, every comment helps. To learn more, see New Get Data experience in Power Query. Thank you for helping us shape the future of Power Query!Power BI Service 500 Internal Server Error
Hi, Are there currently general issues with the Power BI Service? We're trying to publish from Power BI Desktop to different workspaces. Error: Couldn't publish to Power BI An error occurred while attempting to publish 'NAME.pbix': The remote server returned an error: (500) Internal Server Error. Details: Request ID 1f344752-2b27-4b2e-b401-7230b37a05af Activity ID 97f3f776-1119-4aa1-9d20-a85756e880a4 Service URL https://wabi-north-europe-j-primary-redirect.analysis.windows.net/ Error Code CommunicationFrameworkCommunicationException Session ID 97f3f776-1119-4aa1-9d20-a85756e880a4 Client version 2.156.951.0
