Azure Logic Apps connects Azure services to on-premises Kubernetes, with workflow orchestration and run observability.
Azure Logic Apps got a three-part preview update at Ignite 2026. It covers hybrid deployment, enterprise integration and observability. Microsoft's Azure Integration Services Blog laid it out on November 17, 2026. This is a preview, so Microsoft's own Azure Updates definition applies: preview means available to all Azure customers for non-production use and testing. Treat it as a lab item, not a production commitment.

Azure Logic Apps connects Azure services to on-premises Kubernetes, with workflow orchestration and run observability. What Microsoft announced​

The blog groups these items under "modernize the integrations your business depends on". The relevant pieces are:

  • Hybrid Logic Apps: support for additional Kubernetes environments, including RKE2 and Red Hat OpenShift. It also adds DevOps deployment capabilities and Integration Account support in semi-connected environments.
  • Observability: a new unified dashboard for individual Logic Apps, in public preview. Microsoft says it helps teams monitor workflow execution and troubleshoot through one consolidated experience.
  • Integration: the HL7 connector is now generally available. New MLLP and MSMQ connectors are in public preview, for healthcare messaging and legacy applications respectively. Data Mapper also gets enhancements.

The statuses differ. HL7 is GA. The MLLP and MSMQ connectors and the dashboard are preview. Don't treat the whole package as one maturity level.

What the announcement doesn't say​

The announcement is thin on detail. It doesn't describe the dashboard's panels or metrics, how to enable it, or which Logic Apps plans it supports. It also doesn't say what the DevOps deployment capabilities involve, or which Integration Account functions work in semi-connected environments. It gives no rollout schedule, and it doesn't say whether the dashboard is fleet-wide or replaces existing Azure Monitor tooling. It describes the dashboard as covering "individual Logic Apps", so don't assume more than that.

Hybrid deployment: what to check first​

RKE2 and OpenShift aren't entirely new in the documentation. Microsoft Learn's hybrid deployment page already lists Azure Arc-enabled Kubernetes on AKS, Azure Local and Windows Server, Red Hat OpenShift and Rancher RKE2. Microsoft's community blog has also carried walkthroughs. One covers deploying Hybrid on a self-managed RKE2 cluster using MetalLB. Another covers self-managed Red Hat OpenShift or Azure Red Hat OpenShift. The Ignite news reads as Microsoft continuing to expand and formalize that support, not a sudden arrival. The blog doesn't say how its wording maps onto the existing documented configurations, so check current Learn documentation before planning.

The hybrid model has constraints that the new preview features aren't said to remove:

  • Standard workflows only. Hybrid deployment hosts Logic Apps Standard workflows on your own infrastructure. The runtime runs in an Azure Container Apps extension.
  • Local and Azure-connected management are separate. Workflows that depend only on local resources can keep running during an Azure outage. Azure Arc operations and other Azure-dependent features might not be available. Microsoft states that hybrid deployment isn't a fully autonomous, air-gapped management plane.
  • Disconnection limits logging. The runtime can keep logging data for up to 24 hours while disconnected. Anything beyond that might be lost.
  • You supply storage. A SQL database holds run history, inputs and outputs. An SMB file share holds artifacts such as maps and schemas.
  • Some Standard features are missing. Unsupported capabilities include deployment slots, Azure Business Process Tracking, Resource Health in the portal, and managed-identity authentication for connector operations.
  • Managed connectors still need Azure. Connectors hosted in Azure need connectivity to their Azure-hosted services. Built-in runtime-native operations run locally.
  • Region availability is limited. Learn currently lists hybrid support in a specific set of Azure regions. Verify yours before committing.

OpenShift and RKE2 each have their own setup quirks, according to Microsoft's documentation:

  • Ingress: Self-managed clusters have no cloud load balancer to give the Envoy ingress an IP address. You need MetalLB or another in-cluster option, or an external load balancer using NodePort.
  • RKE2 DNS: The az containerapp arc setup-core-dns helper doesn't support RKE2. You configure CoreDNS manually through a HelmChartConfig and a kube-dns alias.
  • RKE2 stability: Microsoft says to raise inotify limits on each node to avoid runtime pods entering CrashLoopBackOff.
  • OpenShift permissions: The extension install grants elevated security context constraints (anyuid, privileged, hostnetwork) to service accounts. Run those through your security review first.
  • Log Analytics: If you want it, enable it when you create the extension. It can't be added later.

The dashboard in context​

Logic Apps already offers several monitoring tools:

  • Run history: shows run status and per-step inputs and outputs.
  • Trigger history: shows each trigger attempt and its outcome.
  • Azure Monitor alerts: can fire on metrics such as failed triggers.
  • Azure Monitor Logs: can capture trigger, run and action events. Those logs can also go to Azure Storage or Event Hubs.

In the Standard Azure portal experience, trigger and run history sit at the workflow level, not the logic app level. A consolidated per-Logic-App view could reduce the clicking. But the announcement doesn't say the dashboard adds anything beyond that, and it isn't confirmed to replace diagnostic settings. In my assessment, that's the likely appeal, but it's an inference from the stated purpose, not a documented capability.

Practical advice​

  1. Hybrid users: match your Kubernetes distribution, version and Azure region against the current Learn requirements page. Don't rely on the Ignite summary.
  2. Disconnected scenarios: plan for the 24-hour logging window and for the Azure-dependent features that go dark.
  3. Dashboard testing: try it in non-production first. Compare it against your existing Azure Monitor alerts and log queries, and keep those in place.
  4. Healthcare and legacy messaging: HL7 is GA. MLLP and MSMQ are preview, so don't put them on a critical path yet.
  5. Wait for documentation: the DevOps deployment details and Integration Account behavior in semi-connected setups aren't published in the announcement.

Microsoft's blog also covers Logic Apps Automation, Azure Connector Namespace and AI features. Those are separate from this story.

Bottom line​

This is a modest but useful update for teams running Logic Apps outside Azure's own infrastructure. The substance is broader Kubernetes platform support and a first look at consolidated monitoring. The announcement leaves several practical questions unanswered, and preview status means it shouldn't carry production workloads yet.

 

References

  1. (In preview) Public Preview: New integration, hybrid deployment, and observability capabilities in Azure Logic Apps Azure Updates 2026-11-17T20:00:32Z
  2. What's new in Azure Logic Apps at Microsoft Ignite 2026 | Microsoft Community Hub techcommunity.microsoft.com
  3. Set up your own infrastructure for Standard logic app workflows - Azure Logic Apps | Microsoft Learn learn.microsoft.com