question

DKarir-7188 avatar image
0 Votes"
DKarir-7188 asked PramodValavala-MSFT commented

New Logic App (Standard) - File System Connector

I was under the impression that the new single-tenant based Logic App (Standard) will allow for on-prem access without a data gateway. When I add a File Connector in VSCode to the workflow, I can connect to a local file share server (at least it shows "Connected") but I get the below error when I try to browse the Folder Path.

Can someone please guide me on what I am doing wrong?

Error code: '400', Message: 'Key 'gateway' not found in connection profile. clientRequestId: F58EE695-B57C-4D56-AC55-XXXXX'. More diagnostic information: x-ms-client-request-id is 'F58EE695-B57C-4D56-AC55-XXXXXX'.


azure-logic-apps
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

PramodValavala-MSFT avatar image
1 Vote"
PramodValavala-MSFT answered PramodValavala-MSFT commented

@DKarir-7188 While built-in connectors work within the single tenant runtime, managed connectors are still hosted and run from Azure as mentioned in the capabilities section of the docs.



· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@PramodValavala-MSFT, thanks for your response. Just to clarify, does that mean I need to deploy my Logic App (Standard) to Azure (example: Premium Service Plan) and leverage VNET connectivity to test the File System connectors capabilities and that I cannot debug locally in VSCode if I'm using managed connectors?

0 Votes 0 ·

@DKarir-7188 While you Logic App could be deployed anywhere, the Managed Connector (running on Azure) itself needs access to your File System either directly (public) or via the On Premises Data Gateway as usual.

0 Votes 0 ·