How to Import an Azure NetApp Capacity Pool into Terraform
terraback azure import --method bulk. Terraback writes the matching azurerm_netapp_pool 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 nested under the account (.../netAppAccounts/<account>/capacityPools/<name>).Import Azure NetApp Capacity Pool with Terraback (recommended)
Terraback reverse-engineers your live infrastructure: it reads the Azure NetApp Files resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure NetApp Capacity Pool 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_netapp_pool.main
id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.NetApp/netAppAccounts/prod-anf/capacityPools/prod-pool"
}Example azurerm_netapp_pool configuration
Here is a realistic Azure NetApp Capacity Pool block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.
resource "azurerm_netapp_pool" "main" {
name = "prod-pool"
resource_group_name = "prod-rg"
location = "eastus"
account_name = "prod-anf"
service_level = "Premium"
size_in_tb = 4
}Gotchas when importing a Azure NetApp Capacity Pool
- The pool is a child of the account: its ARM ID nests under .../netAppAccounts/<account>/capacityPools/<name>, and account_name must reference the parent account.
- size_in_tb is the provisioned pool size and has a minimum of 4 TB (older pools may show 2 TB); it is billed regardless of how much the volumes consume.
- service_level (Standard, Premium, Ultra) is set on the pool and is immutable for the pool's lifetime; changing it forces recreation.
- Volumes draw their capacity from the pool, so the pool cannot be deleted until all its volumes are removed.
Doing it manually with terraform import
The native approach is to write the azurerm_netapp_pool block by hand, then run terraform import azurerm_netapp_pool.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.