Power Platform Community Forum Thread Details

Hello everyone,

I'm facing a persistent issue with Power Automate
when trying to connect to SharePoint.

**The Error Message:**
"The dynamic invocation request failed with error:
status 404 - Error from token exchange:
The connection is not found.
Please create new connection and change your
application to use the new connection."

**What I have tried:**
- Deleted ALL existing SharePoint connections
- Created multiple new SharePoint connections
- Deleted the entire Flow and created a new one
- Tried in Incognito browser mode
- Used "Change connection reference" option
- All connections show "Connected" status (green)
but the error still appears

**My environment:**
- Account: Microsoft 365 (non-admin user)
- Region: Saudi Arabia
- The SharePoint site opens normally in the browser
- Power Automate trigger: "When an item is
created or modified - SharePoint"

**Question:**
Is this a permissions issue for non-admin users?
Or is there another fix?

Any help is appreciated. Thank you!

لقطة الشاشة 2026-...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

AI Builder

Hi @MA-19060218-0,

This error usually means that even though the UI shows a healthy connection, the flow is still internally referencing a stale or deleted connection ID.

When you recreate a connection, Power Automate doesn’t always update the backend bindings correctly, which leads to this “Connection not found” error.

What to do
1. Force update the connection reference (important)
If your flow is inside a solution:

Go to Solutions → Your solution
Open Connection References
Find the SharePoint connection
Edit it and explicitly select your new connection
Save
Turn the flow off and back on

2. Recreate the SharePoint trigger
Triggers often keep old connection/webhook bindings.

Delete the trigger
Add it again
Reconfigure Site + List

3. Check permissions and identity
Make sure:

You have proper access to the SharePoint site/list
The connection is using the correct account
No mismatch between flow owner and connection

4. Quick isolation test
Create a simple flow outside a solution with the same trigger:

If it works → issue is connection reference binding
If it fails → likely permissions or environment issue

Summary
Even after reconnecting, flows can still point to old connection IDs behind the scenes.
Fix is to force rebind the connection + recreate the trigger.

✅ If one of the responses here solved your issue, please mark it as Accepted so others facing the same problem can benefit as well.
👍 If this or any other reply here helped you, feel free to give it a Like. It helps others and is always appreciated.

Sunil Kumar Pashikanti, Moderator
Blog: https://sunilpashikanti.com/posts/