AzureAzure Service Busazurerm_servicebus_queuePro

How to Import an Azure Service Bus Queue into Terraform

To import an existing Azure Service Bus Queue into Terraform, scan it with Terraback and run terraback azure import --method bulk. Terraback writes the matching azurerm_servicebus_queue 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 namespace (.../namespaces/<ns>/queues/<name>).

Import Azure Service Bus Queue with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Azure Service Bus resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure Service Bus Queue to managed Terraform.

1

Scan your Azure account

terraback scan all azure --subscription-id YOUR_ID
2

Generate import blocks and import into state

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_servicebus_queue.orders
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.ServiceBus/namespaces/prod-sbns/queues/orders"
}

Example azurerm_servicebus_queue configuration

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

resource "azurerm_servicebus_queue" "orders" {
  name         = "orders"
  namespace_id = azurerm_servicebus_namespace.main.id
  max_delivery_count = 10
}

Gotchas when importing a Azure Service Bus Queue

  • Provider 4.x uses namespace_id (the parent's full ARM ID), not separate namespace_name/resource_group_name arguments.
  • The import ID still nests under the namespace: .../namespaces/<ns>/queues/<name>.
  • requires_session and requires_duplicate_detection are immutable after creation.
  • max_message_size_in_kilobytes and partitioning options are Premium-only.

Doing it manually with terraform import

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