How to Import an Azure Event Grid Topic into Terraform

Import Azure Event Grid Topic with Terraback (recommended)

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

Example azurerm_eventgrid_topic configuration

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

resource "azurerm_eventgrid_topic" "main" {
  name                = "prod-egtopic"
  resource_group_name = "prod-rg"
  location            = "eastus"
  input_schema        = "EventGridSchema"
}

Gotchas when importing a Azure Event Grid Topic

• A custom topic (azurerm_eventgrid_topic) differs from a system topic (azurerm_eventgrid_system_topic) and a domain (azurerm_eventgrid_domain); confirm which you have.
• input_schema is immutable; changing between EventGridSchema, CloudEventSchemaV1_0, and CustomEventSchema forces recreation.
• Event subscriptions are separate azurerm_eventgrid_event_subscription resources.
• The primary_access_key/secondary_access_key and endpoint are sensitive computed outputs.

Doing it manually with terraform import

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