web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Power Automate SharePo...
Power Automate
Suggested Answer

Power Automate SharePoint Connection Error 404 - "Connection not found" despite reconnecting

(0) ShareShare
ReportReport
Posted on by
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:
I have the same question (0)
  • Suggested answer
    Sunil Kumar Pashikanti Profile Picture
    2,211 Moderator on at

    Since you have already tried the standard approaches of recreating the connection and the flow, this is no longer a surface-level UI issue. The error indicates that during runtime execution, the flow engine is still resolving a stale, invalid, or cached connection token behind the scenes.

    When working with SharePoint triggers, the platform creates a background webhook subscription. If that subscription becomes tied to an old connection or gets corrupted, updating the connection in the UI will not resolve the issue.

    To isolate and confirm the root cause, try the following:
     
    1. Run a trigger isolation test
    Create a new test flow with:
    • Manual trigger
    • SharePoint “Get items” action
    If this works but the automated trigger fails:
    Your connection and permissions are fine. The issue is a corrupted webhook tied to the trigger.
    Fix: delete the trigger from your original flow, save the flow, then add the trigger again and reconfigure it.
    If this also fails:
    Then the issue is deeper, likely related to permissions or authentication.
     
    2. Verify SharePoint permissions
    Opening the site in a browser does not always guarantee API access.
    Make sure your account has:
    • Direct Edit permissions on the specific list
    Avoid relying only on:
    • Group membership
    • Inherited permissions
    3. Check tenant-level policies
    Since you are using a non-admin account, this could be caused by:
    • Data Loss Prevention (DLP) policies
    • Conditional Access rules
    These can block connector calls while still allowing normal browser access.
    To confirm, ask an admin to run the same test flow:
    • If it works for them but not for you, it is a tenant-level restriction
    Final note
    At this stage, the issue is almost certainly not your flow design, but a combination of:
    • stale trigger/webhook metadata
    • or environment-level security constraints
     
     ✅ 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/
  • Suggested answer
    11manish Profile Picture
    3,052 on at
    The most probable cause is a stale or corrupted SharePoint connection reference that Power Automate is still trying to use, even after creating new connections.

    If a completely new flow with a completely new SharePoint connection produces the same error, the issue is likely at the environment or tenant level, and your
     
    administrator may need to investigate further or raise a Microsoft support ticket.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 462

#2
Vish WR Profile Picture

Vish WR 256

#3
David_MA Profile Picture

David_MA 242 Super User 2026 Season 1

Last 30 days Overall leaderboard