How to Import an Azure AI Search Service into Terraform
terraback azure import --method bulk. Terraback writes the matching azurerm_search_service 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.Search/searchServices/<name>).Import Azure AI Search Service with Terraback (recommended)
Terraback reverse-engineers your live infrastructure: it reads the Azure AI Search resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure AI Search Service 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_search_service.main
id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.Search/searchServices/prod-search"
}Example azurerm_search_service configuration
Here is a realistic Azure AI Search Service block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.
resource "azurerm_search_service" "main" {
name = "prod-search"
resource_group_name = "prod-rg"
location = "eastus"
sku = "standard"
}Gotchas when importing a Azure AI Search Service
- The service name must be globally unique and lowercase; it forms the *.search.windows.net endpoint.
- sku is immutable; you cannot change between free, basic, standard, and storage_optimized tiers in place.
- replica_count and partition_count are only adjustable above the free/basic tiers.
- Indexes, indexers, and data sources are managed via the search data plane, not the azurerm provider; admin/query keys are sensitive outputs.
Doing it manually with terraform import
The native approach is to write the azurerm_search_service block by hand, then run terraform import azurerm_search_service.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.