terraform-search-import

To import existing Azure resources into Terraform, you discover unmanaged infrastructure using Azure CLI and generate Terraform import blocks. This brings manually created resources under reliable infrastructure-as-code management without rebuilding them from scratch.

The best way to bring unmanaged Azure infrastructure under code management is using a resource discovery workflow that inventories resources and generates Terraform import blocks. This ensures resources are safely mapped and managed for ongoing governance.

Yes, you can bulk import Azure resources across subscriptions and resource groups into Terraform. The workflow generates and applies import blocks safely for common Azure platform services, enabling efficient migration and auditing of large unmanaged estates.

Yes, you need Azure CLI to discover existing Azure resources before generating Terraform import configurations. The azurerm provider and Terraform import or experimental search capabilities are also required to validate resource IDs and produce compliant configuration.

To refactor Terraform imported resources into AVM modules, you perform post-import refactoring after the initial bulk import. This moves raw imported resources toward cleaner module-based architecture using Azure Verified Modules for better codebase governance.

Terraform 1.14+ search workflows can optionally import Azure resources when azurerm provider support exists. If provider support is unavailable, the workflow falls back to a dependable manual path using generated import blocks.