Odata refresh fails because expiration of the aad token

[Bekkertje]

Can anyone help me out? Its really frustrating for me and our customer, tried everything, the problem is described perfectly by Microsoft:

Refresh fails when updating data from sources that use AAD OAuth The Azure Active Director (AAD) OAuth token, used by many different data sources, expires in approximately one hour. You can run into situations where loading data takes longer than the token expiration (more than one hour), since the Power BI service waits for up to two hours when loading data. In that situation, the data loading process can fail with a credentials error. Data sources that use AAD OAuth include Microsoft Dynamics CRM Online, SharePoint Online (SPO), and others. If you’re connecting to such data sources, and get a credentials failure when loading data takes more than an hour, this may be the reason. Microsoft is investigating a solution that allows the data loading process to refresh the token and continue. However, if your Dynamics CRM Online or SharePoint Online instance (or other AAD OAuth data source) is so large that it could run into the two-hour data-load threshold, you may experience a data load timeout from the Power BI service as well.

But I havent found any solution so far.. Please help me out asap

[lacol]

Currently experiencing this as we've enabled MFA due to the coming changes at the end of September, no information at all from the Power BI team about this? At all? nothing? 5 years?!

[Anonymous]

Any update? It's been almost 5 years now.

[Anonymous]

Issue with token expiring after 1 hour · Issue #2857 · MicrosoftDocs/powerbi-docs (github.com)

https://docs.microsoft.com/en-us/power-bi/connect-data/refresh-troubleshooting-refresh-scenarios#ref...

[v-yulgu-msft]

Hi @Bekkertje,

Unfortunately, the Odata refresh is limited into one hour. And there is no workaround right now. Our product team is working on the fix, investigating a solution that allows the data loading process to refresh the token and continue. Appreciate for your patience.

Thanks,
Yuliana Gu

[Bekkertje]

Then is there any way to filter the data in the new o data link? I found out a way for the old XRMServices links like in the screenshot below, but is there also a way to use a filter in the new link?

https : / /.u• api.crm.dynamics.com/XRMServices/2011/0rganizationData.svc/AccountSet ? 

$se1ect—AccountId , Name , Addressl_StateOrProvince , Addressl_City , Ownerid &$filter= Address1_StateorProvice eq 'CA' 

Address1_StateOrprovince eq • CA' 

Or any other workarround with odata? I have limited my data set, but the odata seems to get all the data (not doing any query folding) instead of what i filter when i do a refresh

[Jeanxyz]

I have used Odata connection a few times, the truth is Power BI is very slow with Odata connection. I also find if the source data is stored on sharepoint, even if you pick data source as SharePoint, the connector behind is still Odata. So you need to be careful when your source data is stored on SharePoint. In my experience, when there are only a few source files stored on SharePoint, data refreshing speed is still ok, but with the increase of numbe rof SharePoint files, the refreshing speed will suddenly deteriorate. 

I hope very much Microsoft will find a way to solve the Odata connection, or at least improve the data connection between SharePoint and Power BI.