DMTS_OAuthFailedToGetResourceIdError

[fvquicke]

I encountered this rather unclear error while attempting to refresh a dataset.

{"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}}}

In another dataset, I’m using the same resources and settings and the updates work perfectly.  However, in this dataset, they’re not working and I’m struggling to identify the cause.  We’re using Web and OData resources from the Dyn365 environment. Can you help us figure this out?

[v-hjannapu]

Hi @fvquicke,

I would also take a moment to thank @rohit1991  , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Regards,
Community Support Team.

[v-hjannapu]

Hi @fvquicke,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We are always here to support you.


Regards,
Community Support Team.

[rohit1991 · Accepted solution]

Hii @fvquicke 

This error appears when Power BI Service cannot determine the correct OAuth resource for your Dynamics 365 OData/Web API connection. Desktop works, but the Service refresh fails because the token cannot be resolved.
Try the following fixes (one of these usually resolves it):

1. Re-authenticate the dataset in Data Source Credentials using OAuth2 >> Organizational Account.

2. Make sure all queries use the exact same Dynamics base URL (even a missing “/” can break OAuth).

3. Ensure all queries use OAuth, and no queries are using Anonymous/Web authentication.

4. Align privacy levels (set them to Organizational).

5. Remove any unnecessary gateway mapping  D365 does not require a gateway.

This issue typically comes from a URL or credential mismatch, not the Dynamics environment itself.