Did you know that you can access Consumption connectors in Visual Studio Code? When you create a Logic App Standard workflow in VS Code, you may notice that some familiar connectors from the Azure Portal designer are missing. At first, this difference can feel confusing. However, there is a clear reason for it.
Visual Studio Code focuses on designing Logic Apps Standard. Although VS Code also supports Consumption Logic Apps, it does not integrate them as deeply as it does Standard workflows.
📝 One-Minute Brief
When building Azure Logic Apps Standard in Visual Studio Code, you may notice that familiar Consumption connectors are missing from the designer. This Friday Fact explains why only in‑app connectors appear by default, how you can unlock Consumption connectors directly from Visual Studio Code, and when it makes sense to use them alongside in‑app connectors in Logic Apps Standard workflows.
In the Azure Portal, the Logic App Standard designer gives you access to both in‑app and Consumption connectors. In contrast, Visual Studio Code shows only in‑app connectors by default.
This behavior exists by design. In‑app connectors provide better isolation and performance because they run in the same environment as the Logic App. As a result, they reduce network latency and give you more control.
For example, if you search for Blob Storage connectors in the Azure Portal, you can find Create blob (V2). However, when you perform the same search in Visual Studio Code, that connector does not appear.
We did the same search, but the result was different, and the connector was not found, but fortunately, the Designer features an equivalent connector (Upload blob to storage container)
So, how can we get access to the consumption connectors on Visual Studio Code?
It is easy, right mouse click over your workflow and click on Use Connectors From Azure:
Next, select again Use Connectors From Azure on the search bar, and select your Resource Group.
After this, you will be ready to use them. For some reason, they do not appear, close the designer, and open it again:
It is also worth noting that Logic App Consumption connectors run in a shared, multi‑tenant environment across multiple customers. Azure fully manages these connectors, which gives you less control over where and how they run. As a result, they do not provide the same in‑app isolation available in Logic Apps Standard.
In contrast, this separation in Logic Apps Standard gives you tighter control over the integration environment and represents one of the key differences between the two hosting models.
To lazy to read? We’ve got you covered! Check out our video version of this content!
Hope you find this helpful! If you enjoyed the content or found it useful and wish to support our efforts to create more, you can contribute towards purchasing a Star Wars Lego for Sandro’s son!
