How to Import an Azure NetApp Volume into Terraform

Import Azure NetApp Volume 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 Volume 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_netapp_volume.main
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.NetApp/netAppAccounts/prod-anf/capacityPools/prod-pool/volumes/prod-vol"
}

Example azurerm_netapp_volume configuration

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

resource "azurerm_netapp_volume" "main" {
  name                = "prod-vol"
  resource_group_name = "prod-rg"
  location            = "eastus"
  account_name        = "prod-anf"
  pool_name           = "prod-pool"
  volume_path         = "prod-vol-path"
  service_level       = "Premium"
  subnet_id           = azurerm_subnet.netapp.id
  storage_quota_in_gb = 100
  protocols           = ["NFSv3"]
}

Gotchas when importing a Azure NetApp Volume

• The volume nests two levels deep under both account and pool: .../netAppAccounts/<account>/capacityPools/<pool>/volumes/<name>; account_name and pool_name must reference both parents.
• subnet_id must point at a subnet delegated to Microsoft.NetApp/volumes; an undelegated subnet is rejected at apply.
• protocols (for example ["NFSv3"], ["NFSv4.1"], or ["CIFS"]) and service_level are effectively immutable; changing them forces a new volume.
• volume_path (the export path / junction) must be unique within the account and is separate from the resource name.

Doing it manually with terraform import

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