Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Logic Apps (Standard) - Managed Identity practical usage in VS Code

See original GitHub issue

When in Visual Studio code, and using Managed Identity somewhere in your workflow, for instance, on a HTTP action, the following error will display while debugging:

Workflow Error: operationName='WorkflowDefinitionProvider.ProcessWorkflow', message='Workflow 'workflow-inbound-dynamic-action' validate and create workflow operation failed, 
the exception is 'The operation 'HTTP' for workflow 'workflow-inbound-dynamic-action' contains managed identity authentication which is supported only for Logic Apps Standard or Logic Apps running in App Service Environments.'', 
The operation 'HTTP' for workflow 'workflow-inbound-dynamic-action' contains managed identity authentication which is supported only for Logic Apps Standard or Logic Apps running 
in App Service Environments.

Will this be supported somehow? This currently means you cannot debug your project when you use a Managed Identity somewhere in a workflow. Not very practical. I guess I understand why it’s not working, because I’m not running it inside Azure, but locally.

As an alternative approach: Wouldn’t implementing DefaultAzureCredential inside Logic Apps (standard) be a better option? That way you are not dependent on credentials on a specific environment.

Another approach: Able to point to a deployed managed identity, similar as how you point to a resource group for API connections (WORKFLOWS_RESOURCE_GROUP_NAME), inside the local.settings.json, so it will try to authenticate with that.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:2
  • Comments:6

github_iconTop GitHub Comments

John-Boschcommented, Feb 22, 2022

This is a real limitation that needs to be fixed. The whole point of managed identities is to not need to manage the App Registrations. This is now forcing us back down the path of not using managed identities at all if we want to be able to debug locally.

github-actions[bot]commented, Oct 28, 2022

This issue was closed because it has been inactive for 7 days since being marked as stale.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Create Standard workflows with Visual Studio Code
This how-to guide shows how to create an example integration workflow that runs in single-tenant Azure Logic Apps by using Visual Studio Code...
Read more >
Logic Apps Standard, Managed connections in Visual Studio ...
Today(June 2022), handling managed connections while developing Logic Apps standard in Visual Studio Code is not straight forward.
Read more >
Interacting with Key Vault from Logic Apps securely
By using a Managed Identity, the Logic App will create an enterprise application itself and will manage the secrets it's self. This means...
Read more >
Using connections with managed identities during local ...
Yes, you can enable managed identity for local logic app. You can use already created api connection while connecting to storage or you...
Read more >
How to Use Managed Identities in Your Azure Logic Apps
A managed identity is an object in Azure Active Directory (Azure AD), which can be used by the Azure resources to establish the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found