How to Import an Azure NetApp Account into Terraform

Import Azure NetApp Account 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 Account 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_account.main
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.NetApp/netAppAccounts/prod-anf"
}

Example azurerm_netapp_account configuration

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

resource "azurerm_netapp_account" "main" {
  name                = "prod-anf"
  resource_group_name = "prod-rg"
  location            = "eastus"
}

Gotchas when importing a Azure NetApp Account

• The ARM type is Microsoft.NetApp/netAppAccounts; the account is the top of the NetApp Files hierarchy and holds no storage capacity itself.
• Capacity pools (azurerm_netapp_pool) and volumes (azurerm_netapp_volume) are separate child resources nested under the account, not imported with it.
• Active Directory connections configured on the account contain credentials; review the generated block for sensitive values after import.
• The account cannot be deleted while pools or volumes still exist beneath it.

Doing it manually with terraform import

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