Skip to main content

Notifications

Announcements

Welcome to the Power Platform Communities
Check out the New Agent Creator Community
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate - Building Flows / "Get File Properties" ...
Power Automate - Building Flows
Unanswered

"Get File Properties" - Permission denied due to missing connection ACL: Connection

(2) ShareShare
ReportReport
Posted on by WBADAM03 177
Hi all,

I want to pull my hair out with this flow. 

I fixed a problem with the dependent flow and it ran fine for half a day, then suddenly the parent flow runs into an issue.

I have a "get file properties" step (sharepoint connector) that was working perfectly for several days, even when other parts of the flow were broken. I saw that all end users were able to use the flow yesterday. At around 9 PM, it just stopped working.

Permission denied due to missing connection ACL: Connection

Sometimes when I try to resubmit a flow it will say this:

Request to Azure Resource Manager failed with error: '{"error":{"code":"InvokerConnectionOverrideFailed","message":"Could not find any valid connection for connection reference name 'shared_sharepointonline_1' in APIM header."}}'.

I am at a loss. This is a mission critical flow that has just had error after error that ran for almost a year until this week everything broke. 

I deleted the entire sharepoint connection in power automate, remade the sharepoint connection, nothing, still have an error. 

Please let me know what I can do, I am at a loss.
Categories:
Business Process Flows
  • Suggested answer
    trice602 Profile Picture
    trice602 13,768 Super User 2025 Season 1 on at
    "Get File Properties" - Permission denied due to missing connection ACL: Connection
    Hi,
     
    I suspect the permissions (either user or library) have changed recently and is the root cause.  That's why it runs successfully (those that have the appropriate permissions) and fails for those that don't.  So while it's a problem with Power Automate, it seems to be more about SharePoint permissions that anything else.  Here's a few things to check - also do a root cause analysis and find one flow run that was successful and one that was not.  Verify the permissions for each user.
     
    If the flow stopped for everyone at 9 PM last night, it's most likely because someone changed the permissions for an entire group (guessing) or the library in question.  Hope this helps:
     

    Here are steps to troubleshoot and resolve this issue:

    1. Verify Permissions

    Ensure that the user account used for the connection has sufficient permissions to access the SharePoint site and the specific file library.

    1. SharePoint Site Permissions:

      • Go to the SharePoint site.
      • Click on "Site permissions" from the settings gear icon.
      • Check if the user has at least "Read" permissions to the site.

    2. Library Permissions:

      • Navigate to the specific document library.
      • Click on "Library settings" from the settings gear icon.
      • Under "Permissions for this document library", verify the user's permissions.

    2. Re-establish Connection

    Sometimes, re-authenticating the connection can resolve permission issues.

    1. Go to Power Automate.
    2. Click on Data from the left menu, then select Connections.
    3. Find the connection used in your flow (e.g., SharePoint connection).
    4. Click on the three dots next to the connection and select Edit.
    5. Re-enter the credentials and ensure the connection is successful.

    3. Update Flow with Correct Connection

    Ensure that the actions within the flow are using the correct connection.

    1. Open the flow in Power Automate.
    2. Edit the "Get File Properties" action.
    3. Check the "Site Address" and "Library Name" fields to ensure they are correct.
    4. Under the "Connection" section, make sure the correct connection is selected. If not, update it.

    4. Check Access Control List (ACL)

    Ensure that the connection has been granted the necessary access within the flow.

    1. Open the flow in Power Automate.
    2. Click on Settings (gear icon) for the action that is failing.
    3. Ensure that the "Run only users" permissions are correctly set. The user should have access to the connection.
     
    ------------------------------------------------


    ⭐ If this was helpful, please like and/or mark as a verified answer to help others find this too!


    Always glad to help! 💯💯💯💯💯

    Tom 

    Follow me on LinkedIn - Thomas Rice, PMP | LinkedIn

     

     

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

News and Announcements

Welcome to the Power Platform Communities
Check out the New Agent Creator Community

Quick Links

Michael Gernaey – Community Spotlight

We are honored to recognize Michael Gernaey as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard >

Last month Overall leaderboard

Featured topics

Start and wait for an approval action

Product updates

Microsoft Power Platform Community release plans