Share your thoughts on the New Power Query experience in Power BI Desktop (Preview)

[miguel]

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!

[Mr_Analyst]

With feature enabled, when I navigate to Get Data > Power BI Semantic Model, the new experience window opens, but it opens to OneLake Catalog and nothting appears (spinning cycle).  I am a government community cloud (GCC) customer and OneLake does not exist for GCC. My Power BI semantic models from current workspaces does not display.

[miguel]

Thank you for reporting this! Working internally with the team who owns this component to make sure that we have a story for users in GCC.

For the time being, we suggest going back to the legacy experience so you can have the sired view for semantic models.

[Prince0011]

Thank you for introducing the new Power Query experience. After reviewing the preview, I appreciate several improvements:

✅ The redesigned Get Data interface feels cleaner and more modern.

✅ Data source discovery is more intuitive, making it easier to locate connectors.

✅ The streamlined connection flow reduces the time required to connect to data sources.

✅ Dark mode support and improved accessibility are welcome additions.

Some suggestions for future enhancements:

• Add a "Recent" and "Favorites" section for frequently used data sources.

• Provide more filtering and categorization options when browsing connectors.

• Include guided onboarding tips for users transitioning from the classic experience.

• Ensure all existing Power Query features remain easily accessible as the editor modernization rolls out.

Overall, this is a positive step toward creating a more consistent experience across Microsoft Fabric, Power BI Desktop, and Excel. I'm looking forward to seeing the modernized Power Query Editor later this year.

[Daniel_Leckie]

Have tried out the new Power Query Connection release in to public preview, and immediately release you can't create custom SQL. 😞
This has meant most of our users have reverted to the old "Get Data" experience.
This would be our biggest barrier and hope this is fixed prior to full GA release.

I do like that existing Fabric Items are more available, being seen on a bigger screen.

Also looks like it is caching the connections and list of objects, which is fine, but if you've already created a model using one connection then is makes sense to connect to the existing Model created before in Fabric.

[miguel]

definitely try the June version which does have the support that you are mentioning 🙂 

[KarolinaCS]

Currently, the option to set the credential type and credentials to connect directly to my API is not intuitive or visible.

[umarkiegi]

Hi,
The new interface omits (or hides) the option "Combine & Transform data" when using the folder Power Query data source.
thanks,
Urtzi

[miguel]

Thanks for the feedback!

Currently the process is a bit different from the legacy UI.

In the new UI we surface the "Combine" button and, once you're in this screen, we allow you to define if you wish to continue the transformation process within the Power Query editor ("Transform data" option) or just load the result of that to the data model (Via the "Load" option).

This way we delay the decision that you want to make around whether you want to commit to loading the result to the data model directly or do more transformations in the Power Query editor.

[ancasselman]

Advanced Options seems to be missing for Amazon Athena as well, so no way to enter a custom SQL query.
Also, I get this error after authenticating: An exception occurred: [Expression.Error] We cannot convert the value null to type Record. (Session ID: 978a81c1-ec2f-43ea-811a-c44b1c1ed3ca)

[miguel]

Definitely give the June version of Power BI Desktop a try as we changed the behavior for connectors that were affected by the gap, so you should be redirected to the legacy UI version for those connctors (including Amazon Athena).

[anthony-b]

Our custom connector uses Navigation Tables as described here https://learn.microsoft.com/en-us/power-query/handling-navigation-tables. This was working as expected with the old experience for years. The new experience just displays them as regular tables. This has resulted in confusion for some of our customers who have recently switched to the new experience. Is this a bug or are navigation tables no longer supported?

[miguel]

Would you mind sharing a bit more about what the differences are?  What were those item being rendered as before? when you mention "tables", is this just about the icon being shown in the navigator?

If you can share some screenshots of the previous experience versus the new one or even some sample code that we could use to try things out with implicit authentication (perhaps a .mez or .pqx file), that would help tremendously.

[anthony-b]

I was able to reproduce the issue using the NavTable Nested source from the NavigationTable sample https://github.com/Microsoft/DataConnectors/tree/master/samples/NavigationTable.

As-is, the sample works as expected in both the old and new experience. Changing "Nested C"'s ItemKind and ItemName to "Table" resulted in the change in behavior we see in our connector with the same ItemKind. This link seems to imply that only the icon should change https://learn.microsoft.com/en-us/power-query/handling-navigation-tables#values-for-itemkind.

[miguel]

Thank you for this!

We've identified the bug and we'll be looking closer into it.

[cxuereb_sf]

Does not work with Snowflake at all... Had to tell our users not to use it this feature for now and opened a MSFT Support Ticket about this.

[miguel]

Thanks for the feedback! 
The June version of Power BI Desktop introduced a mitigation path where, when you enable this preview feature, it'll take you to the legacy experience.

In parallel, we're working on enabling the native query support for all connectors in the modern UI and this will become available in both Power BI Desktop, Power BI web modelling and all Power Query Online experiences.

thanks again for your support!

[teja_allam]

Basically, when I connect to a Snowflake database using the organizational account (Azure AD / Entra OAuth SSO) sign-in method with the New Power Query experience preview enabled, the classic Recent Sources list stops working. After connecting (Get Data → Snowflake → server + warehouse → organizational account sign-in), loading a table, doing Close & Apply, and saving the .pbix, the Home → Recent sources list still shows “There are no recent sources to display” — even though the credential is saved correctly under Data source settings → Global permissions and the load succeeded. The “Recent data (Preview)” panel in the new Get Data dialog also stays empty. Disabling the New Power Query experience preview (Options → Preview features) and restarting fixed it , Recent Sources populates normally after that. So it appears the New Power Query experience isn’t writing to the classic Recent Sources store, at least with the Snowflake connector plus organizational-account auth.

[danny_oneill]

I tried it for a week and switched back. Even loading CSV or Excel it is just over complicated. 

Clicking CSV now I have to wait for the interface to load. I just want to select a file and go. Not have 'an experience'. 

I want to click the little drop down on the get data, select CSV, select file, done.

New experience is drop down, select csv, wait for interface to load, click the browse button, select the file

Its an extra click and a longer wait.

[danextian]

With this realase, SQL statement option for the Snowflakes connector is missing. Also, would be better to have the built in connectors load/show up right away rather than wait for all other stuff that are specific to the logged inusers (eg, recennt dat, onelake catalog) to load first.

[Lihlea]

The problem now with this new view, when using WEB API, we are no longer getting the Advanced option to set parameters.