Using SharePoint to Connect to Power Automate error

(1) Share

Report

Posted on by DM-17062001-0

Hello,

Description of Issue

I’m encountering a “Folder Not Found” error in Power Automate when attempting to access a SharePoint/OneDrive folder within my flow.

Error details:

Error message: Folder Not Found

clientRequestId: bb9239e1-65be-4ebc-b692-a14eacb4cfdc

serviceRequestId: 637c20a2-e0f8-1000-d4a8-584a8e91a95f

What I’m Trying to Do

I am attempting to:

Access or retrieve files from a specific folder

The folder is expected to exist in SharePoint / OneDrive (used for external sharing / document storage)

Questions / Help Needed

Could this error be caused by:
- Incorrect internal path vs display name?
- Connection or authentication issues?
- Timing/sync issues with newly created folders?

Are there known issues where Power Automate cannot resolve folders that exist in SharePoint or OneDrive?

Can someone guide me through this if there's be a more technical fix for this issue?

Appreciate the help!

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Ellis Karim 12,137 Super User 2026 Season 1 on at

Like
a
(2)

Report
Copy link

Link copied!

We need more details to help you! Please share a screenshot of your flow, showing the configured actions. If there’s an error, tell us which action failed and include the error message. Be careful not to include any sensitive or personal information. This will help us understand the issue and provide a solution faster. Thank you!

Ellis Karim
elliskarim.com | LinkedIn | Bluesky
If this solved your issue, please mark it as ✅ Accepted Answer. If it helped, feel free to give it a 🩷 Like!

Was this reply helpful? Yes No
Suggested answer

11manish 3,148 on at

Like
a
(0)

Report
Copy link

Link copied!

The most likely causes are either an incorrect internal folder path, a dynamically generated path containing unexpected characters/spaces, or timing issues when accessing a newly created folder. Start by logging the exact folder path with a Compose action, verify it manually in SharePoint/OneDrive, and test with a hardcoded path. If the folder is created earlier in the flow, add a short delay or retry mechanism before attempting to access it. This usually identifies the root cause quickly.

Was this reply helpful? Yes No
Suggested answer

Vish WR 3,685 on at

Like
a
(2)

Report
Copy link

Link copied!

@DM-17062001-0

Good points already raised above. To add to that, the fastest way to isolate this is to drop a Compose action just before the failing step and log the exact folder path value being passed in at runtime. Manually typed or dynamically built paths are the most common reason for this error, even when the folder clearly exists in SharePoint.

Also worth confirming: are you using the SharePoint connector or the OneDrive for Business connector? They handle folder paths differently and a folder shared externally may resolve fine in SharePoint but not via OneDrive and vice versa.

If you can share a screenshot of the failing action and the path value from the Compose output, that will make it much easier to pinpoint exactly where it is breaking.

Vishnu WR

LinkedIn - My Tech Space

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 answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
DM-17062001-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Was this reply helpful? Yes No