Showing results for 
Search instead for 
Did you mean: 
Advocate III
Advocate III

'Forbidden' Error Copying a file from SharePoint to On-Premises (using On-Premises Data Gateway)

I am trying to use the File System - Copy File action to move a file from SharePoint to an On-Premises File System.  Maybe some of you have seen a similar issue.


  • I have installed the On-Premises Data Gateway on my development machine (Windows 10 Pro)
    • I am logged in with my Azure AD account
    • I registerd this with the same account I have provided credentials for in the Flow 'Copy File' action
  • I am using a SharePoint action to get the Link of the file which I am copying


Flow Design


Error Trace


In the failure summary, I can see the details of the issue.  It tells me that the provided credentials don't have access to the target path.  This looks suspect to me - why does it switch the direction of the slashes before the file name? 




The outputs file is showing the following errors:

  • "body":{"status":403,"message":"403 FORBIDDEN\r\nclientRequestId:
  • Without further details

The local On-Premises Data Gatewaty logs showed this error:

Microsoft.Data.Mashup.MashupCredentialException (0x80004005): The credentials provided for the Folder source are invalid.


 I've troubleshot this (so far) by:

  • Looking at the Output logs provided by Flow
  • Reinstalling the OPDG (more than once)
  • Reconfiguring the OPDG connection on the Flow action  (more than once)
  • Reviewing the local Flow logs on the target machine.


Has anyone encountered issues similar to this? 

Advocate III
Advocate III

In Flow, when working with File System actions, you need to create a connector to your On-Premises Data Gateway.  Here is the screen. 


Configuring the Flow On-Premises Data Gateway Connector.png


In the fields for Username and Passowrd, you have to put the credentials in the domain\login pattern.  I was failing when I entered the credentials as  After recreating the connection using these credentials, I was able to connect using the On-Premises Data Gateway. 


Also - you can use the PowerShell command below to return the logged on domain and user: 



After making this change, I was able to use the File System - Create File action successfully, but not the File System - Copy File action. 

Community Support
Community Support

Hi @panterra,


Could you please share a screenshot of your flow’s configuration?

The issue is confirmed on my side. I think the File System connector have no access to the file in SharePoint with “Link to item” content. Only the people who are assigned with proper access could access the file in SharePoint.


Besides, if you want to copy file from SharePoint to local folder, please take a try with the alternative way as below:17.JPGThe flow works successfully as below:18.JPG


Best regards,


Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

I had the same Forbidden error and this solution worked for new files saved to the folder or e.g. right click -> New - Text Document, but failed for files pasted into the folder.

Helpful resources

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

New Ideas Forum MPA.jpg

A new place to submit your Ideas for Power Automate

Announcing a new way to share your feedback with the Power Automate Team.

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

MPA Licensing.jpg

Ask your licensing questions at the Power Automate AMA!

Join Priya Kodukula and the licensing team, super users and MVPs to find answers to your questions on Power Automate licensing.

Users online (5,913)