This is a well-documented issue with two separate root causes.
Root cause 1: File ID format mismatch between connectors
Microsoft docs confirm: the OneDrive for Business connector and the Excel Online Business connector use different internal file identifiers.
The OneDrive connector returns an Id property, but the Excel Online Business connector expects a File Identifier property. These are not always interchangeable and the difference only surfaces for other users because your OneDrive is already fully provisioned while new users' personal SharePoint sites may not be.
In your Create Table action, instead of using the Id output from Create File, use the Path output (the full file path) or the File Identifier output specifically.
The path-based reference is more reliable across users than the GUID-based Id.
Root cause 2: Personal SharePoint site not yet provisioned
When a user's OneDrive/personal SharePoint site hasn't been fully provisioned, the Excel Online Business connector (which routes through Microsoft Graph and SharePoint) can't find the file even though the OneDrive connector can create it. The OneDrive connector uses a different API path that works before full provisioning. Adding a Delay of 10-15 seconds between the Create File and Create Table actions can resolve this for affected users.
The confirmed fix combination:
1. Change the File input in Create Table from the Id output to use the full path expression:
@{outputs('Create_file')?['body/Path']}
2. Add a 15-second Delay between Create File and Create Table
3. If still failing for specific users, they need to open OneDrive once in their browser first to trigger site provisioning
Best regards,
Valantis
✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.
❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).
🏷️ For follow-ups @Valantis.
📝 https://valantisond365.com/
