Hi @Sangram Chaware ,
Thanks for bringing your concern to us below is the information which might help you in resolving your concern.
Below are the Prerequisites for both the Consumption and Standard Workflow: To connect to your file share, different requirements apply, based on your logic app and the hosting environment:
Consumption logic app workflows in multi-tenant Azure Logic Apps, you need to meet the following requirements, if you haven't already:
- The File System managed connector requires that your gateway installation and file system server must exist in the same Windows domain. After you add a File System managed connector trigger or action to your workflow, select the data gateway resource that you previously created so you can connect to your file system.
Standard logic app workflows You can use the File System built-in connector or managed connector. To use the File System managed connector, follow the same requirements as a Consumption logic app workflow in multi-tenant Azure Logic Apps.
To use the File System built-in connector, your Standard logic app workflow must run in App Service Environment v3 but doesn't require the data gateway resource.
And below are the limitations of Built-in connector:
- For a new connection, the built-in connector expects a fully qualified domain name, unlike the managed connector, which uses the machine name in the root path.
- The built-in connector supports up to 20 connections maximum for a Standard logic app resource and the built-in connector doesn't support duplicate connections, which have the same root folder path, with different credentials. Although connection creation succeeds, the new connection continues to use the credentials from the previous connection.
Thankyou.