Http request connectors with managed identity are not working locally (Logic App Standard)

[timjansenortec]

I am using a Http request with ManagedServiceIdentity to get a secret from a keyvault: "Some_Action": { "inputs": { "authentication": { "audience": "https://vault.azure.net", "type": "ManagedServiceIdentity" }, "method": "GET", "uri": "@{parameters('keyVaultUrl')}/secrets/SomeSecret?api-version=7.1" }, "runAfter": {}, "type": "Http" },

This gives the following error when running locally in Visual Studio Code: 'The operation 'Some_Action' for workflow 'XX' contains managed identity authentication which is supported only for Logic Apps Standard or Logic Apps running in App Service Environments.

Am I doing something wrong? Is this even a supported scenario? It would be nice if logic apps could get the identity from the context, the same way that DefaultAzureCredential does in a coded app (https://docs.microsoft.com/en-us/dotnet/api/azure.identity.defaultazurecredential?view=azure-dotnet).

[bydynamics]

Same issue, question. are managed identities (user) supported for the vs code local scenario?

[2022-07-26T15:47:34.411Z] Workflow Error: operationName='WorkflowDefinitionProvider.ProcessWorkflow', message='Workflow 'sb-employees_bc-employees-resources' validate and create workflow operation failed, the exception is 'The operation 'HTTPRunQueryAndListResultsTranslations' for workflow 'sb-employees_bc-employees-resources' contains managed identity authentication which is supported only for Logic Apps Standard or Logic Apps running in App Service Environments.'', exception='Microsoft.Azure.Workflows.Common.ErrorResponses.ErrorResponseMessageException: The operation 'HTTPRunQueryAndListResultsTranslations' for workflow 'sb-employees_bc-employees-resources' contains managed identity authentication which is supported only for Logic Apps Standard or Logic Apps running in App Service Environments

[timjansenortec]

As a workaround, I have written my own custom connector that internally uses DefaultAzureCredentials. This works fine. For me this is worth the effort, since I am doing a bunch of other things in the custom connector. For the most basic scenario, this is way too hassle.

In my opinion, using ManagedServiceIdentity should 'just' work when running locally in vs code.

[StefanPuntNL]

Same issue and question. @derek1ee Could you shed some light on this scenario?

[kseeman]

I'm also running into the same issue. Was anyone able to find a solution or is creating a custom connector the only work-around?

[rohithah]

managed identity is not supported when running locally. You need to either run this in azure or you can configure AAD authentication on the action either with clientId/Secret or a certificate

[simonp92]

Is support for managed identities in VSCode on the roadmap?

It would enhance the local development experience quite a bit