Accessing a shared company OneDrive folder in Make — Site's Drive fails, but My Drive works

Questions
1

:bullseye: What is your goal?

I want to use Make to access and process files from a company OneDrive folder that was shared with me by a colleague. The folder opens correctly in the browser from the sharing email, and I want to use it as a source in my scenario.

:thinking: What is the problem & what have you tried?

A colleague shared a folder with me from his company OneDrive. I can open it in the browser without any issue, and the URL shows it is hosted under a business Microsoft environment (…sharepoint.com/personal/…).

In Make, I tried to access it through the OneDrive module.

What I tested:

I first tried Site’s Drive, because the folder belongs to another user and is hosted in a SharePoint/OneDrive Business environment.
However, Make could not load the Site ID and returned an API error.
Then I switched to My Drive and surprisingly the shared folder/item appears there and can be selected.

So at the moment I am unsure what the correct / reliable setup is:

should shared folders from another user’s OneDrive be handled through My Drive,
or should this normally work through Site’s Drive,
or is my connection configured in a wrong way.

I would like to understand the correct approach before building the whole scenario on top of this.

:clipboard: Error messages or input/output bundles

Error messages or input/output bundles
Error received when trying to use Site’s Drive in the OneDrive module:

{
“message”: “[400] This API is not supported for MSA accounts (no addressUrl for Microsoft.MicrosoftSearch, False).”,
“details”: [
“Failed to load data!”,
“Value must not be empty.”
]
}

Additional context:

The shared folder opens correctly in browser.
The URL looks like this pattern:
https://-my.sharepoint.com/personal/_…/
In Make, Site’s Drive fails with the error above.
In Make, My Drive is able to see/select the shared folder.

3

Hey there,

there isn’t one. Microsoft’s products are notoriously bad at handling API access (or working at all for that matter) so whichever way you managed to get it to work, just leave it like that and don’t touch it any more unless it starts giving errors.

But yeah, if the file was shared with you, then My Drive is the way to access it. And if it is not visible under the Site’s Drive, then it maybe wasn’t generically shared with everyone?