Issue with accessing Excel data with Onedrive for Business Connector

(0) Share

Report

Posted on by Hayden1980

We have a few apps that access a shared excel spreadsheet in a shared Onedrive for business location. These apps have been working correctly for several years, however yesterday all users with the exception to the user who owns the Onedrive account receive the following error:

Failed to load Table1. The specified record was not found. Server response: Table1 failed: Failed to read metadata from file sources. Response from the end service is: Not Found clientRequestID

All users still have full access permissions to the Onedrive location and the excel file and the owner account of the onedrive location doesn't have this error.

Was there an update for the Onedrive for business connector which may be causing this?

Categories:

Building Power Apps

I have the same question (17)

All responses (5)

Answers (0)

Sort by

Hayden1980 6 on at

Like (0)

Report
Copy link

Link copied!

Noticed this post: My App can no longer be reached by users so I'm not alone

Was this reply helpful? Yes No
Nate0173 51 on at

Like (0)

Report
Copy link

Link copied!

Nope, you are not alone. We are having the same issue which started on 8/20/25. Our Power Apps with Excel data source stored on OneDrive were working fine for years though 8/19/25. Then, suddenly users cannot access the data (same error message). This is a consistent problem for all apps with an Excel data source stored on OneDrive.

Was this reply helpful? Yes No
JM-20080836-0 23 on at

Like (0)

Report
Copy link

Link copied!

We are facing exactly the same issue, also identified with the OneDrive for Business connector in PowerApps since around August 19/20.

It only works when the app is launched by the owner of the OneDrive.

We have already opened a support ticket with Microsoft — they confirmed they are investigating the problem.

I suggest you do the same so they take this issue seriously and speed up the resolution.

Was this reply helpful? Yes No
WarrenBelz 155,487 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @Hayden1980,

The easiest longer-term fix is to move the file to SharePoint. User access control is far more robust in that environment.

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it a Like♥.
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No
Suggested answer

JM-20080836-0 23 on at

Like (0)

Report
Copy link

Link copied!

✅ Quick update: everything is working again since this morning.

I received the following details from Microsoft support:

Issue Summary:
Our Product Group (PG) has completed their investigation and identified the root cause. The issue stems from the use of the "cross-drive" scenario, which involves accessing files shared from another user's OneDrive. This scenario is explicitly listed as Not Supported in Microsoft’s documentation:
https://learn.microsoft.com/en-us/connectors/onedriveforbusiness/#known-issues-and-limitations

Recent Change:
While this functionality previously worked, it was never officially supported. A recent update by PG now enforces this limitation, resulting in the current disruption.

Temporary Mitigation:
To unblock critical workflows, PG has implemented a KillSwitch that temporarily reverts to the old behavior. This is a short-term fix and should not be relied upon for future solutions.

Recommended Long-Term Solution:
PG strongly recommends transitioning to the SharePoint Connector for accessing files shared from other users’ sites. This approach is supported and aligns with Microsoft’s best practices.

Please ensure your teams are aware of this change and begin planning updates to any flows or solutions that currently depend on the "cross-drive" scenario.

Was this reply helpful? Yes No