Skip to content
| Marketplace
Sign in
Visual Studio Code>Azure>Azure Logic Apps (Standard)New to Visual Studio Code? Get it now.
Azure Logic Apps (Standard)

Azure Logic Apps (Standard)

Microsoft

microsoft.com
|
138,868 installs
| (10) | Free
Visual Studio Code extension for Azure Logic Apps (Standard)
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Azure Logic Apps for Visual Studio Code (Standard)

In Visual Studio Code, you can use the Azure Logic Apps (Standard) extension to quickly create, debug, manage, and deploy logic apps directly to Azure. For requirements and more information, see Create a Standard logic app workflow using Visual Studio Code.

Sign up today for your free Azure account and receive 12 months of free popular services, $200 free credit and 25+ always free services 👉 Start Free.

Azure Logic Apps - Create unit tests from Standard workflows

Starting with version 5.58.8, the Azure Logic Apps (Standard) extension for Visual Studio Code provides the capability to create unit test from a workflow run or a workflow saved definition, that can be edited and executed locally. For more information, see Create unit tests from Standard workflows in Azure Logic Apps with Visual Studio Code (Preview).

Azure Logic Apps - Create Standard logic app projects from Azure portal export

Starting with version 5.18.7, the Azure Logic Apps (Standard) extension for Visual Studio Code provides the capability to create Standard logic app projects from a logic app exported from the Azure portal. For more information, see Export Standard logic apps from Azure portal to Visual Studio Code.

Azure Logic Apps - Introducing the Azure Logic Apps Hybrid deployment model (preview)

Starting with version 4.107.2, the Azure Logic Apps (Standard) extension for Visual Studio Code introduces the Azure Logic Apps Hybrid deployment model, a new feature that gives you more flexibility and control over your infrastructure. This offering lets you build and deploy workflows that run on customer-managed infrastructure, providing you with the option to run Standard logic apps on premises, in a private cloud, or even in a non-Microsoft public cloud. For more information, see Introducing the Logic Apps Hybrid Deployment Model (Public Preview).

Azure Logic Apps - Automatic Regeneration of Connection ACL keys

Starting with version 4.57.0, the Azure Logic Apps (Standard) extension for Visual Studio Code will automatically regenerate the keys required to allow the extension to access Azure Managed Connections. This will allow the same Azure Managed Connection to be used for projects for longer than 7 days without any user intervention. For more information, see Regeneration Azure Managed Connection ACL for Local Development.

Azure Logic Apps - Introducing Azure Logic Apps Rules Engine

Starting with version 4.25.1, the Azure Logic Apps (Standard) extension for Visual Studio Code introduces the Rules Engine, a decision management inference engine. This engine allows customers to build Standard workflows in Azure Logic Apps and integrate readable, declarative, and semantically rich rules that operate on multiple data sources. Currently, the native data sources available for the Rules Engine are XML and .NET objects. For more information, see Decision management and business logic integration using the Azure Logic Apps Rules Engine (Preview).

Azure Logic Apps - .NET 10 Custom Code projects

.NET 10 custom code projects are class libraries loaded by the Logic Apps runtime, not standalone Functions applications. The template does not generate Program.cs or include ASP.NET Core HTTP integration or Application Insights worker-service packages.

The template retains the Functions Worker and Worker SDK, uses Workflows SDK 1.4.1, and explicitly references the worker extensions abstractions for function attributes. Dependency copying and build-triggered publication into the sibling Logic App's lib/custom/net10.0 folder are preserved. The unused output-directory and net472 copy workaround targets have been removed.

This template cleanup applies to newly created custom code projects. It does not modify existing projects or the separate codeful Logic App application templates.

New regular Logic App projects default LOGIC_APPS_CUSTOMCODE_DOTNETVERSION to net10.0 without requiring a framework selection. Custom code projects retain their selected .NET 8 or .NET 10 setting; .NET Framework, Rules Engine, codeful, existing regular projects, and package imports do not receive this default. FUNCTIONS_INPROC_NET8_ENABLED remains unchanged.

Adding a .NET 10 custom code project to an existing Logic App also sets LOGIC_APPS_CUSTOMCODE_DOTNETVERSION to net10.0 in that Logic App's local.settings.json, replacing an older value if present. Existing workflows and unrelated app settings are preserved.

To migrate an existing .NET 8 custom code project to .NET 10, follow Logic Apps Standard custom code now supports .NET 10. The guide covers project dependencies, runtime settings, coordinated debugging, and build and deployment verification.

Azure Logic Apps - Automated Deployment Scripts Generation (preview)

Starting with version 4.4.3, the Azure Logic Apps (Standard) extension for Visual Studio Code supports the ability to generate ARM templates for Logic Apps Standard applications and Azure Managed Connections. It will also support the generation of Azure DevOps YAML pipelines, sppeding up the move from Local development to cloud using DevOps best practics. For more information, see Automate build and deployment for Standard logic app workflows with Azure DevOps (preview).

Azure Logic Apps - Improved Onboarding Experience

