How to Import an Azure CDN Endpoint into Terraform

Import Azure CDN Endpoint with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Azure CDN resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure CDN Endpoint 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_cdn_endpoint.main
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.Cdn/profiles/prod-cdn/endpoints/prod-endpoint"
}

Example azurerm_cdn_endpoint configuration

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

resource "azurerm_cdn_endpoint" "main" {
  name                = "prod-endpoint"
  profile_name        = "prod-cdn"
  resource_group_name = "prod-rg"
  location            = "eastus"

  origin {
    name      = "origin1"
    host_name = "prodassets.blob.core.windows.net"
  }
}

Gotchas when importing a Azure CDN Endpoint

• The endpoint ID nests under its parent profile; you cannot import an endpoint without the .../profiles/<profile>/endpoints/ path.
• The classic Microsoft.Cdn endpoint is distinct from azurerm_cdn_frontdoor_endpoint (Front Door Standard/Premium); they are not interchangeable.
• At least one origin block is required and the origin host_name is immutable.
• Custom domains are separate azurerm_cdn_endpoint_custom_domain resources.

Doing it manually with terraform import

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