You’re offline. This is a read only version of the page.
Hi all,
I have an Azure VM in a VNet with a Private Link endpoint, the Private Link service being presented to the VNet is an Azure Storage File Share. Using Storage Explorer/net use I can map the network drive using the access key OK as per the connection script.
The scenario I have though needs a flow to be able to check this file share using the File System data connector, so I have installed the On-Premise Data Gateway to this VM and Power Automate can access this OK and reference local files. When I attempt to access the file share with the same credentials though I get the following;
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: xxxx-xxx-xxxx-xxx", "error": { "message": "The credentials for this connection do not have access to '', please try using a different location or account." }, "source": "filesystem-uks.azconn-uks-01.p.azurewebsites.net" }.
I have tried various different combinations of username/password but this does not seem to make a difference - If I attempt to use a local account to access the mapped drive I get;
The dynamic invocation request failed with error: { "status": 400, "message": "The requested action could not be completed. Check your request parameters to make sure the path '' exists on your file system.\r\nclientRequestId:xxxx-xxx-xxxx-xxx", "error": { "message": "The requested action could not be completed. Check your request parameters to make sure the path '' exists on your file system." }, "source": "filesystem-uks.azconn-uks-01.p.azurewebsites.net" }.
If I use the local account to access a local folder or share on the VM it works fine.
Does anyone know if it is feasible to access an Azure File Share using the OPDG running in Azure?
Thanks
Thanks Javier,
I have connected the Azure file share successfully as per your linked doc (bearing in mind it's hosted via Private Link) to the VM as Z:\ and can confirm that Windows is able to browse it OK. When I then attempt to access it using Flow via the On-Premise Data Gateway though I receive the following;
The dynamic invocation request failed with error: { "status": 404, "message": "There is no folder '' located on your file system. Verify the folder exists or create it before trying to access it.\r\nclientRequestId: xxxx-xxxx-xxxx", "error": { "message": "There is no folder '' located on your file system. Verify the folder exists or create it before trying to access it." }, "source": "filesystem-uks.azconn-uks-01.p.azurewebsites.net" }.
In the data connector config I have set the Root Folder to Z:\ and using the local VM credentials which the OPDG service is running under.
Again, setting the data connector in Flow to use the UNC network path and credentials of the storage account prefixed by AZURE\ for the domain gives me;
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: xxxx-xxxx-xxxx", "error": { "message": "The credentials for this connection do not have access to '', please try using a different location or account." }, "source": "filesystem-uks.azconn-uks-01.p.azurewebsites.net" }.
Hi CraigMck,
I would like to share this document with you.
https://docs.microsoft.com/en-us/azure/storage/files/storage-how-to-use-files-windows
I hope it can helps you.
Javier
#1
WarrenBelz
146,651
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,999
Most Valuable Professional
Share
Report
All responses (
Answers (
