Introducing the Logic Apps Hybrid Deployment Model
We are excited to announce the launch of the Logic Apps Hybrid Deployment Model, a new feature that empowers our customers with additional flexibility and control. This new offering allows you to build and deploy workflows that run on customer-managed infrastructure, providing you with the option to run Logic Apps 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. What this means is that you get local processing of workflows, the data processed by the workflows remains in your local SQL Server and also provides you the ability to connect to local networks. Since the Hybrid Deployment Model is based upon Logic Apps Standard, the built-in connectors will execute in your local compute giving you access to local data sources and higher throughput.
In some scenarios, you will need connectivity to external resources such as SaaS based systems like Office 365, Microsoft Teams and Dataverse. For these use cases, you can leverage our large library of Azure connectors to fulfil this need. You will also require internet connectivity to manage your Logic App from the Azure Portal. But, the semi-connected nature of our platform allows you to absorb temporary internet connectivity issues.
Hybrid Deployment Model Use Cases
During our early access preview, we had the opportunity to work with many customers to better understand their needs. The usage patterns that we encountered typically fall into the following segments:
Billing Model Introduced
A billing model has been introduced to support the Hybrid Deployment Model. Since a customer is running these workloads on their managed infrastructure, customers are responsible for their Kubernetes infrastructure such as AKS or AKS-HCI (more distributions to come). A customer is also responsible for providing a SQL Server license for their runtime data storage needs. Beyond these pre-requisites, there is a charge per vCPU/hour charge of $0.18 (USD) to support the Logic Apps workloads. This allows customers to pay for just what they need and scale their resources as needed to support dynamic workloads, without the need to 'buy for peak' usage. For scenarios where customers need Azure/managed connectors (like Office 365, Microsoft Teams), existing usage billing applies for those executions.
Additional Resources
For additional information and step by step guides on how to establish your Hybrid deployment of Logic Apps, please check out the following resources:
Set up your own infrastructure for Standard logic app workflows - Azure Logic Apps | Microsoft Learn
Create Standard logic app workflows for hybrid deployment - Azure Logic Apps | Microsoft Learn
Known Limitations
These are known product gaps that we are working on and anticipate support for in the near future
- SAP access through the SAP built-in connector
- XSLT 1.0 for custom code
- Custom code support with .NET Framework
- Managed identity authentication
VS Code extension update that allows for hybrid deploymentsThis has now been released as of 10/24/2024
Stay tuned for more updates and detailed documentation as we roll out this exciting new feature. We look forward to seeing how you will harness the power of the Logic Apps Hybrid Deployment Model to drive innovation and efficiency in your organization.
Microsoft
