How to enable API Management Connector inside VS Code Logic App Standard Workflow Designer

If you’ve been working with Azure Logic Apps Standard in Visual Studio Code and noticed that the API Management connector is conspicuously absent from the list of connectors inside the workflow designer, you’re not alone. This is a typical behavior that many developers encounter, and understanding why it happens—and how to enable it—can save you a lot of headaches.

The issue

So, if you create a new Logic App Standard project or open your existing project inside VS Code, and if you try to add an action and cannot find the API Management actions/connector from the Add an action panel:

Don’t panic or start worrying. This behavior is completely normal for this connector.

At first glance, it may look strange or even like a bug. After all, this is a built‑in connector, and it does not appear as expected. Naturally, you might expect it to show up in the list. However, this isn’t a bug. Instead, Microsoft designed this behavior intentionally as a custom feature of the connector.

The solution

To enable the API Management connector, we need to:

• Right-click on top of one workflow and select the option Use Connectors from Azure –> We are not really going to work with management Azure connectors, but we need their behavior 🙂

• This will ask you to select a Subscription and the Resource group.
  • Choose the subscription and resource group where you will publish this project — it doesn’t need to match API Management.
• After that, it is IMPORTANT to close all the workflow designers you have open inside VSCode.
• Now, we need to open the workflow designer again. It will ask you to authenticate in Azure — use your account.
• After that, if you try to find the API Management connector, it will be present.

This behavior occurs because the API Management connector needs access to Azure to load existing APIM instances and the correct APIs. So, although it is a “built-in” connector, it requires Azure connectivity to run. Once we enable the Use Connectors from Azure step, the connector will appear on the list and behave as expected.

If you liked the content or found it helpful and want to help me write more, you can buy (or help buy) my son a Star Wars Lego set! 

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community. View all posts by Sandro Pereira