Starting with version 2.81.5, the Azure Logic Apps (Standard) extension for Visual Studio Code includes a dependency installer that automatically installs all the required dependencies in a new binary folder and leaves any existing dependencies unchanged. For more information, see Get started more easily with the Azure Logic Apps (Standard) extension for Visual Studio Code.

Azure Logic Apps - Data Mapper for Visual Studio Code

In Visual Studio Code, you can graphically describe transformations by mapping relationships between data types in a source schema and a target schema. After you install the Azure Logic Apps - Data Mapper, you can create direct basic relationships and more complex transformations using functions, handling any translation between supported schema types in the backend. For more information, see Create maps to transform data in Azure Logic Apps with Visual Studio Code (preview).

Azure Logic Apps (Standard) moves to the Resources tab

🎉 Version 2.15.15 and later: The Azure Logic Apps extension now follows the design pattern that Azure extensions follow. Previously, in the Azure window, an Azure Logic Apps extension section showed your Azure subscriptions and associated "remote" logic apps hosted in Azure.

Now, your remote logic apps still appear in the Azure window, but in the Resources section instead. You can see your remote logic apps when you expand the Logic App node.

Extension toolbar buttons have now migrated to the Workspace section.

Azure Logic Apps in Resources tab.

Azure Logic Apps (Standard) Custom Code Workspace

We are excited to announce a new feature in Logic Apps that allows users to author their own custom code using the .NET Framework. With this new feature, users can create custom code actions that can be used in their Logic Apps workflows.

Please note that this feature is currently in private preview and is only available on Windows. We encourage users to try out this new feature and provide feedback to help us improve it.

Known issues

For known issues, see GitHub issues - Azure Logic Apps.

Local SMB file system connections

Creating a local file system connection to an SMB share requires Windows. The extension runs net.exe use directly, without a shell, and returns the existing UNC mountPath on success. No PowerShell adapter or additional runtime dependency is required.

Process output is discarded, and failures return a fixed message. Raw process errors, command arguments, and diagnostic output are not forwarded to the designer, logs, or telemetry. If a connection fails, check the share path, credentials, network access, and any existing connections to the same server.

Passwords remain in the net.exe process arguments and may be visible to local process inspection or process-creation auditing. This protects the extension's error-reporting path, not command-line credential exposure. Standard net use password parsing still applies, including the special * password-prompt syntax; the extension does not provide interactive input.

Experimental local bundles

Enable azureLogicAppsStandard.useExperimentalExtensionBundle to bind extension-launched design-time hosts (including Data Mapper) and F5 to a selected cached bundle. A shared, ephemeral loopback metadata-only source advertises only that folder, preventing Core Tools' forced latest lookup from selecting a public bundle. It serves no archives or project files and is disposed when the extension unloads. No project configuration, process-wide environment, installed Core Tools, or other cached versions are modified.

A blank experimentalExtensionBundleVersion selects the highest local version; an explicit value selects that exact three- or four-part cache folder version. A project's AzureFunctionsJobHost_extensionBundle_version setting takes precedence over the inherited environment pin and experimental version setting. Folder and manifest versions are validated independently: folder 1.197.13 can contain manifest version 1.197.0.13. Selection logs are not proof of another process's loaded assembly.

Healthy local experimental bundles work offline. Missing bundles require an explicitly configured source, respecting project/environment source precedence. Downloads are staged and validated before replacement; failures preserve the previous cache and stop launch without public substitution. Correct a failed installation and reload before retrying. Changing selection does not migrate an already-running host: stop that project's host through its normal controls before reopening the designer. Unknown or different tracked selections are rejected, not silently reused or terminated.

The override does not apply to a separately launched func host start or a manually executed shell task. F5 binds the generated debug-symbol process task to the same selected bundle; custom symbol commands remain caller-owned. NuGet projects and nonexperimental launches retain existing behavior. A local bundle does not update cloud services.

Experimental F5 supports explicit workspace shell/process host tasks and the extension-generated type: "func", command: "host start" task when its provider resolves to a shell/process execution. The host and generated symbol tasks are executed as new, workspace-scoped tasks so VS Code applies the overrides without mutating saved tasks. Because the public Task API cannot retain a saved task's dependsOn graph on such a replacement, experimental F5 rejects those configurations rather than silently dropping prerequisites. Disable experimental bundles to run a customized dependency graph. Existing Azurite, pre-debug validation, and custom-code build/publish steps still run; nonexperimental and NuGet tasks retain their saved dependency graphs.

Providing feedback

  • To open product bugs, go to GitHub issues for Azure Logic Apps.

  • To submit feedback and comments, use the Azure Logic Apps feedback form.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Telemetry

Visual Studio Code collects usage data and sends it to Microsoft to help improve our products and services. Read our privacy statement to learn more. If you don’t wish to send usage data to Microsoft, you can set the telemetry.enableTelemetry setting to false. Learn more in our FAQ.

License

MICROSOFT SOFTWARE LICENSE TERMS

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft