Introducing the Logic Apps Hybrid Deployment Model (Public Preview)

Introducing the Logic Apps hybrid deployment model

We’re excited to announce the launch of the Logic Apps hybrid deployment model, a new feature that provides customers with additional flexibility and control. This new offering allows you to build and deploy workflows that run on your customer management infrastructure and also gives you the option to run Logic Apps on-premises, in a private cloud, or in a third-party public cloud.

The Logic Apps hybrid deployment model allows you to tailor an integrated solution to fit your specific needs, including compliance, data privacy, and network restrictions. This model gives you the freedom to choose the environment that best suits your workflow while still leveraging the power of Azure Logic Apps.

The hybrid deployment model supports a semi-connected architecture. This means that you process the workflow locally, the data processed by the workflow remains on the local SQL Server, and also provides the ability to connect to the local network. The hybrid deployment model is based on Logic Apps Standard, so built-in connectors run on local compute, providing access to local data sources and higher throughput.

Some scenarios require connectivity to external resources, such as Office 365, Microsoft Teams, and SaaS-based systems such as Dataverse. For these use cases, you can leverage the large library of Azure connectors to meet these requirements. You also need an internet connection to manage your logic app in the Azure portal. However, the semi-connective nature of our platform allows us to absorb temporary internet connectivity issues.

Hybrid deployment model use cases

During our early access preview, we had the opportunity to work with many of our customers to better understand their needs. The usage patterns we have encountered generally fall into the following sectors:

Introducing a billing model

A billing model was introduced to support the hybrid deployment model. Customers run these workloads on managed infrastructure, so they are responsible for their Kubernetes infrastructure, such as AKS or AKS-HCI (with additional deployments to come). Customers are also responsible for licensing SQL Server to meet their runtime data storage requirements. In addition to these prerequisites, you are charged $0.18 (USD) per vCPU/hour to support Logic Apps workloads. This allows customers to scale resources as needed to support dynamic workloads without having to ‘buy at peak’ and pay only for what they need. For scenarios where customers require Azure/managed connectors (e.g. Office 365, Microsoft Teams), existing usage charges will apply for that run.

Additional Resources

For additional information and step-by-step guides on how to set up a hybrid deployment of Logic Apps, check out the following resources:

Setting up your own infrastructure for standard logic app workflows – Azure Logic Apps | microsoft run

Create a standard logic app workflow for hybrid deployments – Azure Logic Apps | microsoft run

Known Limitations

This is a known product gap that we are working on and support is expected in the near future.

• SAP access via SAP built-in connector
• XSLT 1.0 for custom code
• Custom code support through .NET Framework
• Managed Identity Authentication
• file system connector
• Updated VS Code extension to allow hybrid deployments

Stay tuned for further updates and detailed documentation as we roll out this exciting new feature. We’re excited to see how you can leverage the power of the Logic Apps hybrid deployment model to drive innovation and efficiency in your organization.