DMTS_OAuthFailedToGetResourceIdError

[jonmorgan]

I keep getting this message after publishing my file to the online service and refreshing. Each time the table is different that it references. I've tried clearing all the permissions in the desktop file and re-entering them, and tried re-signing in to all the sources in the online service but nothings seems to remove the error. 

Can anyone help shed light on what I'm missing (that may of course be very obvious!)? I notice another post mentioning its a possible bug, but I'm not sure my situation is the same.

Data source error{"error":{"code":"DMTS_OAuthFailedToGetResourceIdError","pbi.error":{"code":"DMTS_OAuthFailedToGetResourceIdError","details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Failed to get OAuth resource, please make sure the OAuth is supported"}}],"exceptionCulprit":1}}} Table: Attainment (Progress Model).

Cluster URIWABI-UK-SOUTH-redirect.analysis.windows.net

[v-hashadapu]

Hi @jonmorgan , Hope you're doing fine. Can you confirm if the problem is solved or still persists? Sharing your details will help others in the community.

[v-hashadapu]

Hi @jonmorgan , Hope you're doing okay! May we know if it worked for you, or are you still experiencing difficulties? Let us know — your feedback can really help others in the same situation.

[v-hashadapu]

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.

[jonmorgan]

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.

[v-hashadapu · Accepted solution]

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

[jonmorgan]

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.

[GilbertQ]

Hi @jonmorgan 

Further to that, what I would recommend you do is find your Power Query data source and see what is supported in terms of refreshing in the Power BI service. List of all Power Query connectors - Power Query | Microsoft Learn

[tayloramy]

Hi @jonmorgan,  

This error means the service failed to obtain a valid OAuth "resource" for one of your data sources during a refresh in the cloud. That usually happens when the connector or auth path you used in Desktop is not fully supported for service refresh, the OAuth setup requires same-tenant access, a viewer-owns-data/SSO toggle is misapplied, or cached credentials became invalid. Because the engine fails wherever it is in the refresh, a different table can show up as the culprit each run. See Microsoft’s refresh/OAuth notes (docs) and a community thread showing the exact message (example).

Here are some things to try:

1. Re-enter credentials for every source in the dataset settings and Save. If you see the checkbox "Report viewers can only access this data source with their own Power BI identities using DirectQuery," toggle it off temporarily to test with stored credentials. This specific combo has resolved the same error for others (community solution, toggle explained).
2. Confirm your OAuth path is supported in the Service and meets the same-tenant requirement. Cross-tenant OAuth connections are not supported for refresh (docs).
3. Avoid mixed auth methods per host, then republish after clearing Desktop permissions 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.