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