How to Import an Azure App Service Plan into Terraform
terraback azure import --method bulk. Terraback writes the matching azurerm_service_plan resource block and the Terraform 1.5+ import block for you, so you do not have to run terraform import by hand. The import ID is the full resource ID (.../providers/Microsoft.Web/serverFarms/<name>).Import Azure App Service Plan with Terraback (recommended)
Terraback reverse-engineers your live infrastructure: it reads the Azure App Service resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure App Service Plan to managed Terraform.
Scan your Azure account
terraback scan all azure --subscription-id YOUR_IDGenerate import blocks and import into state
terraback azure import --method bulkThe 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_service_plan.main
id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.Web/serverFarms/prod-plan"
}Example azurerm_service_plan configuration
Here is a realistic Azure App Service Plan block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.
resource "azurerm_service_plan" "main" {
name = "prod-plan"
resource_group_name = "prod-rg"
location = "eastus"
os_type = "Linux"
sku_name = "P1v3"
}Gotchas when importing a Azure App Service Plan
- The ARM type is Microsoft.Web/serverFarms even though the Terraform type is azurerm_service_plan.
- azurerm_service_plan replaced the deprecated azurerm_app_service_plan; os_type and sku_name are now top-level required arguments.
- os_type (Linux/Windows) is immutable; changing it forces a new plan.
- Web apps and function apps that run on the plan are separate resources referencing service_plan_id.
Doing it manually with terraform import
The native approach is to write the azurerm_service_plan block by hand, then run terraform import azurerm_service_plan.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
Import your whole Azure account in minutes
Terraback scans 80+ Azure resource types and emits clean Terraform plus import blocks, running locally with read-only credentials. $499 once, no SaaS.