How to Import an Azure CDN Profile into Terraform
terraback azure import --method bulk. Terraback writes the matching azurerm_cdn_profile 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 (.../providers/Microsoft.Cdn/profiles/<name>).Import Azure CDN Profile 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 Profile to managed Terraform.
Scan your Azure account
terraback scan all azure --subscription-id YOUR_IDGenerate import blocks and import into state
terraback azure import --method bulkThe 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_profile.main
id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.Cdn/profiles/prod-cdn"
}Example azurerm_cdn_profile configuration
Here is a realistic Azure CDN Profile block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.
resource "azurerm_cdn_profile" "main" {
name = "prod-cdn"
resource_group_name = "prod-rg"
location = "eastus"
sku = "Standard_Microsoft"
}Gotchas when importing a Azure CDN Profile
- Endpoints under the profile are separate azurerm_cdn_endpoint resources and are not imported with the profile.
- sku is immutable; switching between Standard_Microsoft, Standard_Akamai, Standard_Verizon, or Premium_Verizon forces recreation.
- Classic CDN profiles differ from Front Door (azurerm_cdn_frontdoor_profile); confirm which product you actually run before importing.
- location for classic CDN profiles is typically 'global' but the provider stores the deployed region value.
Doing it manually with terraform import
The native approach is to write the azurerm_cdn_profile block by hand, then run terraform import azurerm_cdn_profile.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
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.