How to Import an Azure Event Hubs Namespace into Terraform

Import Azure Event Hubs Namespace with Terraback (recommended)

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

Example azurerm_eventhub_namespace configuration

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

resource "azurerm_eventhub_namespace" "main" {
  name                = "prod-ehns"
  resource_group_name = "prod-rg"
  location            = "eastus"
  sku                 = "Standard"
  capacity            = 1
}

Gotchas when importing a Azure Event Hubs Namespace

• The namespace name must be globally unique; it forms the *.servicebus.windows.net hostname.
• Event hubs inside the namespace are separate azurerm_eventhub resources.
• auto_inflate_enabled and maximum_throughput_units only apply to the Standard SKU.
• Switching to/from the Premium or Dedicated tier can force recreation; review the sku change carefully.

Doing it manually with terraform import

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