import-infrastructure-as-code

To convert existing Azure resources into Terraform, you can use discovery tools that identify live infrastructure and map it into codified configurations. This skill uses Azure CLI to discover resources and outputs AVM-based Terraform modules for reproducible deployments.

The best way to reverse-engineer live Azure infrastructure into Terraform is by scanning the environment via Azure CLI, mapping resource dependencies, and generating standardized configurations. This process creates AVM-based Terraform modules to enable drift prevention and validation.

Yes, you can use Azure Verified Modules (AVM) when importing infrastructure as code. This skill specifically selects AVM modules during the discovery phase to ensure the generated Terraform configurations are standardized, reusable, and aligned with Microsoft's best practices.

To generate Terraform from a specific Azure subscription or resource group, you provide the subscription ID, resource group name, or individual resource IDs. The skill discovers the targeted resources and outputs corresponding AVM-based Terraform configurations and architecture documentation.

Yes, importing Azure infrastructure as code directly helps with drift prevention by reconstructing live deployments into codified Terraform configurations. This allows you to validate, plan, and reproduce deployments consistently, preventing untracked configuration drift.

When using automated discovery to generate Terraform from Azure, limitations may arise from complex resource dependencies or unsupported AVM mappings. The skill outputs discovery data and architecture documentation to help you validate the generated configurations and manually adjust any incomplete resource mappings.