Forum Discussion
DMTS_OAuthFailedToGetResourceIdError
Hi jonmorgan , Thank you for reaching out to the Microsoft Fabric Community Forum.
Power BI Desktop is more flexible in how it connects, but the Service only supports the native Snowflake connector with specific authentication paths. If the dataset was built using ODBC or an older connector version, the Service can’t complete the OAuth handshake, which explains why the error shows up inconsistently across tables.
Another common cause is the Azure AD tenant link. For OAuth to work in the Service, the Snowflake integration has to be registered in the same tenant as your Power BI environment. If your Snowflake login is tied to a different Azure AD tenant, the Service won’t be able to retrieve the token even though Desktop allows it.
Finally, there have been recent connector changes in both Microsoft and Snowflake. If this issue started suddenly, it’s very possible your dataset was built before those changes and now needs to be republished using the latest version of Power BI Desktop. Reconnecting to Snowflake through the native connector, publishing again and then re-entering credentials in the Service usually resolves the problem. If your Snowflake instance is private (not publicly reachable), you’ll also need a data gateway, since the Service alone can’t reach it.
Power BI August 2023 Feature Summary | Microsoft Power BI Blog | Microsoft Power BI
Power Query Snowflake connector - Power Query | Microsoft Learn
Hi jonmorgan , hope you are doing great. May we know if your issue is solved or if you are still experiencing difficulties. Please share the details as it will help the community, especially others with similar issues.
Sadly not as yet. I think I've narrowed it down to the Snowflake connector that is used for some of the data, but not why the issue has suddenly started.
Hi jonmorgan , Thank you for reaching out to the Microsoft Fabric Community Forum.
Power BI Desktop is more flexible in how it connects, but the Service only supports the native Snowflake connector with specific authentication paths. If the dataset was built using ODBC or an older connector version, the Service can’t complete the OAuth handshake, which explains why the error shows up inconsistently across tables.
Another common cause is the Azure AD tenant link. For OAuth to work in the Service, the Snowflake integration has to be registered in the same tenant as your Power BI environment. If your Snowflake login is tied to a different Azure AD tenant, the Service won’t be able to retrieve the token even though Desktop allows it.
Finally, there have been recent connector changes in both Microsoft and Snowflake. If this issue started suddenly, it’s very possible your dataset was built before those changes and now needs to be republished using the latest version of Power BI Desktop. Reconnecting to Snowflake through the native connector, publishing again and then re-entering credentials in the Service usually resolves the problem. If your Snowflake instance is private (not publicly reachable), you’ll also need a data gateway, since the Service alone can’t reach it.
Power BI August 2023 Feature Summary | Microsoft Power BI Blog | Microsoft Power BI
Power Query Snowflake connector - Power Query | Microsoft Learn
Thanks for all the tips, they helped guide me to a sort of resolution. Turns out there were two issues, one with Snowflake to do with the connector update. Moving it over to implementation 2 seems to have worked. The other was related to a JSON connection that had suddenly stopped working, I found a solution on line that by skipping the connection test it then works without issue. Some of the Snowflake connections are still causing issues but switching those back to implementation 1 seems to be resolving while I dig into it more.