What is Azure Arc-enabled Logic Apps? (Preview)

With Azure Arc-enabled Logic Apps, you can develop and run single-tenant based logic apps anywhere that Kubernetes can run. For example, you can run your logic app workflows on Azure, Azure Kubernetes Service, on premises, and even other cloud providers. This offering provides a centralized single-pane-of-glass management platform through Azure Arc and the Azure portal for the following capabilities:

• Use Azure Logic Apps as your integration platform.
• Connect your workflows to all your services no matter where they're hosted.
• Run your integration solutions directly alongside your services.
• Create and edit workflows using Visual Studio Code.
• Deploy using your choice of pipelines for DevOps.
• Control your infrastructure and resources in Azure, non-Azure, multiple clouds, on premises, and edge environments.

For more information, review the following documentation:

• What is Azure Logic Apps?
• Single-tenant versus other Logic Apps environments
• Azure Arc overview
• Azure Kubernetes Service overview
• What is Azure Arc-enabled Kubernetes?
• What is Kubernetes?

Why use Azure Arc-enabled Logic Apps

With Azure Arc-enabled Logic Apps, you can create and deploy logic app workflows in the same way as in the single-tenant experience for Azure Logic Apps. You also gain more control and flexibility when you have logic apps running on a Kubernetes infrastructure that you operate and manage.

Minor differences exist between the Azure Arc and single-tenant Logic Apps experiences for creating, designing, and deploying logic apps. When you use Azure Arc-enabled Logic Apps, the major difference is that your logic apps run in a custom location. This location is mapped to an Azure Arc-enabled Kubernetes cluster where you have installed and enabled the Azure App Service platform extensions bundle.

For example, this cluster can be Azure Kubernetes Service, bare-metal Kubernetes, or another setup. The extensions bundle enables you to run platform services such as Azure Logic Apps, Azure Functions, and Azure App Service on your Kubernetes cluster.

For more information, review the following documentation:

• Single-tenant versus other Azure Logic Apps environments
• Azure Kubernetes Service overview
• What is Azure Arc-enabled Kubernetes?
• Custom locations on Azure Arc-enabled Kubernetes
• App Service, Functions, and Logic Apps on Azure Arc (Preview)
• Set up an Azure Arc-enabled Kubernetes cluster to run App Service, Functions, and Logic Apps (Preview)

When to use Azure Arc-enabled Logic Apps

Although Kubernetes provides more control and flexibility, you also have operational overhead. If you're satisfied that the Logic Apps service meets your needs, you're encouraged to continue using this service. However, consider using Azure Arc-enabled Logic Apps when you have the following scenarios:

• You already run all your apps and services on Kubernetes. You want to extend these processes and controls to all your other PaaS services.

• You want to use Logic Apps as your integration platform. However, you need fine grained networking with compute control and flexibility. You don't want to use an integration service environment (ISE) or App Service Environment (ASE).

• For security reasons, you need control over where your logic apps run, for example, in your own region or in your own datacenter.

• You want to run your logic apps in multi-cloud scenarios and use the Logic Apps service as your sole integration platform for all your applications wherever they run.

Compare offerings

This table provides a high-level comparison between the capabilities in the current Azure Logic Apps offerings:

Next steps