Infrastructure Export
Export your live Azure infrastructure into Infrastructure as Code. Download IaC as Terraform , Bicep, or ARM templates or push the code directly to your repository.
Overview
Clophi's Infrastructure Export lets you capture your live Azure environment and turn it into clean, version-controlled IaC. You are not limited to a single resource group, you can assemble a collection of resources from across your subscription and export them as a single infrastructure.
Prerequisites
Before you begin, Clophi needs permission to read the resources you want to export. Grant the Clophi reader service principal the Reader role on either:
- The individual resource groups you wish to access, or
- The subscription scope, for broader access across all resource groups.
Read-only access
The Reader role grants Clophi the ability to list and inspect your resources only.
Step 1 — Browse your resource groups
Once permissions are in place, Clophi fetches the resource groups available to the service principal and lists them in the Resource Groups dashboard. From here you can see everything you are authorized to access in one view.
Step 2 — Select resources and child dependencies
Click into any resource group to view its full list of resources. Select the items you want to include in your export collection. If a selected resource has child resources, they appear in the right-hand tab so you can also include them in the same operation.
Tip
Resources in a single collection can come from different resource groups. You can build the collection that matches your needs.
Step 3 — Import the collection
Once your selection is complete, click Import resource group. Clophi pulls each resource's configuration into your Infrastructure section. Larger collections may take a few seconds more.
Step 4 — Review and configure your infrastructure
After import, your resources land in the Infrastructure section. Implicit dependencies between resources where a resource references another one are wired up automatically. If you have some additional explicit dependencies which are not present in the infrastucture configuration, you can also add them at this stage. If you have any modification you want to perform on any of the imported resources, you can edit each resource through its dedicated form as well.
Step 5 — Download or push to repository
When you are ready, you have two paths to ship your infrastructure code. You can download it as Terraform, Bicep, or ARM templates, either parameterized or non-parameterized, or push the generated code directly to your connected Git repository and open a pull request from the Infrastructure section.
