We are thrilled to announce the General Availability of the Logic Apps Hybrid Deployment Model, a groundbreaking feature that offers unparalleled flexibility and control to our customers. This innovative deployment model allows you to run Logic Apps workloads on customer-managed infrastructure, providing you with the option to host your integration solutions on-premises, in a private cloud, or even in a third-party public cloud.

With the Logic Apps Hybrid Deployment Model, you can tailor your integration solutions to meet your specific needs, whether it’s for regulatory compliance, data privacy, or network restrictions. This model ensures that you have the freedom to choose the best environment for your workflows, while still leveraging the powerful capabilities of Azure Logic Apps.

The Hybrid Deployment Model supports a semi-connected architecture, offering local processing of workflows, local storage, and local network access. This means that the data processed by the workflows remains in your local SQL Server, and you have the ability to connect to local networks. Additionally, the built-in connectors will execute in your local compute, giving you access to local data sources and higher throughput.

 
Since we launched the public preview, we have received an overwhelmingly positive response from customers across various industries. Many customers, including those looking to migrate from BizTalk Server, have expressed interest in this offering due to its ability to co-locate integration platforms near key lines of business systems, avoiding dependencies on public internet to process transactions.

Journey of the Hybrid Deployment Model Feature

At the Integrate 2024 event, we announced the early access preview of the Hybrid Deployment model for Logic Apps Standard. This initial phase allowed interested parties to nominate themselves for early access and provided valuable feedback on the model’s functionality and benefits.

Following the private preview, we launched the public preview, which empowered our customers with additional flexibility and control. This phase allowed customers to build and deploy workflows on customer-managed infrastructure, offering the option to run Logic Apps on-premises, in a private cloud, or in a third-party public cloud. The public preview also introduced the semi-connected architecture, enabling local processing of workflows and access to local data sources.

In October 2024, we refreshed the public preview and received an overwhelmingly positive response from customers across various industries. This feedback highlighted the model’s ability to meet specific use cases, such as migrating from BizTalk Server and co-locating integration platforms near key lines of business systems. The public preview refresh also emphasized the model’s alignment with our promise of providing customers with more options to meet their business needs.

We are excited to see how our customers will leverage the Logic Apps Hybrid Deployment Model to meet their business needs and drive innovation. Thank you for your continued support and feedback.

New features in the GA release:

Open Telemetry support:

Open telemetry is a vendor-neutral open-source Observability framework for instrumenting, generating, collecting, and exporting telemetry data.

The support for Open Telemetry in Hybrid deployment model ensures the seamless logging in the semi-connected scenarios and provides the ability to choose any observability platform as a telemetry endpoint.  More details here.

To set up Open Telemetry capability from Azure portal, follow these steps:

1. Open the host.json in the root directory of SMB file share path configured in your logic app.


2. In the host.json file, at the root level, add the following telemetryMode setting with the OpenTelemetry value, for example:
   
   {
   “version”: “2.0”,
       “extensionBundle”: {
           “id”: “Microsoft.Azure.Functions.ExtensionBundle.Workflows”,
           “version”: “[1.*, 2.0.0)”
       },
       “telemetryMode”: “OpenTelemetry”
   }
   
   When you enable Open Telemetry in the host.json file, your logic app exports telemetry based on the Open Telemetry-supported app settings that you define in the environment.


3. Add below app settings from portal by navigating to Containers–>Environment variables–>edit and deploy.

4. If your Open Telemetry endpoint requires other Open Telemetry related settings, include these settings in the app settings too.

Support for Zip deployment through VSCode:

The support for Zip deployment in VSCode deployment has enhanced the deployment experience with more reliability. This feature uses Azure Entra authentication for deployment, hence the VSCode machine doesn’t require to have permissions on the SMB share and the user need not to provide SMB credentials in subsequent deployments.

To use Zip deployment, follow below steps:

1. create an app registration.

1. In the VSCode deployment, provide Client ID, Object ID and Client secret values. 

If there are any concerns with creating App registration, you can continue to use SMB deployment option by choosing “Use SMBDeployment For Hybrid” in the Extensions configuration of VSCode

If you would like to use zip deployment in an existing Logic App, you will need to manually add the app settings as indicated here.

The Zip deployment APIs can be used in CI/CD pipelines as well for DevOps deployment. We will be publishing another blog with detailed steps on the DevOps process.

Support for more regions:

We are pleased to announce the expansion of our hybrid deployment support to additional regions, in response to valuable customer feedback. This enhancement aims to better meet the diverse geographic and operational requirements of your businesses. The hybrid deployment is now available in the following regions:

Central US, East Asia, East US, North Central US, Southeast Asia, Sweden Central, UK South, West Europe, and West US.

Logic Apps Rules Engine Support on Linux containers:

In this release, we have added support for Azure Logic Apps Rules Engine to run on Linux containers which enables customers to use the Rules Engine capabilities in Hybrid Logic Apps.

Improvements for Effective Scaling and Performance:

We have introduced few improvements in the runtime storage and the scaling behaviour aimed at improving  the performance and achieving effective scaling.

Please refer to the following articles:

Scaling mechanism in hybrid deployment model for Azure Logic Apps Standard | Microsoft Community Hub

Hybrid deployment model for Logic Apps- Performance Analysis and Optimization recommendations | Microsoft Community Hub

Diagnostic tool:

To assist with troubleshooting the environment configuration issues, we have created a troubleshooting tool, which will help you review the health of all the components of the hybrid deployment and provide insights. You can find the script in our GitHub repository.

Select the troubleshoot.ps1 file and copy it to a folder and run the script using PowerShell. This script should be run where you have access to kubectl.

References:

Create Standard logic app workflows for hybrid deployment – Azure Logic Apps | Microsoft Learn

Set up your own infrastructure for Standard logic app workflows – Azure Logic Apps | Microsoft Learn

Set up and view enhanced telemetry for Standard workflows – Azure Logic Apps | Microsoft Learn