How to Import an Azure Event Grid Event Subscription into Terraform

Import Azure Event Grid Event Subscription 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 Event Subscription 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_event_subscription.orders
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.Storage/storageAccounts/prodassets/providers/Microsoft.EventGrid/eventSubscriptions/orders-sub"
}

Example azurerm_eventgrid_event_subscription configuration

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

resource "azurerm_eventgrid_event_subscription" "orders" {
  name  = "orders-sub"
  scope = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.Storage/storageAccounts/prodassets"

  webhook_endpoint {
    url = "https://app.example.com/events"
  }
}

Gotchas when importing a Azure Event Grid Event Subscription

• The import ID is the scope resource ID with /providers/Microsoft.EventGrid/eventSubscriptions/<name> appended, so it embeds the full ID of whatever resource (storage account, resource group, topic) it is attached to.
• scope can be a topic, storage account, resource group, or subscription; it is immutable, so a different scope means a new resource.
• Exactly one endpoint block is allowed (webhook_endpoint, azure_function_endpoint, eventhub_endpoint_id, etc.); webhook URLs are not always returned and may show a diff.
• An Event Grid topic is a different resource (azurerm_eventgrid_topic); a subscription on a topic still imports through this resource.

Doing it manually with terraform import

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