Error getting OData from Microsoft Graph: Access to the resource is forbidden

I have the exact issue. Using  OData.Feed("https://graph.microsoft.com/v1.0/users") succesfully for months in PowerBI.com with 8 scheduled refreshes per day. First refresh of  June 1st give an  "Access to the resource is forbidden" error messages.

When I test it on https://developer.microsoft.com/en-us/graph/graph-explorer I have no issue.

Any suggestion is welcome.

Hi jevgenijmartpbi_2e,

I have reported this issue internally: CRI 71609700. Will update here once I get any information. 

Best Regards,
Qiuyun Yu

v-qiuyu-msft, thanks. Keep is posted.

I'm awaiting the response here, too.

I've got multiple client reports that are using Graph for their row-level security, and this has production reports in stasis. Thanks for looking into this, v-qiuyu-msft.

eagerly waiting a solution, same issue for me.. i no longer have access to graph api from powerbi desktop using odata or web connectors.

@v-qiuyu-msft, thanks for loooking into this.

While waiting for the solution, do you think we could have some kind of the workaround?

For example, would Web API authentication work?

jevgenijmart thanks for raising the issue. v-qiuyu-msft thanks for looking into it. I thought I was going mad trying to figure out why this had started to happen in my reports!! Look forward to hearing about a  resolution :-)

I'm having the same issues.

Possible culprit may be that in the June release of PowerBI upgraded the OData drivers to version 4, but the MS Graph doesn't consistently supoort v4 of OData across allthe services.

Any work-around would be appreciated, I can't restrict updates to the end users' powerbi desktop

Anonymous, this was an issue before June release popped, and I verified that it's broken on the May release as well. I originally had this issue last Thursday, May 31st. It seems like most people collectively woke up this Monday to finally see that their Graph-based queries were broken.

Anonymous nice idea.

But yeah, I was getting the issue since Thursday, May 31st.

It feels like it has something to do with some changes on Azure/Graph API side