Showing results for 
Search instead for 
Did you mean: 
New Member

File System not connecting



I'm trying to create a flow to save specific email attachments into a network drive, but can't seem to get 'File System' to successfully connect to a file path.


I've set up a 'File System' connection, and put "[domain]\[user]" as my username, along with password and gateway.   I've verified the gateway connects successfully in the on-premises app.  However, every time I try to navigate the folder path in File System, it throws the following error:


"The dynamic invocation request failed with error: { "status": 403, "message": "The credentials for this connection do not have access to '', please try using a different location or account.\r\nclientRequestId: 79ce29a8-84e1-410a-885e-27e6-500f7b78", "error": { "message": "The credentials for this connection do not have access to '', please try using a different location or account." }, "source": "" }"
I've tried all iterations of user and domain (which seems to be a common issue), and tried using a local drive instead of a network drive, but all result in the same error.  Any ideas on how best to debug next?
Really appreciate any help!
Community Support
Community Support

Hi @cholland5,


Are you input the correct domain/username?

You could find your computer name via reading this document:

How to Find Your Computer Name | Information Technology | Drexel University

If the domain is "", the domain put in the file system connection should be "Atest".


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

Hi Lin Tu,

Thank you for the fast response! 


I can confirm I've tried this, also with many other varieties (user name vs machine name, "\" vs. "/", domain with and without ".org") but still get an error.


Are there other checks I can perform to verify compatibility?




Frequent Visitor

Hello Lin Tu,

I encountered status error 403 these days. In my case, it was because the account which I used to create the flow was not the same as the one I register the gateway. If this is the case, you have to reinstall the gateway and register the gateway using your flow account or vise versa.

Hope this would help

Frequent Visitor

If you are using any organization ID so try to give full ID with .com

example:\username for me it worked.


New Member

Exact same error, we are testing with some test .txt file.
  "message""The credentials for this connection do not have access to 'test.txt', please try using a different location or account.\r\nclientRequestId: 2ce95e0c-5ea5-4533-9df6-bcdddadcc51a",
  "error": {
    "message""The credentials for this connection do not have access to 'test.txt', please try using a different location or account."

Helpful resources

Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Community Calls Conversations

Community Calls Conversations

A great place where you can stay up to date with community calls and interact with the speakers.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Top Kudoed Authors
Users online (2,687)