How to Import an Azure Logic App Workflow into Terraform

Import Azure Logic App Workflow with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Azure Logic Apps resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure Logic App Workflow to managed Terraform.

terraback scan all azure --subscription-id YOUR_ID

terraback azure import --method bulk

The Terraform import block

Terraback emits a Terraform 1.5+ import block like the one below. Because the block lives in your configuration, the import is reviewable in a pull request and repeatable across environments.

import {
  to = azurerm_logic_app_workflow.main
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.Logic/workflows/prod-logicapp"
}

Example azurerm_logic_app_workflow configuration

Here is a realistic Azure Logic App Workflow block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "azurerm_logic_app_workflow" "main" {
  name                = "prod-logicapp"
  resource_group_name = "prod-rg"
  location            = "eastus"
}

Gotchas when importing a Azure Logic App Workflow

• This is a Consumption-tier Logic App; Standard-tier Logic Apps are modeled as azurerm_logic_app_standard (an App Service) instead.
• Triggers and actions are separate azurerm_logic_app_trigger_* and azurerm_logic_app_action_* resources, or supplied via the workflow definition; they are not imported with the workflow shell.
• access_endpoint and callback URLs are computed and sensitive.
• The full workflow definition JSON is not always round-tripped by the provider; review the workflow body after import.

Doing it manually with terraform import

The native approach is to write the azurerm_logic_app_workflow block by hand, then run terraform import azurerm_logic_app_workflow.example <import-id> for every resource, one at a time. That works for a handful of resources, but it does not scale: you author all the HCL yourself and repeat the command for each item. Terraback generates the HCL and the import blocks for your whole account in one pass.

Import other Azure resources