How to Import an Azure App Configuration into Terraform

Import Azure App Configuration with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Azure App Configuration resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure App Configuration 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_app_configuration.main
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.AppConfiguration/configurationStores/prod-appconfig"
}

Example azurerm_app_configuration configuration

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

resource "azurerm_app_configuration" "main" {
  name                = "prod-appconfig"
  resource_group_name = "prod-rg"
  location            = "eastus"
  sku                 = "standard"
}

Gotchas when importing a Azure App Configuration

• Individual keys and feature flags are separate azurerm_app_configuration_key and azurerm_app_configuration_feature resources, not imported with the store.
• soft_delete_retention_days and purge_protection_enabled cannot be changed after creation on the free SKU.
• Access keys are sensitive computed outputs; reference them via outputs rather than hardcoding.
• The store name must be globally unique and is part of the public endpoint hostname.

Doing it manually with terraform import

The native approach is to write the azurerm_app_configuration block by hand, then run terraform import azurerm_app_configuration.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