Standard Logic app - built-in connector file system create connection mountpath

Shawn 91 Reputation points
2023-04-07T11:17:52.82+00:00

Hi All, I am trying to connect to the on-prem. file system using 'File system' built-in connector. When I specified the root folder and created a connection, User's image

the FileSystem_mountpath is created under Configuration with the value 'C:\mounts\fileSystem. User's image

When I tested the connection, I got the following error. {"statusCode":"Unauthorized","body":{"code":"ServiceProviderActionFailed","message":"The service provider action failed with error code 'Unauthorized' and error message 'Access to the path 'C:{filepath from the action}' is denied.'."}} Is my setup okay? or should I remove C: ? because the on-prem file directory is not starting with C: but \{servername}\folder Thank you.

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,542 questions
{count} votes

1 answer

Sort by: Most helpful
  1. SnehaAgrawal-MSFT 22,706 Reputation points Moderator
    2023-04-11T14:12:22.27+00:00

    @Shawn Thanks for reaching here! It seems like you are facing an issue with the built-in connector file system create connection mount path. This error message usually occurs when the Logic App does not have the required permissions to access the specified file path. To resolve this issue, you can try the following steps:

    1. Check if the file path you are trying to access is correct and exists.
    2. Make sure that the account used to run the Logic App has the required permissions to access the file path.
    3. Check if the file path is accessible from the network where the Logic App is running.
    4. If you are using an on-premises data gateway, make sure that it is installed and configured correctly.

    Further you may want to know that the File System connector uses the App Service BYOS feature to mount the file share to a specific path. So, when a new connection is created, designer updates the config to mount the file share to C:\mounts<connection-id> and the mount path is then written to connections.json.

    The Logic Apps runtime only uses this mount path for any of the action/trigger executions.

    However please note that a connection created successfully still doesn’t guarantee that the mount was successful. Due to networking constraints of the file share/logic apps, the file share might still not be accessible from Logic Apps.

    Suggest you to check if the mount path exists from the file system through the Kudu console to ensure that the connection properly works. Please refer to below articles would be helpful: Using File system connector in Logic Apps Standard Connect to on-premises file systems from workflows in Azure Logic Apps Please let us know if further query or issue remains.    


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.